Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <pedro_alves@portugalmail.pt>
Subject: Re: For example only, updated Windows DLL support and gdbserver 	DLL         support
Date: Tue, 19 Jun 2007 20:12:00 -0000	[thread overview]
Message-ID: <20070619201223.GA29049@caradoc.them.org> (raw)
In-Reply-To: <200706192000.l5JK0ZVU014446@d12av02.megacenter.de.ibm.com>

On Tue, Jun 19, 2007 at 10:00:35PM +0200, Ulrich Weigand wrote:
> That sounds reasonable.  The member name would presumably also
> have to be added to so_list ...

Yeah.

> > I'm not sure how much trouble you'll have reporting the correct
> > relocations for an object file.  Do you get something based on
> > sections, or do AIX object files have a fixed number of segments?
> 
> XCOFF seems to be a bit limited in that respect, I understand there
> is just "Text" and "Data".  The AIX ldinfo structure provides:

Perfect.  Then GDB's xcoff reader can report that the object file has
two "segments", one text and one data.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-19 20:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 15:08 Daniel Jacobowitz
2007-06-18 21:07 ` Christopher Faylor
2007-06-18 21:12   ` Daniel Jacobowitz
2007-06-18 21:54     ` Pedro Alves
2007-06-18 23:28       ` Christopher Faylor
2007-06-19 19:06 ` Ulrich Weigand
2007-06-19 19:19   ` Daniel Jacobowitz
2007-06-19 20:00     ` Ulrich Weigand
2007-06-19 20:12       ` Daniel Jacobowitz [this message]
2007-06-19 22:43         ` Pedro Alves
2007-06-19 23:34           ` Daniel Jacobowitz
2007-06-19 23:58             ` Pedro Alves

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=20070619201223.GA29049@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    --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