Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: multi-arch debug doesn't dump definitions as requested
Date: Thu, 07 Feb 2002 18:38:00 -0000	[thread overview]
Message-ID: <3C633A0A.1040906@cygnus.com> (raw)
In-Reply-To: <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







  reply	other threads:[~2002-02-08  2:38 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 [this message]
2002-02-08  2:22   ` Richard Earnshaw
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=3C633A0A.1040906@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=Richard.Earnshaw@arm.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