This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: multi-arch debug doesn't dump definitions as requested
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Richard dot Earnshaw at arm dot com
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 07 Feb 2002 21:38:02 -0500
- Subject: Re: multi-arch debug doesn't dump definitions as requested
- References: <200202061733.RAA03457@cam-mail2.cambridge.arm.com>
> According to
> http://sources.redhat.com/gdb/papers/multi-arch/howto.html
>
> Rebuild and then run GDB vis:
>
> gdb/gdb
> (gdb)
> (gdb) set archdebug 1
> (gdb) file x-y-z
> ....
>
> If all goes well, gdb will report the current value of all the
> architecture dependent macro's. At this stage must are still
> being taken from hardwired definitions in your
> tm-XXX.h file. Failing that, an internal error message
> reporting an uninitialised architecture vector member will be
> reported.
>
> Except that that doesn't happen. All I get is
>
> (gdb) set archdebug 1
> Warning: command 'set archdebug' is deprecated.
> Use 'set debug arch'.
>
> (gdb) file gdb
> gdbarch_update: info.bfd_arch_info arm
> gdbarch_update: info.byte_order 1 (little)
> gdbarch_update: info.abfd 0x1d2e00
> gdbarch_update: info.tdep_info 0x0
> gdbarch_update: Architecture 0x001d3000 (arm) unchanged
> Reading symbols from gdb...done.
>
> Note, "set debug arch 1" doesn't do anything different either.
>
> How about a "maint" (or maint info) command?
Try:
(gdb) maint print architecture [ <savefile> ]
and look at sizeof.exp.
The lack of output comes, at least in part, because it isn't possible to
print the macros/values safely.
Andrew