From: Mark Hindley <mh15@st-andrews.ac.uk>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Debugging Windows Namespace extension dll
Date: Fri, 19 Nov 1999 04:10:00 -0000 [thread overview]
Message-ID: <l03130301b45aed9c5d31@[138.251.135.28]> (raw)
In-Reply-To: <199911191222.NAA32665@cerbere.u-strasbg.fr>
That is the whole point. I can't get it to break anywhere. Maybe it was a
silly example I posted, but I get the same problem if I try to put a bp on
(say) line 1 of DllMain.
Why is gdb trying to insert a bp before the dll is loaded?
>>tb 13
>>
>>Breakpoint 1 at 0x661811a0: file CompObj.cpp, line 13.
>
>>Starting program: /windows/explorer.exe /root,
>>{53161ce0-56af-11d3-abb2-444553540001},
>>bfb90000:C:/WINDOWS/SYSTEM/COMCTL32.DLL
>>bfb50000:C:/WINDOWS/SYSTEM/SHLWAPI.DLL
>>bff60000:C:/WINDOWS/SYSTEM/USER32.DLL
>>bff30000:C:/WINDOWS/SYSTEM/GDI32.DLL
>>bff70000:C:/WINDOWS/SYSTEM/KERNEL32.DLL
>>bfed0000:C:/WINDOWS/SYSTEM/ADVAPI32.DLL
>
> Its normal because your DLL has not yet been loaded into
>memory !!
>>Cannot insert breakpoint 1:
>>
>>Cannot access memory at address 0x661811a0.
>>Am I doing something silly?
>
> You must first break somewhere after
>the DLL was loaded, or is it possible to
>get a stop after DLL loading ?
>
>
>
>Pierre Muller
>Institut Charles Sadron
>6,rue Boussingault
>F 67083 STRASBOURG CEDEX (France)
> mailto:muller@ics.u-strasbg.fr
>Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
Mark Hindley
Acting Director of the Music Centre
University of St Andrews
01334 462226
http://www.st-andrews.ac.uk/services/music
next parent reply other threads:[~1999-11-19 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199911191222.NAA32665@cerbere.u-strasbg.fr>
1999-11-19 4:10 ` Mark Hindley [this message]
[not found] <l03130305b44c7ccd1ad2@[138.251.135.28]>
1999-11-09 6:00 ` Chris Faylor
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='l03130301b45aed9c5d31@[138.251.135.28]' \
--to=mh15@st-andrews.ac.uk \
--cc=gdb@sourceware.cygnus.com \
--cc=muller@cerbere.u-strasbg.fr \
/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