| Debugging Windows DLLs [message #205172] |
Mon, 19 November 2007 08:52  |
Eclipse User |
|
|
|
Hi,
I know, this isn't a real CDT problem, but maybe, someone of you can help
be anyway:
I have written a library and have built it with debugging symbols as
windows DLL. I also have made an application that uses this DLL, and that
is also built with debugging symbols. The DLL project is also mentioned as
project Reference. I start a gdb debugging session with the application
(If I browse the source paths, the paths of the DLL project are included),
I can step throgh all those functions defined in the application. I also
can browse the sub-variables of the objects what are of types defined in
the DLL. The problem is: I cannot step into those functions defined in the
DLL. If I click 'step into', it only works with functions of the app, with
DLL functions, it behaves like 'step over'.
I get the same behaviour (at least, that with the steps) if I use gdb in a
debugging session.
Which settings do I have to specify in gdb, or - much better ;) - in
eclipse to debug a DLL?
Fabian.
|
|
|
| Re: Debugging Windows DLLs [message #205251 is a reply to message #205172] |
Tue, 20 November 2007 13:05  |
| Eclipse User |
|
|
|
> Hi,
> I know, this isn't a real CDT problem, but maybe, someone of you can
> help be anyway:
> I have written a library and have built it with debugging symbols as
> windows DLL. I also have made an application that uses this DLL, and
> that is also built with debugging symbols. The DLL project is also
> mentioned as project Reference. I start a gdb debugging session with the
> application (If I browse the source paths, the paths of the DLL project
> are included), I can step throgh all those functions defined in the
> application. I also can browse the sub-variables of the objects what are
> of types defined in the DLL. The problem is: I cannot step into those
> functions defined in the DLL. If I click 'step into', it only works with
> functions of the app, with DLL functions, it behaves like 'step over'.
> I get the same behaviour (at least, that with the steps) if I use gdb in
> a debugging session.
> Which settings do I have to specify in gdb, or - much better ;) - in
> eclipse to debug a DLL?
>
> Fabian.
I have to add a problem using CDT: I was able to debug into the DLL by
using gdb's command line interface, specifying directory and dll-symbols
for the source path and the binary file of the DLL. I placed a breakpoint
in the DLL, and the program was stopped correctly on reaching the
breakpoint.
Now, I want to know how I can do these steps in eclipse - because setting
the breakpoint by _filename_ does not work properly - the breakpoint
simply is ignored by gdb. So, I have to make CDT passing the breakpoints
to gdb by symbols, not file:linenumbers.
Another problem, which is not very bad, but a but uncomfortable: If the
debugger breaks, and I step until I reach a DLL-definded function, gdb
cannot step into (by step command), but if I am currently in a DLL
function, at another DLL function, I can step into it.
So, how can I make eclipse behave like in the 2nd paragraph, and maybe,
someone knows something about my problems in paragraph 3.
Fabian.
|
|
|
Powered by
FUDForum. Page generated in 0.25116 seconds
Home