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 19:19:00 -0000	[thread overview]
Message-ID: <20070619191938.GA26206@caradoc.them.org> (raw)
In-Reply-To: <200706191905.l5JJ5pcj014266@d12av02.megacenter.de.ibm.com>

On Tue, Jun 19, 2007 at 09:05:51PM +0200, Ulrich Weigand wrote:
> One thing I don't quite like is this:
> 
> > +    case TARGET_OBJECT_LIBRARIES:
> > +      if (core_vec->xfer_shared_libraries != NULL)
> > +	return core_vec->xfer_shared_libraries (ops, object, annex, readbuf,
> > +					       writebuf, offset, len);
> 
> I had understood the core_fns method of providing a core file target to
> be deprecated, and in fact I just recently got rid of it for AIX in favour
> of the gdbarch_regset_from_core_section callback ...   I'd prefer this to
> be a gdbarch callback (which would also support core file cross-debugging).

I hadn't even thought about it.  Yes, you're right.

> It looks like the only way to get this to work within the regular solib
> framework would be to actually teach solib.c itself about this form of
> archive members.

Yes, I think you're right.  How about we add an optional member=""
attribute to <library>, and make the common solib.c code open it?
We'd also have to allow .o files.

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?

One thing I've thought of doing is having <section name="blah"
address="blah"/> tags, as an alternative to segment; or they could
have id="N" instead of using section name, or whatever else was
necessary.  So far I haven't needed it, but it would work for
e.g. Linux KGDB which also loads .o files.  Though that's just an
example; actually, for KGDB I'd rather have a bit of Python
distributed with GDB or with the kernel that knows how to list
additional "libraries" :-)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-19 19:19 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 [this message]
2007-06-19 20:00     ` Ulrich Weigand
2007-06-19 20:12       ` Daniel Jacobowitz
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=20070619191938.GA26206@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