Problem with gdb script

[Chris Johns]

Joel Sherrill wrote:
> 
> Where should it go in CVS?  At the moment, I am leaning to
> scripts/gdb but I don't know.
> 

It needs to be a location that we can have the files installed from.

> 
> Way back when I tohught it would be nice to actually add empty
> shells of command and document them.  That way we had a plan
> which allowed people to add to this.
> 

I suspect each command will come out of an itch someone has. If we have 
a frame work then others can add to it. I will see what I come up with.

> 
> No.  I am hoping ot keep it at the gdb macro level and not invoke
> any code on the target.  That seems more portable and safer.
> 

Agreed, now ever GDB macros will run much slower. I suppose this is ok 
for debugging.

> 
> That makes one this week. :)
> 

Sorry to disappoint, but I have changed my mind. I think the macros are 
better in the RTEMS source code as they can changed based on a change in 
RTEMS. Having to update GDB packages because of a script change does not 
seem the correct thing to do.

-- 
  Chris Johns, cjohns at cybertec.com.au