Stack tracing on Linux ?

[Georg Wrede]

Fawzi Mohamed wrote:
> On 2009-04-03 19:24:25 +0200, Christopher Wright <dhasenan at gmail.com> said:
> 
>> Georg Wrede wrote:
>>> Fawzi Mohamed wrote:
>>>> Well inlined functions will have no frame, also last call 
>>>> optimization (tail optimization) removes the frame.
>>>
>>> If I were to write a compiler, then using "-g -debug", etc. would 
>>> make sure neither happens!
>>
>> However, closures in D1 have a stack frame that is within the creating 
>> function's stack frame, and gdb assumes that means a corrupt stack. 
>> There's no real way around this.
> 
> Now this is more clear, thanks!

If the current D closure architecture is considered stable and 
permanent, then maybe the gdb or glibc folks might want to look at it?

And while at it, they'd probably know right off the bat what seems to be 
the problem with D stack traces not currently showing properly.