>>>>> "Joe" == Joe Casadonte <[EMAIL PROTECTED]> writes:
Joe> Paul Kinnucan ([EMAIL PROTECTED]) wrote:
>> This is only a debug message formatting problem that I have not
>> gotten around to fixing because it is harmless. It is not the
>> reason you are unable to get the debugger to work. Please submit
>> a problem report.
Joe> Of course, you are right on this one. Silly typo on my part
Joe> was the actual problem. My next problem is that I cannot get
Joe> the -Xdebug option to work with the JVM:
Joe> java -Xdebug foo
Joe> results in the following Doc Watson error in java.exe
Joe> Exception access violation (0x0000005), Address: 0x504a64ca
Joe> What I'm working towards is to be able to attach to a running
Joe> WebLogic process to debug some EJB stuff. If I can do that
Joe> (relatively) easily, I can convert several people in the office
Joe> to Emacs users....
This is a JVM bug. I first came across it on a brand new
dual pentium machine that I had bought to serve a website I had spent
six months writing. The JVM would fall over periodically usually
within 30 seconds of starting an app. Recently I have found this on
another machine where the TogetherJ package falls over immediately
after starting. In the case of my website we got it running on an old
crappy desktop machine running 95 fine. The dual pentium machine is
essentially a door stop as it doesnt do what it was supposed to do.
You might want to track down where the JVM crash is coming
from. It could be from your app (try running it from the command line
with the same options) or from the JVM which emacs is running to do
the debug process.
Im afraid that I cant tell you what the problem is beyond this,
as I never sorted it out despite several months of trying. If you do
find a solution please let me know as I might finally be able to do
something with the machine I bought.
Phil
