New version of GDB Macros file

[Joel Sherrill]

Paul Whitfield wrote:
> Greg Marsden wrote:
>> I replaced them with (struct Thread_Control_struct *)  and they work 
>> fine with PPC rtems.
>
I was using these macros to test something for a customer with a VERY 
old RTEMS version
but it appears to also have the Thread_Control_struct so all references 
should just be changed.
It should work for any RTEMS version still in use.  Anyway, I edited the 
script in the Wiki
to fix this.

> Thanks for the tip:
>
> Just for the archives:
>
> That tip got me passed that problem:
>
> Then I had a very mysterious problem with gdb getting very confused
> in the gdb code to show the list of tasks waiting on a semaphore, etc.
>
> In the end the fix was to change the name of the variable $count to $i!
>
For whatever reason this is needed, just edit it in the script and 
change it.
Make sure the change is noted in the header.

> Anyone care to explain that one! - the error I was getting looked like
> gdb was calling my code on the target!
>
> After that I needed to edit the code for stack back trace to be
> Coldfire/68k specific and then it all worked.
>
I don't really know how to deal with this long term except to
make a commented out line for each target.  If you could add your
Coldfire change with a "m68k/Coldfire" comment above it.

Which port uses  gpr1 for the stack pointer.  It it MIPS?    Long lost
information. <sigh>  I don't remember everything anymore.

> Regards
>
> Paul
>
> =========================================================================
> The information in this e-mail is intended for the addressee only.
> Unauthorised use, copying, disclosure or distribution by anyone else
> is prohibited. Please let us know immediately if you receive this
> e-mail in error. Thank you.
> =========================================================================
>