Jeff,
that 'proposed change' sort of escaped into the wild in a wash of commits from
a 'mhaberler only' state of affairs.
I'll clean that up eventually.
- Michael
Am 11.01.2012 um 15:34 schrieb Jeff Epler:
> I belatedly took a look at this proposed change.
>
> The added file backtrace.cc do
I belatedly took a look at this proposed change.
The added file backtrace.cc doesn't include a license. If it's
code that you copied from the internet, then you can't just add a
license statement on your own, you have to obey the original (probably
also unspecified) license.
If readlink truncate
ort
>
> - Reply message -
> From: "Michael Haberler"
> Date: Fri, Sep 16, 2011 00:48
> Subject: [Emc-developers] patch: generating a backtrace in task (was: EMC's
> 'silent segfaulting' behaviour)
> To: "EMC developers"
>
> He
y message -
From: "Michael Haberler"
Date: Fri, Sep 16, 2011 00:48
Subject: [Emc-developers] patch: generating a backtrace in task (was: EMC's
'silent segfaulting' behaviour)
To: "EMC developers"
Here's a proposed patch to generate a backtrace in task on
On 16 September 2011 07:48, Michael Haberler 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"
--
BlackBer
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.
http://git.mah.priv.at/gitweb/emc2-dev.git/shortlog/refs/heads/backt