This is the mail archive of the
mailing list for the glibc project.
Re: backtrace semantics
>> 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.
Hm. Interesting discussion. What do you think about python like
strategy? That said,
application always dump backtrace when any unexpected thing was happen and
application user (not app creator) see it. At this time, current frame
is most useful
I'm not sure there is such application in real world. _I_ only uses
backtrace() for debugging.
I only says I'm not sure every people use it for only debugging.