From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jan.kratochvil@redhat.com
Cc: sanjoy@playingwithpointers.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 5/6] New JIT unwinder.
Date: Sat, 20 Aug 2011 18:30:00 -0000 [thread overview]
Message-ID: <201108201829.p7KITqt7024731@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20110820175838.GC26447@host1.jankratochvil.net> (message from Jan Kratochvil on Sat, 20 Aug 2011 19:58:38 +0200)
> Date: Sat, 20 Aug 2011 19:58:38 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> > +
> > + inf_data = get_jit_inferior_data ();
> > +
> > + callbacks.reg_get = jit_unwind_reg_get_impl;
> > + callbacks.reg_set = jit_unwind_reg_set_impl;
> > + callbacks.target_read = jit_target_read_impl;
>
> Couldn't GDB just export these functions to the plugin without having to use
> the callbacks vector? Python does so, libthread_db does so (see
> proc-service.list).
I'd say that's a bad idea. The --dynamic-list linker option isn't
uniformly available, and even -rdynamic may not work everywehere.
next prev parent reply other threads:[~2011-08-20 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 6:26 JIT Reader (re-roll) Sanjoy Das
2011-08-20 6:26 ` [PATCH 1/6] Introduce header (jit-reader.in) and modify build system Sanjoy Das
2011-08-20 18:04 ` Jan Kratochvil
2011-08-20 18:18 ` Sanjoy Das
2011-08-20 6:27 ` [PATCH 2/6] Platform agnostic dynamic loading code Sanjoy Das
2011-08-20 6:27 ` [PATCH 3/6] New commands for loading and unloading a reader Sanjoy Das
2011-08-20 8:24 ` Eli Zaretskii
2011-08-20 17:31 ` Jan Kratochvil
2011-08-20 6:27 ` [PATCH 5/6] New JIT unwinder Sanjoy Das
2011-08-20 17:59 ` Jan Kratochvil
2011-08-20 18:30 ` Mark Kettenis [this message]
2011-08-20 19:45 ` Jan Kratochvil
2011-08-30 17:53 ` Tom Tromey
2011-08-20 6:33 ` [PATCH 6/6] Documentation Sanjoy Das
2011-08-20 8:34 ` Eli Zaretskii
2011-08-20 6:33 ` [PATCH 4/6] Use the loaded reader Sanjoy Das
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=201108201829.p7KITqt7024731@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=sanjoy@playingwithpointers.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