Re: [Mingw-users] Debugging Excel-callable dll in WinNT using GDB

[Christopher F. <cg...@re...>]

Wow.  How many mailing lists did you send this message to?

So far, I've seen it twice in the cygwin mailing list, once in the gdb
mailing list, and now once here.

Your inability to find a new version of gdb is a little perplexing since
one is available under cygwin at http://cygwin.com/ (click on Install
Cygwin Now! and expand the Devel category).  I don't know that a newer
version of gdb will solve your problem but at least you'll be running
code that isn't three years old.

If you do decide to run the cygwin version of gdb, you'll be better off
using cygwin drive specs like
/cygdrive/c/progra~1/micros~1/office/excel.exe .

And, if you have questions about the cygwin version of gdb then
obviously this mailing list won't be the place to ask them.

cgf

On Thu, Jan 10, 2002 at 09:18:09AM -0500, Jeanine Kwong wrote:
>I would like to debug an Excel-callable dll in a Windows NT machine
>using gdb version 4.17.1.  What the c++ function does is it takes in the
>parameters from the excel formula, do some calculations, then output the
>result to the cell.  
>
>Because the dll contains a c++ function that creates a thread, I put in
>a "DebugBreak()" call in the c++ codes before and inside whhere the
>program creates a thread.  The program is compiled with g++ with the
>"-mthread" switch.
>
>I tried the following:
>(gdb) file c:\\progra~1\\micros~1\\office\\excel.exe    
>(gdb) run       'Excel started
>
>At this point, gdb command window became inactive.
>I put the formula in a cell in the Excel worksheet with the appropriate
>parameters and pressed enter.
>The dll kicks in and hit the line where "DebugBreak()" is.  gdb regains
>its control.
>
>(gdb) l      'show 10 lines after where debugBreak() is, before creating
>a thread, so far so good
>(gdb) cont   'continue to the DebugBreak() after inside the procedure
>when the thread is created.
>
>(gdb) 1      '***PROBLEM STARTS****!!!
>It showed 10 lines, but they are not the lines that I expected to see! 
>I suspect that it gdb is still in the "old" thread.
>
>(gdb) info threads         'I attempted to find out the thread IDs
>info threads               'not helpful at all!!
>
>Questions:
>Is there any way that I can find out the thread ID?  Is there any switch
>that I have to have to put when I compile the program so that gdb
>becomes thread-aware?  Any suggestion?  
>
>I am thinking of getting a newer version of gdb, but I could not find a
>pre-compiled version of it (ie. a .exe file).  If you do, please let me
>know.
>
>Any help is highly appreciated.
>
>Thanks,
>Jeanine Kwong
>Analyst
>Scotia Capital
>
>_______________________________________________
>MinGW-users mailing list
>Min...@li...
>
>You may change your MinGW Account Options or unsubscribe at:
>https://lists.sourceforge.net/lists/listinfo/mingw-users