On Thu, 14 Sep 2023 17:04:08 +0200
Daniel Kiper wrote:
> On Mon, Aug 14, 2023 at 12:47:33AM -0500, Glenn Washburn wrote:
> > On Sat, 12 Aug 2023 01:57:42 +0200
> > "Vladimir 'phcoder' Serbinenko" wrote:
> >
> > > Le sam. 12 août 2023, 00:22, Glenn Washburn
> > > a
> > > écrit :
> > >
> > > > T
On Mon, Aug 14, 2023 at 12:47:33AM -0500, Glenn Washburn wrote:
> On Sat, 12 Aug 2023 01:57:42 +0200
> "Vladimir 'phcoder' Serbinenko" wrote:
>
> > Le sam. 12 août 2023, 00:22, Glenn Washburn a
> > écrit :
> >
> > > The backtrace module is written assuming that the frame pointer is in
> > > %ebp
On Sat, 12 Aug 2023 01:57:42 +0200
"Vladimir 'phcoder' Serbinenko" wrote:
> Le sam. 12 août 2023, 00:22, Glenn Washburn a
> écrit :
>
> > The backtrace module is written assuming that the frame pointer is in %ebp.
> > By default, -Os optimization level is used, which enables the gcc option
> >
Le sam. 12 août 2023, 00:22, Glenn Washburn a
écrit :
> The backtrace module is written assuming that the frame pointer is in %ebp.
> By default, -Os optimization level is used, which enables the gcc option
> -fomit-frame-pointer. This break the backtrace functionality. Enabling
> this may cause
The backtrace module is written assuming that the frame pointer is in %ebp.
By default, -Os optimization level is used, which enables the gcc option
-fomit-frame-pointer. This break the backtrace functionality. Enabling
this may cause an unnoticeable performance cost and virtually no size
increase.
