This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: backtrace semantics
From: "Carlos O'Donell" <carlos@systemhalted.org>
Date: Sat, 19 Jan 2013 14:28:10 -0500
> On Sat, Jan 19, 2013 at 10:43 AM, David Miller <davem@davemloft.net> wrote:
>>> I'd say you should always list the caller of backtrace() in the frame.
>>>
>>> In gdb when you issue `bt' you always get the caller in the backtrace.
>>
>> Fair enough, I'll fix sparc to match.
>>
>> I hope other port maintainers are paying attention :-)
>
> Don't sound so defeatist. If you really want to be
> different try coming up with some creative counter
> arguments? :-)
>
> As a user *I* want to see all the frames from the point
> at which the function call occurs. It seems most
> logical to me that the frame I'm in should be included.
You don't know what function you're in when you make the backtrace()
call? :-)
That's my argument for not including it.