Of course, segfaulting is unacceptable to begin with. It's pretty hard to eliminate them if no one knows that they occurred. It would be great if we generated some sort of message with an opportunity to report this to the developers.
It's hard to do that if a machine isn't connected to a network. Saving a report and suggesting that it be emailed to developers would be worthwhile. Ken On 9/15/2011 6:19 PM, Michael Haberler wrote: > I wonder what folks think about the current EMC behaviour of 'silent > segfaulting'. > > IMO this is unacceptable - it should at least report the fact and create a > backtrace for inspection. > > Opinions? > > -Michael > > example - while debugging a patch, the task interp instance segfaulted and > continued to run happily - the only notice I got was: > > $ dmesg > [48237.278086] milltask[15797]: segfault at 46 ip 005be977 sp bfd1b0d0 error > 4 in libc-2.11.1.so[563000+153000] > > > ------------------------------------------------------------------------------ > Doing More with Less: The Next Generation Virtual Desktop > What are the key obstacles that have prevented many mid-market businesses > from deploying virtual desktops? How do next-generation virtual desktops > provide companies an easier-to-deploy, easier-to-manage and more affordable > virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
