stack traces on fedora and mingw

Per Bothner
Mon Mar 1 18:34:00 GMT 2004

Can someone summarize the status of printStackTrace and what's wrong?

(1) On Fedora GNU/Linux CVS head prints a mangled stack trace.  The
documentation says the default is demangled.  What happened?

(2) On MinGW CVS head prints a stack trace with just hex addresses.
Is this likely to get fixed?  Is there a work-around?  Is there a
version of gdb that could be used to get real traces?

Thanks for any advice/information.
	--Per Bothner

More information about the Java mailing list