Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: tromey@redhat.com
Cc: rnk@mit.edu (Reid Kleckner),
	gdb-patches@sourceware.org,
	        unladen-swallow@googlegroups.com
Subject: Re: [RFA] Add interface for registering JITed code
Date: Fri, 24 Jul 2009 13:25:00 -0000	[thread overview]
Message-ID: <200907241130.n6OBUwMe004564@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <m3y6qf9tz7.fsf@fleche.redhat.com> from "Tom Tromey" at Jul 23, 2009 11:42:20 AM

Tom Tromey wrote:

> >>>>> "Reid" == Reid Kleckner <rnk@mit.edu> writes:
> 
> Reid> So that means we need LLVM to generate dwarf debug info, and we
> Reid> need to register it with GDB.
> 
> Nice.
> 
> Your overall approach seems good to me.

I agree, this looks good to me as well.

> Reid> +      /* Hack to work around the fact that BFD does not take ownership of the
> Reid> +         memory for files allocated in memory.  */
> 
> Is it possible to fix this directly in BFD?  Since...
> 
> Reid> +        bim = (struct bfd_in_memory *) objfile->obfd->iostream;
> 
> ... this is definitely fishy :-)

I'd suggest that Reid instead use bfd_openr_iovec to access an ELF image
directly in inferior memory, as is currently done e.g. by
  remote.c:remote_bfd_open
  spu-linux-nat.c:spu_bfd_open
  solib-spu.c:spu_bfd_open (is about to be introduced by the patch
  http://sourceware.org/ml/gdb-patches/2009-07/msg00546.html)
This works without BFD changes or directly accessing BFD internals ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2009-07-24 11:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  1:58 Reid Kleckner
2009-07-23 12:08 ` Reid Kleckner
2009-07-23 23:21 ` Tom Tromey
2009-07-24 13:25   ` Ulrich Weigand [this message]
2009-07-24 16:52     ` Doug Evans
2009-07-25  0:40     ` [unladen-swallow] " Reid Kleckner
2009-07-24 16:55   ` Reid Kleckner
2009-07-24 20:42     ` Eli Zaretskii
2009-07-24 20:55       ` Tom Tromey
2009-07-25 15:29         ` Eli Zaretskii
2009-07-27 23:20           ` Reid Kleckner
2009-07-28 20:20             ` Eli Zaretskii
2009-07-28 22:23               ` Reid Kleckner
2009-07-29 15:20                 ` Eli Zaretskii
2009-07-24 21:06     ` Tom Tromey
2009-07-25  0:23       ` Reid Kleckner
2009-07-30 16:30         ` Tom Tromey
2009-07-30 16:54           ` Tom Tromey
2009-08-05 21:05             ` [unladen-swallow] " Reid Kleckner
2009-07-30 21:10           ` Thiago Jung Bauermann
2009-07-31 18:18             ` Thiago Jung Bauermann
2009-07-31 20:31               ` [unladen-swallow] " Reid Kleckner
2009-08-01 14:43                 ` Thiago Jung Bauermann
2009-08-14 19:29                 ` Tom Tromey
2009-08-14 23:37                   ` Reid Kleckner
2009-08-17 15:31                     ` Tom Tromey
2009-08-20 18:22                       ` Doug Evans
2009-08-21 15:17                         ` Ken Werner
2009-08-21 16:31                           ` Doug Evans
2009-08-21 18:59                             ` Ken Werner
2009-08-21 19:53                               ` Doug Evans
2009-07-31 20:55               ` Paul Pluzhnikov

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=200907241130.n6OBUwMe004564@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=rnk@mit.edu \
    --cc=tromey@redhat.com \
    --cc=unladen-swallow@googlegroups.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