[U-Boot-Users] Are there any users of tools/gdb/astest.c?

[U-Boot-Users] Are there any users of tools/gdb/astest.c?

[Detlev Zundel]

Hi,

looking through the mailing list archive, it becomes clear that the
mentioned "tools/gdb/astest.c" posed (in my view unnecessary)
problems for some U-Boot newcomers that stopped them from compiling the
main U-Boot code.

My question therefore is, does anyone still use this code or has it
been obsoleted by binutils?

Looking through the code it seems like it dumps ELF file infos for the
hard-coded "elf32-powerpc" BFD target so it is of limited use only to
the newly supported architectures anyway.

If anyone wants to keep the file then please speak up, otherwise I'd
like to ask Wolfgang to remove it so there is one less obstacle for
new users of U-Boot.

Thanks
  Detlev

-- 
You get 3 opportunities to advertise your Rock band, no more.
           -- Proposed Symbolics guidelines for mail messages (1984)

[U-Boot-Users] Re: Are there any users of tools/gdb/astest.c?

[Murray Jensen]

On 05 Aug 2003 18:33:54 +0200, Detlev Zundel <dzu@denx.de> writes:
>If anyone wants to keep the file then please speak up, otherwise I'd
>like to ask Wolfgang to remove it so there is one less obstacle for
>new users of U-Boot.

I was responsible for the gdb directory being there - long time ago early in
the ppcboot days - when the board I was using had no ethernet and no flash
(really!). I would burn ppcboot into an EPROM, then use gdb to download a linux
kernel over the serial line and debug it the same way if it crashed (with kgdb).
Wasn't too bad at 230400 baud. But I stopped using these tools many years ago.

astest was just a little hack that printed some info I needed - it could
definitely go. In fact, the whole gdb directory could probably go, although
I suppose it might be useful to someone/somewhere/sometime. Cheers!
								Murray...
-- 
Murray Jensen, CSIRO Manufacturing & Infra. Tech.      Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia.         Fax: +61 3 9662 7853
Internet: Murray.Jensen at csiro.au

Hymod project: http://www.msa.cmst.csiro.au/projects/Hymod/

To the extent permitted by law, CSIRO does not represent, warrant and/or
guarantee that the integrity of this communication has been maintained or
that the communication is free of errors, virus, interception or interference.

The information contained in this e-mail may be confidential or privileged.
Any unauthorised use or disclosure is prohibited. If you have received this
e-mail in error, please delete it immediately and notify Murray Jensen on
+61 3 9662 7763. Thank you.

[U-Boot-Users] Re: Are there any users of tools/gdb/astest.c?

[Detlev Zundel]

Hi Murray,

> astest was just a little hack that printed some info I needed - it could
> definitely go. In fact, the whole gdb directory could probably go, although
> I suppose it might be useful to someone/somewhere/sometime. Cheers!

Thanks for the info.  It just appeared to me that my intention of
not stopping new users could also be accomplished by simply separating
a "gdbtools" make target from the "make all" target.  This way the
code would be preserved but it won't stop anyone on compilation
problems.

Wolfgang, what do you think?

Cheers
  Detlev

-- 
Indeed, the author firmly believes that the best serious work is also
good fun.   We needn't apologize if we enjoy doing research.
                                        -- Donald Knuth

[U-Boot-Users] Re: Are there any users of tools/gdb/astest.c?

[Wolfgang Denk]

In message <87znilu9ep.fsf@deepthought.outer.space.org>
Detlev Zundel wrote:

> > astest was just a little hack that printed some info I needed - it could
> > definitely go. In fact, the whole gdb directory could probably go, although
> > I suppose it might be useful to someone/somewhere/sometime. Cheers!
> 
> Thanks for the info.  It just appeared to me that my intention of
> not stopping new users could also be accomplished by simply separating
> a "gdbtools" make target from the "make all" target.  This way the
> code would be preserved but it won't stop anyone on compilation
> problems.
> 
> Wolfgang, what do you think?

Let's do both: remove the astest.c file as the same can be done using
standard tools (bjdump), and remove the  tools/gdb  target  from  the
default build sequence (so build time will improve).

Detlev, can you please do this and check it in?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
"I haven't lost my mind - it's backed up on tape somewhere."

[U-Boot-Users] Re: Are there any users of tools/gdb/astest.c?

[Detlev Zundel]

Hi Wolfgang,

> Let's do both: remove the astest.c file as the same can be done using
> standard tools (bjdump), and remove the  tools/gdb  target  from  the
> default build sequence (so build time will improve).
> 
> Detlev, can you please do this and check it in?

Done.

There's now a new top-level make target "gdbtools" which only
compiles the tools/gdb directory which is not included in the "all"
target anymore.

Cheers
  Detlev

-- 
Peace of mind isn't at all superficial to technical work.  It's the
whole thing.   That which  produces it is good work  and that which
destroys it is bad work.
                                        -- Robert M. Pirsig