At 08:17 PM 2/3/00 +0000, Larry Riedel wrote:
>
>> > -> Fire up xemacs 21.x with JDE 2.1.6b17
>> > -> M-x jde-bug-start-debugger
>> > -> M-x jde-bug-attach-local-host
>> > -> M-x jde-bug-set-target-process
>> > -> M-x jde-bug-show-threads
>> >
>> > From looking at the code, it appears the "state" of the "process"
>> > is set to "unknown", which causes jde-dbs-target-process-runnable-p
>> > to return nil. I don't know why the state is "unknown" or if that
>> > is correct or what.
>>
>> Try suspending the attached process first (JDEbug->Processes->Suspend).
>> The attached process is not suspended when the attach occurs, it's
>> merely waiting for something to happen, user input, debugger input,
>> anything. Most debug commands will not work on a non-suspended
>> process. So you have to suspend it first.
>
>I did try that (jde-bug-suspend-process), and it seemed to be
>successful because the debugger process window said "All threads
>suspended", but it had no effect on the main problem of "No target
>process or process is not suspended".
>
>I can go directly to the *JDEbug* window and say "1 2 get_threads"
>and it will show me the thread list. I think jde-bug-show-threads
>would wind up doing that same command, but it does not get
>that far because jde-bug-show-threads bails out when it see that
>jde-dbs-target-process-runnable-p is returning nil, which I think
>is because the "state" of the "process" is set to "unknown", and I
>am not sure what is up with that.
>
Yep, you're right. This is a bug. I will fix this right away and get out a
new release. I'll also add a Display->Thread command which will show the
stack for any thread. Ultimately, my plan is to have a "GUI" that displays
the stack and allows you to click on any stack frame and go to the source
for that stack frame. The Display->Thread command is a stopgap until i can
get the full functionality implemented.
- Paul
