This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


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

Re: [patch] java run-time stack trace


Per Bothner writes:
 > Bryce McKinlay <bryce@albatross.co.nz> writes:
 > 
 > > Actually, I'd like to have CNI functions mangled in C++ style. This is
 > > how they are written in the source code (think copy/search/paste), and it
 > > can help to make it very obvious when the stack trace goes through native
 > > code. Also, this is consistent with GDB.
 > 
 > What about library functions?  Having (say) ClassLoader.defineClass
 > should up in C++ style is *not* what most users want or expect.
 > Whether a class is written in Java or CNI is an implementation detail,
 > which should not effect how the stack trace looks, at least for standard
 > java.* and javax.* classes.

I'm sure this is right.  What bothers me is how java demangling can
possibly cope with things like array<int>.

Andrew.

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