bug reporting and file descriptors...

[Reinhard Tartler]

On Tue, Jul 20, 2010 at 23:27:38 (CEST), Daniel J Blueman wrote:

> With certain types of bug, it really helps to know what file
> descriptors were open at the time of crashing.
>
> For example, gstreamer is crashing in libavformat, however no
> information was gathered to show the path of inodes attached to the
> file descriptors [1], where it would be immediately clear what file to
> try and reproduce with:
>
> $ ls -l /proc/6117/fd
> 0 -> /dev/null
> 1 -> pipe:[3602840]
> 2 -> /dev/pts/6
> 3 -> socket:[3602928]
> 4 -> pipe:[3602929]
> 5 -> pipe:[3602929]
> 6 -> socket:[3602931]
> 7 -> /home/daniel/test.mp3
>
> Would it make sense to have this information, or have I overlooked something?

I think it would be incredibly helpful.

extra points for an interactive apport hook that asks the users if the
detected files may be automatically attached with the bug.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4