On 09-02-19 22:07, Ian Lance Taylor wrote:
> On Fri, Feb 8, 2019 at 9:26 AM Thomas Schwinge
> wrote:
>>
>> On Fri, 8 Feb 2019 10:41:47 +0100, Tom de Vries wrote:
>>> The backtrace functions backtrace_full, backtrace_print and backtrace_simple
>>> walk the call stack, but make sure to skip the fi
On 09-02-19 22:07, Ian Lance Taylor wrote:
> On Fri, Feb 8, 2019 at 9:26 AM Thomas Schwinge
> wrote:
>>
>> On Fri, 8 Feb 2019 10:41:47 +0100, Tom de Vries wrote:
>>> The backtrace functions backtrace_full, backtrace_print and backtrace_simple
>>> walk the call stack, but make sure to skip the fi
On Fri, Feb 8, 2019 at 9:26 AM Thomas Schwinge wrote:
>
> On Fri, 8 Feb 2019 10:41:47 +0100, Tom de Vries wrote:
> > The backtrace functions backtrace_full, backtrace_print and backtrace_simple
> > walk the call stack, but make sure to skip the first entry, in order to skip
> > over the functions
On 08-02-19 18:25, Thomas Schwinge wrote:
> Hi Tom!
>
> On Fri, 8 Feb 2019 10:41:47 +0100, Tom de Vries wrote:
>> The backtrace functions backtrace_full, backtrace_print and backtrace_simple
>> walk the call stack, but make sure to skip the first entry, in order to skip
>> over the functions them
Hi Tom!
On Fri, 8 Feb 2019 10:41:47 +0100, Tom de Vries wrote:
> The backtrace functions backtrace_full, backtrace_print and backtrace_simple
> walk the call stack, but make sure to skip the first entry, in order to skip
> over the functions themselves, and start the backtrace at the caller of th
On Fri, Feb 8, 2019 at 10:41 AM Tom de Vries wrote:
>
> Hi,
>
> The backtrace functions backtrace_full, backtrace_print and backtrace_simple
> walk the call stack, but make sure to skip the first entry, in order to skip
> over the functions themselves, and start the backtrace at the caller of the