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: where do stack traces get filled in?


>>>>> "Adam" == Adam Megacz <gcj@lists.megacz.com> writes:

Adam> Are backtraces a target-specific thing (which would have to be
Adam> rewritten for win32), or would I be able to do some clever
Adam> cut-and-paste out of glibc? Or is this impossible with SJLJ
Adam> exceptions?

Adam> Well, I guess there's licensing issues with glibc (LGPL vs
Adam> GPL-with-exception); perhaps "review the glibc code, learn how
Adam> it works, and then reimplement the same algorithm".

I don't really know what exactly would have to be done.
For all I know there is some Win32 API you could use here.

Occasionally we've discussed being able to find the backtraces using
information that is already around, for instance exception-handling
info.  We need a more powerful approach because we need to be able to
find the classes whose methods are on the stack; this is used by some
of the Java security features we don't implement.

Tom


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