[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jdt-debug-dev] Java debugger shows arg0, arg1 instead of the real name of a method parameters
|
Thanks, Darin.
But I checked with my colleague, and he did have this checkbox checked.
Thanks,
Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx
Darin
Wright/Ottawa/IBM
@IBMCA To
Sent by: "Eclipse JDT Debug developers
jdt-debug-dev-bou list." <jdt-debug-dev@xxxxxxxxxxx>
nces@xxxxxxxxxxx cc
Subject
04/10/2006 05:48 Re: [jdt-debug-dev] Java debugger
PM shows arg0, arg1 instead of the
real name of a method parameters
Please respond to
"Eclipse JDT
Debug developers
list."
Local variable names are optional based on debug attribues generated when
compiling class files. See the "Java > Compiler" preference page:
"Add variable attributes to generated class files (used by the
debugger)"
It sounds like this option is turned off. When var names are missing, we
give them generated names arg0, etc.
Darin Wright
Xuan
Chen/Toronto/IBM@IBMCA
To
Sent by: "Eclipse JDT Debug developers list."
jdt-debug-dev-bounces@ <jdt-debug-dev@xxxxxxxxxxx>
eclipse.org cc
Subject
04/10/2006 04:03 PM [jdt-debug-dev] Java debugger shows
arg0, arg1 instead of the real name
of a method parameters
Please respond to
"Eclipse JDT Debug
developers list."
Hi,
I have a question about the debugger behaviour in RAD 6.0 when debugging a
web application running in WAS 5.1 test environment. I am not sure if this
is the right mailing list for this type of question. If not, please point
me to the right mailing list. Thanks.
One of my colleagues is developing a web application inside RAD 6.0. He
created a web project, and linked the source folder to a specific
directory. Then he debugged his web application inside WAS5.1 test
environment. But he noticed that all the arguments were shown as arg0,
arg1, arg2, etc, instead of the real name of the parameters. Just
wondering what could be the possible cause of this behaviour? Please
notice those methods are from his source code, not the ones from WAS
runtime or JRE code.
Thanks,
Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx
_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-debug-dev
_______________________________________________
jdt-debug-dev mailing list
jdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-debug-dev