Yes, the invalid stack frame message disappears automatically after a while, so everything is okay there. Now I just got the problem that JDEBug is SLOW, so if anyone got any idea how I can speed it up, I would be grateful. I have a client application which communicates with a J2EE server and a mom broker, it normally takes about 10 sekunds to start up, but when I start it up in debug mode it can take anything between 5 and 15 minuttes! I can from my task manager see that emacs constantly uses anything between 70 and 90 pct. cpu and about 35 mb ram, java uses 2 or 3 pct cpu and about 25 mb ram.
Any help or tips would be much appreciated Henrik ----- Original Message ----- From: "Henrik Kj�r" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Troy Daniels" <[EMAIL PROTECTED]> Sent: Tuesday, November 04, 2003 9:20 PM Subject: Re: JDEBug - Invalid stack frame > Thanx Trey. > > For some reason JDEBug breaks at my first breakpoint, but the line did not > get read and nothing get in my JDEBug window except the exception!? > Anyway, I just set another breakpoint in the next line and C-c C-z C-c > (continue) and then I get something in my window - nice :-) > > Henrik > > > ----- Original Message ----- > From: "Troy Daniels" <[EMAIL PROTECTED]> > To: "Henrik Kj�r" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Tuesday, November 04, 2003 9:00 PM > Subject: Re: JDEBug - Invalid stack frame > > > At 08:47 PM 11/4/2003 +0100, Henrik Kj�r wrote: > > >I am trying to use JDEBug for debugging, but I am not having much success. > >When I start debugging my JDEBug opens nicely, but displays an "Invalid > >stack frame" message with red in the buttom of the window, and the window > >has no content at all. > > > >Any idea!? > > That's actually "normal" operation. The window is part of a rudimentary > GUI, that is a recent addition. It currently only shows the value of local > variables. The error message is because, when the debugger starts, it > sometimes tries to update the local variable display when the process isn't > suspended. That causes an exception, which is reported in red. In my > environment, the message usually goes away quickly. > > Try setting a breakpoint (C-c C-z C-b) in your program on a line after > local variables are defined. The line should be green after you set the > breakpoint and turn red after you start the JDEbug. When the program gets > to that line, the error message should disappear, and the window should > show the local variables in a tree view. > > Troy > > > >
