[Emc-developers] patch: generating a backtrace in task (was: EMC's 'silent segfaulting' behaviour)

2011-09-16 Thread Michael Haberler
Here's a proposed patch to generate a backtrace in task on SIGSEGV, SIGFPE and SIGUSR1 the SEGV and FPE signals will abort task, sending SIGUSR1 will create a backtrace and continue. Appropriate Operator message are displayed.

Re: [Emc-developers] patch: generating a backtrace in task (was: EMC's 'silent segfaulting' behaviour)

2011-09-16 Thread andy pugh
On 16 September 2011 07:48, Michael Haberler mai...@mah.priv.at wrote: comments? Looks more helpful than what we get now when we mess up. -- atp Torque wrenches are for the obedience of fools and the guidance of wise men

Re: [Emc-developers] patch: generating a backtrace in task (was: EMC's 'silent segfaulting' behaviour)

2011-09-16 Thread s...@highlab.com
I'd love to have backtraces of users' crashes, but i'm not sure explicit support in each of our executables is the way to do it. Do you know about Apport? It's a system-wide crash reporting tool that might be useful for us. https://wiki.ubuntu.com/Apport - Reply message - From:

Re: [Emc-developers] patch: generating a backtrace in task (was: EMC's 'silent segfaulting' behaviour)

2011-09-16 Thread Michael Haberler
I dont think this is necessarily an either-or. These are disjoint use cases IMV. I concur it would be desirable to have support for something along these lines for end users. It would be a bit more than configuring that tool though ; we probably need to setup a site where this stuff gets

Re: [Emc-developers] Git oddness

2011-09-16 Thread Chris Radek
On Fri, Sep 16, 2011 at 12:43:06AM +0100, andy pugh wrote: I just pushed a commit and got an odd series of messages (also, there was no announcement on #emc-devel) Fixed, thanks! -- BlackBerryreg; DevCon Americas, Oct.