This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: Debugging Windows Namespace extension dll
- To: gdb AT sourceware.cygnus dot com
- Subject: Re: Debugging Windows Namespace extension dll
- From: cgf AT cygnus dot com (Chris Faylor)
- Date: 16 Sep 1999 02:07:48 GMT
- DJ-Gateway: from newsgroup cygnus.gdb
- Newsgroups: cygnus.gdb
- Organization: Cygnus Solutions
- References: <l03130300b404ff236a3b@[138.251.135.28]>
In article <l03130300b404ff236a3b@[138.251.135.28]>,
Mark Hindley <mh15@st-andrews.ac.uk> wrote:
>I am in the middle of writing a windows namespace extension implemented as
>an in process server dll. I have got the basic structure complete and it
>builds fine with gcc, but I can not get it to debug with gdb.
>
>I am trying:
>
>exec-file /windows/explorer.exe
>
>source-file MyDll.dll
>
>set args /root, {My CLSID},
>
>
>There appears to be 2 problems. I get an access violation when the dll is
>read, eith as the initial symbol file, or when it is loaded by explorer
>when the programme is run. The other is that I am unable to set any
>breakpoints. If I type
>
>break DllMain
>
>the reply is
>
>Cannot access memory at 0x....
The way that I normally do something like this is:
gdb /windows/explorer.exe
symbol-file MyDll.dll
set args /root
l DllMain
bp <first line number in DllMain>
run
As you probably, know using 'symbol-file' wipes out any existing symbol file
so this may not be exactly what you want. You could use add-sym if you know
the load address of your DLL.
Hope this helps,
Chris Faylor
--
cgf@cygnus.com
http://www.cygnus.com/