From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard.Earnshaw@arm.com, gdb@sources.redhat.com
Subject: Re: multi-arch debug doesn't dump definitions as requested
Date: Fri, 08 Feb 2002 02:22:00 -0000 [thread overview]
Message-ID: <200202081021.KAA01070@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Thu, 07 Feb 2002 21:38:02 EST." <3C633A0A.1040906@cygnus.com>
>
> 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
Thanks. Shouldn't http://sources.redhat.com/gdb/papers/multi-arch/howto.ht
ml be updated to show this. At present it says:
Add:
#ifndef GDB_MULTI_ARCH
#define GDB_MULTI_ARCH 1
#endif
to the top of your tm-XXX.h file. 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. ...
next prev parent reply other threads:[~2002-02-08 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 9:34 Richard Earnshaw
2002-02-07 18:38 ` Andrew Cagney
2002-02-08 2:22 ` Richard Earnshaw [this message]
2002-02-08 2:41 ` Pierre Muller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202081021.KAA01070@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox