From the feature page:
"If the executable does not make undefined calls, then it will run
normally. If it does make undefined calls you will either get an abort
as soon as the undefined call is detected or you will get a backtrace
when the undefined call is detected."
Does this mean abrt will tr
On 01/24/2013 08:00 PM, Chris Adams wrote:
Once upon a time, Bill Nottingham said:
Jaroslav Reznik (jrez...@redhat.com) said:
The MEMSTOMP code utilizes GPLV2+ and LGPL3 code. The GPLV2+ code is limited
to the backtrace code which is not thread safe and may need to be
disabled/rewritten.
I a
Chris Adams (cmad...@hiwaay.net) said:
> Once upon a time, Bill Nottingham said:
> > Jaroslav Reznik (jrez...@redhat.com) said:
> > > The MEMSTOMP code utilizes GPLV2+ and LGPL3 code. The GPLV2+ code is
> > > limited
> > > to the backtrace code which is not thread safe and may need to be
> >
On Thu, Jan 24, 2013 at 01:29:36PM -0500, Bill Nottingham wrote:
> Jaroslav Reznik (jrez...@redhat.com) said:
> > = Features/MEMSTOMP =
> > https://fedoraproject.org/wiki/Features/MEMSTOMP
> >
> > Feature owner(s): Jeff Law
> >
> > Include the MEMSTOMP DSOs in Fedora 19 to enable developers to
Once upon a time, Bill Nottingham said:
> Jaroslav Reznik (jrez...@redhat.com) said:
> > The MEMSTOMP code utilizes GPLV2+ and LGPL3 code. The GPLV2+ code is
> > limited
> > to the backtrace code which is not thread safe and may need to be
> > disabled/rewritten.
>
> I assume this could be d
Jaroslav Reznik (jrez...@redhat.com) said:
> = Features/MEMSTOMP =
> https://fedoraproject.org/wiki/Features/MEMSTOMP
>
> Feature owner(s): Jeff Law
>
> Include the MEMSTOMP DSOs in Fedora 19 to enable developers to more quickly
> detect certain library calls which result in undefined behaviou
