At 11:10 PM 4/18/2001 -0400, you wrote: > >Please enter the details of your bug report here > >I'm having trouble starting JDEbug. I've used it in the past with great >results, but I've not been able to get it to work lately. > Some people have this same trouble. Others do not. Unfortunately, I am one of the ones that has no trouble starting the JDE on any platform that I use. Thus, it is impossible for me to debug it. I have described this problem and discussed it at length on the JDE mailing list many times in the past year and many times in the past month. If you're interested, read the mailing list archives. This problem is only going to be solved in one of two ways: somebody who has this problem takes the initiative to debug it (has yet to happen since I first got reports on this bug a year ago) or I stumble upon a fix by accident. A couple of days ago I discovered quite by accident a subtle bug in the JDE function that parses messages from the debugger. This bug causes messages that have back slashes in them to be parsed incorrectly and the result is that the JDE thinks the debugger has not responded when it actually has. I experience this bug when trying to get the value of a local char variable whose value is a backslash. It is possible that this bug, which I have fixed, may be causing the startup problem, though it is not obvious to me why it would because AFAIK there are not any backslashes in the startup messages. Anway, I plan to include the fix in the next release so you can test it if you like. - Paul
