Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: "Michael Snyder" <msnyder@vmware.com>, <gdb@sourceware.org>
Subject: RE: GDB for multiple targets
Date: Tue, 09 Dec 2008 18:40:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA069E6C5F@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <200812091811.mB9IBQYV032215@d12av02.megacenter.de.ibm.com>

 
> From: Ulrich Weigand [mailto:uweigand@de.ibm.com] 
> Sent: Tuesday, December 09, 2008 1:11 PM
>
> Except for the target architecture (which is already provided as
> part of the target description) and the osabi, the only remaining
> feature that falls back to a compile-time default is the target
> byte order (as far as I can see).  Now, the byte order fallback
> is only used if the endianness cannot be determined from the
> executable file being debugged, so this should be a rare case.
> However, it would certainly make sense to allow the target to
> provide byte order information in the target description as well.

When using the 'attach' command to debug a process, GDB is able to 
find the executable automatically.  So, I don't actually use the 'file'
command in those cases.  Would GDB still be able to determine the
endianness in those cases?

thanks
Marc


  reply	other threads:[~2008-12-09 18:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 17:09 Marc Khouzam
2008-11-21 19:07 ` Michael Snyder
2008-11-22 15:26   ` Ulrich Weigand
2008-12-09 14:42     ` Marc Khouzam
2008-12-09 18:12       ` Ulrich Weigand
2008-12-09 18:40         ` Marc Khouzam [this message]
2008-12-09 18:44           ` Ulrich Weigand
2008-11-24 16:36 Duane Ellis
2008-11-24 22:03 ` Daniel Jacobowitz
2008-11-25  0:04   ` Duane Ellis
2008-11-25  4:06     ` Daniel Jacobowitz
2008-11-25 17:48       ` Duane Ellis
2008-11-26  2:51         ` Daniel Jacobowitz

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=6D19CA8D71C89C43A057926FE0D4ADAA069E6C5F@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=uweigand@de.ibm.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