From: Andrew Cagney <cagney@gnu.org>
To: Roland McGrath <roland@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [KLUDGE PATCH] Linux vsyscall DSO support
Date: Thu, 08 Apr 2004 21:30:00 -0000 [thread overview]
Message-ID: <4075C45E.50005@gnu.org> (raw)
In-Reply-To: <200404082109.i38L9h5o010821@magilla.sf.frob.com>
Roland, FYI.
Last time this was discussed the observer was identified as the correct
mechanim for hooking this in. That's why I'm currently overhauling that
code.
Andrew
> Perhaps you recall the discussion here some months back about what hook to
> use in Linux targets for the detection of the vsyscall DSO. The last time
> I asked here about a resolution on how best to do this, I got no feedback.
> I hope we can now jumpstart the effort to find the right way to implement
> this. To get things rolling again, here is a patch that I am not
> suggesting for inclusion, but does work. This is a kludge to overload the
> solib hooks with target-specific code. These solib hooks get called at
> roughly (or perhaps even precisely?) the correct places where the vsyscall
> DSO checks ought to happen. A reminder, the appropriate places are when
> gdb thinks the address space might be a fresh layout from what it knows,
> i.e. first attach (or any attach?), after exec, and on opening a core file.
>
> As I said, this code works for me. (It requires symbol_file_add_from_memory,
> which is in the patch I just re-posted.) It seems doubtful this is the
> ultimately desireable approach to wedging this code in where needs to be.
> But it's what I've got, and as I said I'm still waiting for more feedback to
> conclude on exactly what the preferred better thing to do is.
>
>
next prev parent reply other threads:[~2004-04-08 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 21:09 Roland McGrath
2004-04-08 21:30 ` Andrew Cagney [this message]
2004-04-08 22:13 ` Roland McGrath
2004-04-22 0:18 ` Andrew Cagney
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=4075C45E.50005@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=roland@redhat.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