This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Idea for stack traces

From: Adam Megacz <gcj at lists dot megacz dot com>
To: java at gcc dot gnu dot org
Date: 09 Mar 2002 00:16:41 -0800
Subject: Re: Idea for stack traces
Organization: Myself
References: <3C88EE69.5080506@waitaki.otago.ac.nz> <15496.63468.299976.719150@cuddles.cambridge.redhat.com>

Andrew Haley <aph@cambridge.redhat.com> writes:
> libgcj would not be so very hard, and we could arrange for this info
> to be emitted even on targets that don't use DWARF by default.

Is DWARF the kind of thing that takes extra effort to get working on
new platforms, or is it high enough up in the front end that it just
automatically works when a new backend is added?

I'm thinking mainly in terms of mingw, which does not use DWARF. Is
there some simple way to get gcc to emit DWARF info for this target?

  - a

-- 
"If I put copyrighted material into the 'chewy nougat center', I can
 claim the crunchy chocolate coating is an 'Access Control
 Mechanism'."                                     --lynx_user_abroad

Why Windows NT/2k/XP is unreliable: www.zappadoodle.com

References:
- Idea for stack traces
  - From: Bryce McKinlay
- Idea for stack traces
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]