Check to see if you have some optimize switches turned on. If so, disable
them in the compile for the debug. Then you can turn them back on afterward.
If your paranoid, then you can just leave the optimizations off. It does
make the code a tiny bit slower but more than that, with all the debug
information, it is easy to rebuild the source code from the objects.
Good luck!
Robert Casto
President - CinciJava LLC
Phone: 513-755-2221
FAX: 831-307-7638
robert@xxxxxxxxxxxxx
-----Original Message-----
From: Brian K Bonner [mailto:brian.bonner@xxxxxxxxxxxx]
Sent: Monday, May 17, 2004 4:19 PM
To: users@xxxxxxxxxx
Subject: [cinjug-users] OS/400 Stack Trace Line Numbers Incorrect
I was wondering if anyone (I'm sure someone is) is doing deployments to
OS/400 5R2? We have a client running Tomcat 4.1.29 on OS/400 5R2 and when
we log a stack trace the line numbers don't match up to our source code.
I'm confident that the code running is the same code we compiled, but for
some reason the line numbers are off.
Has anyone seen anything like this and have an explanation or fix? We're
running JDK 1.4.2_03 (part of the PTFs).
Thanks,
- Brian
---------
You may unsubscribe from this mailing list
by sending a blank email addressed to:
users-unsubscribe@xxxxxxxxxx
--
Find additional help by sending a blank email
addressed to:
users-help@xxxxxxxxxx
|