Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: uweigand@de.ibm.com, brobecker@adacore.com, teawater@gmail.com,
		gdb-patches@sourceware.org, msnyder@vmware.com
Subject: Re: [RFA] Check solib bfd arch
Date: Fri, 18 Sep 2009 14:39:00 -0000	[thread overview]
Message-ID: <20090918143909.GA10099@caradoc.them.org> (raw)
In-Reply-To: <200909181407.n8IE7ktV013370@brahms.sibelius.xs4all.nl>

On Fri, Sep 18, 2009 at 04:07:46PM +0200, Mark Kettenis wrote:
> I suppose we needsto add the necessary magic to sparc-sol-nat.c to set
> the proper architecture.  I'll need to figure out how to extract that
> information from the system.  Is it possible to create a target
> description that just contains the architecture and not all the
> register stuff?

Yes, this is easy.  If there aren't any registers, the register bits
will be disabled.  The XML version would be something like:

<!DOCTYPE target SYSTEM "gdb-target.dtd">
<target>
  <architecture>sparc:sparcv9</architecture>
  <osabi>Solaris</osabi>
</target>

The C version could be generated from that, or if you want to do it
dynamically:

  struct target_desc *result = allocate_target_description ();
  set_tdesc_architecture (result, my_bfd_arch_info_ptr);

After that, mips_linux_read_description is a simple example of how to
supply the description.

I suspect the check is going to be problematic whether we do this or
not, though.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2009-09-18 14:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  9:52 Hui Zhu
2009-07-05 21:36 ` Ulrich Weigand
2009-07-06  3:03   ` Hui Zhu
2009-07-07 16:45     ` Ulrich Weigand
2009-07-08  2:46       ` Hui Zhu
2009-07-09 13:43         ` Ulrich Weigand
2009-07-09 16:50           ` Hui Zhu
2009-09-17 22:56         ` Joel Brobecker
2009-09-18  5:05           ` Hui Zhu
2009-09-18 12:50           ` Ulrich Weigand
2009-09-18 13:06             ` Ulrich Weigand
2009-09-18 13:10             ` Daniel Jacobowitz
2009-09-18 14:24               ` Joel Brobecker
2009-09-18 14:08             ` Mark Kettenis
2009-09-18 14:11               ` Mark Kettenis
2009-09-18 14:39               ` Daniel Jacobowitz [this message]
2009-09-18 14:53                 ` Pedro Alves
2009-09-18 16:14                   ` Ulrich Weigand
2009-09-18 16:25                     ` Daniel Jacobowitz
2009-09-18 16:41                       ` Pedro Alves
2009-09-18 16:44                         ` Daniel Jacobowitz
2009-09-18 16:45                         ` Pedro Alves
2009-09-18 17:17                           ` Joel Brobecker
2009-09-18 20:43                             ` Joel Brobecker
2009-09-22 23:04           ` Joel Brobecker

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=20090918143909.GA10099@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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