|
Bug ID:
|
4666440
|
|
Votes
|
0
|
|
Synopsis
|
Cannot debug inside constructor
|
|
Category
|
forte4j:kjava
|
|
Reported Against
|
4_fcs
|
|
Release Fixed
|
|
|
State
|
11-Closed,
Will Not Fix,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
11-APR-2002
|
|
Description
|
build 020410
Place breakpoint into MIDlet's constructor. Debugger doesn't stop at the breakpoint.
Workaround exists: Place code from constructor into method and place breakpoint into method.
|
|
Work Around
|
Use JDK1.3.x to debug application
|
|
Evaluation
|
We found that this bug occures only under JDK1.4. Neither NB nor kjava bug. JDK1.4 JDB does not work. Probably JDK bug.
xxxxx@xxxxx 2002-04-18
It is definitely a problem between emulator and JDK 1.4. JDI used ReferenceType and index (int) to describe a method. emulator uses numbers 0-n. JDK 1.4 treats methods with index 0 as obsoleted (I don't know why). J2SE uses bigger numbers (like 9856136) so the problem doesn't occur when debugging J2SE application.
It is obsolete bug now. Closing
xxxxx@xxxxx 2004-08-05
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
