This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: [freenet-tech] Technology / Features
- From: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
- To: Jeff Sturm <jsturm at one-point dot com>
- Cc: Adam Megacz <gcj at lists dot megacz dot com>, java at gcc dot gnu dot org
- Date: Fri, 01 Mar 2002 13:07:02 +1300
- Subject: Re: [freenet-tech] Technology / Features
- References: <Pine.LNX.4.10.10202281848240.30889-100000@mars.deadcafe.org>
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.