It would be useful if crash dumps included a list of files that were open at
the time of the crash.
This is useful in trying to reproduce problems on long-running applications.
On Linux you can get this information by enumerating /proc/<pid>/fd/, and using
readlink on each item.
Also there is a similar /proc/<pid>/fdinfo/ which shows file positions and
flags. Could be useful at some point.
Since the crashdump format seems to support system specific extensions
(MD_LINUX_AUXV for example), I think this could be implemented as a linux-only
feature at first.
If issue #183 would get fixed, and open-files list implemented then breakpad
crashreports could be considered a replacement for copying coredumps and
binaries around.
Original issue reported on code.google.com by edwinto...@gmail.com on 24 Jul 2010 at 8:54
Original issue reported on code.google.com by
edwinto...@gmail.comon 24 Jul 2010 at 8:54