[freenet-tech] Technology / Features

Thu Feb 28 16:08:00 GMT 2002

Jeff Sturm wrote:
>On 28 Feb 2002, Adam Megacz wrote:
>>>Interestingly, why does gcj use DWARF2 info to generate stack traces
>>on Linux instead of just doing this?
>>
Because it runs on CPUs other than x86, and we don't want to write a 
backtrace function for every single architechture out there ;-)
>It doesn't. It uses the backtrace function from glibc.
>>However backtrace doesn't work on a few targets (alpha) where we can't
>walk the stack. For those we could possibly use libunwind, which I
>haven't closely examined yet. And libunwind is based on DWARF2.
>
RTH said the EH unwinder could easily be modified to fill out a stack 
trace without actually unwinding, so this is what we should do for 
targets using DWARF2 exceptions.
regards
Bryce.