public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pebolle at tiscali dot nl" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/9474] GDB will not set pending breakpoints in DLL's loaded with LoadLibrary()
Date: Wed, 27 Apr 2011 13:09:00 -0000	[thread overview]
Message-ID: <bug-9474-4717-FxWrlFxuRZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9474-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=9474

Paul Bolle <pebolle at tiscali dot nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pebolle at tiscali dot nl
          Component|win32                       |tui

--- Comment #1 from Paul Bolle <pebolle at tiscali dot nl> 2011-04-27 13:05:57 UTC ---
0) If I understand this API correctly (ie, if I didn't miss something in wine's
source) there actually are four functions:
- LoadLibraryA()
- LoadLibraryExA()
- LoadLibraryW()
- LoadLibraryExW()

1) I suppose supporting this would mean something like:
- locating "imports" of one or more of those four functions in the header of
the executable where imported functions should be listed;
- setting a (certain type of) breakpoint at those locations. That breakpoint
should make sure that if those functions are (successfully) called the list of
functions imported from DLL will be updated, that this list is checked for
pending breakpoints, etc.

2) In short, an interface broadly similar to the interface used for 
"manually" loading shared libraries on systems that use dlopen(3). That looks
doable (but far for from trivial, certainly for me).

3) To aid my memory: see bp_shlib_event and create_solib_event_breakpoint() for
an introduction to that interface.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


       reply	other threads:[~2011-04-27 13:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9474-4717@http.sourceware.org/bugzilla/>
2011-04-27 13:09 ` pebolle at tiscali dot nl [this message]
2011-04-27 13:16 ` [Bug win32/9474] " pebolle at tiscali dot nl
2011-04-27 14:52 ` pedro at codesourcery dot com
2011-04-28 15:20 ` pebolle at tiscali dot nl
2011-04-28 21:20 ` pebolle at tiscali dot nl
2011-04-29 10:20 ` pedro at codesourcery dot com
2011-04-29 19:32 ` pebolle at tiscali dot nl
2011-05-02 10:45 ` pedro at codesourcery dot com

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=bug-9474-4717-FxWrlFxuRZ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).