Gerrit - I just spent another half hour poking around looking at bug 470029 et al.
I start to get the impression that there is no bug in dash. evolution-data-server crashes, traps the crash, calls /usr/lib/libgnomeui-0/gnome_segv2 \"evolution-data-server-1.12\" 11 \"1.12.1\" in an attempt to get a useful bug report back to the evolution developers. In Gutsy, that program is diverted to debreaper, the python program that is supposed to rummage around in the dead program to create the email. Except that in this case it instead fishes around in the dash that was called with the above -c command line. Dash is still running smoothly as the parent of debreaper, patiently waiting for debreaper to finish. debreaper is too stupid to notice, and reports on dash in the middle of its wait4() call. I looked for evidence of bugs like this attributed to bash, but didn't see them. I can explain that, though, if bash (unlike dash) optimizes the "last call" into an exec. Then debreaper's parent is evolution-data-server, and the desired stack is traced. An example of the above is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467561 I have some evidence to back this up, but there's also a lot of intuition involved. I thought you'd like to hear it anyway. - Larry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
