Sun JDK 1.6.0_17 jdb Broken under Fedora 11??
Hard to believe, but that is what it looks like. I would welcome a better explanation though.
I have this dirt simple program that seems to break jdb. That is, I start up the program under jdb, put the execution point at main, say 'next' and the program runs to completion instead of stepping through one high level instruction in the current stack frame! The program is: Code:
What is going on here? Has anyone else encountered a similar problem? Surely nothing in the program should break jdb this badly. I have neither CLASSPATH nor JAVA_HOME set. But I never heard of that causing this problem, either. AFAIK, all of 'java', 'javac' and 'jdb' should show up in the PATH only once, in /usr/bin/java, which in turn points to /etc/alternatives, which in turn points to 'usr/java/jdk1.6.0_17/bin/java' (for example). Or am I confusing jdb with gdb? jdb actually seems to work better if I do NOT compile with the '-g' flag -- necessary for gdb. Is this flag really for 'custom' debug -- whatever that would really mean? |
I have not figure out what has since changed, or whether it was all cockpit error in the first place: but I no longer have the problem.
|
All times are GMT -5. The time now is 11:53 PM. |