Re: [PATCH] Fix annoying startup srcbar bug

[Keith Seitz <keiths at redhat dot com>]

On Mon, 4 Jun 2001, Fernando Nasser wrote:

> Keith,
>
> Have you tried this with remote targets?

Nope.

> Some of us tried this some time ago and we've got side-effects.  It has
> been some time so I don't remember exactly but I vaguely recall it had
> something to do with remote targets...
>
> P.S.: I am now remembering something about having to add something to
> make them active again after you connect to a board, but if it is doing
> the right thing after you attach it is probably all right.  It can also
> be a problem that only existed in the old code and I did not try to turn
> then off after the rewrite --  I am not sure.

Hmmm. I tried:

$ gdb gdb GDB_PID

and

$ gdb
File->Open... gdb
Run->Attach... gdb

In both cases, the gui came up with the proper run state. If Insight does
NOT come up with the proper run state, then the variable "gdb_running"
(one of the globals I am trying to get rid of!) is not correct. When this
happens, 99 times of 100, it is because inferior_pid is zero.

I've found several toolchains where inferior_pid is set to the thread id
"0". This really breaks things. Both gdb and insight use "inferior_pid==0"
as a test for "is there a running process?"

This should be all "fixed" now that Kevin has checked-in his pid/tid
changes, since he explicitly defines null_ptid to indicate that there is
no inferior.

Keith