On Mar 29, 12:40 pm, pel...@yahoo.com wrote:
> I have a method that logs on entry (based on a flag), and I would like
> to be able to identify the caller in the trace. Now, I can use
[quoted text clipped - 7 lines]
> This code does not have to be very efficient, as it will only be
> turned on rarely in fault isolation. Any help is greatly appreciated.
If I don't mention very special debugging facilities which I do not
know in their details, the plain default JVM or running objects does
not have names of object references nor other names used in the source
code. Names are only handles for compiler to do its work. In thread
dump gotten from Ctrl\ or CtrlBrk, we only see hex address values.
Lew - 29 Mar 2007 13:23 GMT
> If I don't mention very special debugging facilities which I do not
> know in their details, the plain default JVM or running objects does
> not have names of object references nor other names used in the source
> code. Names are only handles for compiler to do its work. In thread
> dump gotten from Ctrl\ or CtrlBrk, we only see hex address values.
Huh, that's funny, you don't see class names and the like? Maybe the "-g"
compilation option would help.
-- Lew
SadRed - 30 Mar 2007 00:11 GMT
> > If I don't mention very special debugging facilities which I do not
> > know in their details, the plain default JVM or running objects does
[quoted text clipped - 6 lines]
>
> -- Lew
OP is not talking about class name and not the debugger
information. He just wants to see object reference names on stack
trace.