CDT, DBG: debug C++ dll with VB60 executable [message #166934] |
Thu, 30 March 2006 12:05 |
Eclipse User |
|
|
|
Originally posted by: rene.nijboer.siemens.com
Hello,
Eclipse: Version: 3.1.2
CDT: 3.0.2
In Eclipse (CDT) I have created a DLL. The DLL compiles and can be debuged
within Eclipse using a testproject (C++).
I have also a VB60 executable that is using the c++ dll. When I run the
executable (without debugging) the DLL returns the correct values. But
when I want to debug the DLL using this VB60 executable a message box
pops-up with the following message:
Unable to set the temporary breakpoint in main.
Reason: Target request failed: No symbol table is loaded. Use the "file"
command...
Continue?
If I select the [Yes]: the program is running fine, but with debugging
functionality...
Additional info:
I have set the option -g in the debug option.
Part of the messages in the console when compiling/building.
Invoking: GCC C++ Compiler
g++ -O0 -g3 -g -Wall -c -fmessage-length=0 -oMain_C_Wrapper.o
../Main_C_Wrapper.cpp
What am I doing wrong?
Tanks in advance.
Rene
|
|
|
Re: CDT, DBG: debug C++ dll with VB60 executable [message #167002 is a reply to message #166934] |
Thu, 30 March 2006 17:25 |
Eclipse User |
|
|
|
Originally posted by: dschaefer.qnx.com
Rene Nijboer wrote:
> Hello,
>
> Eclipse: Version: 3.1.2
> CDT: 3.0.2
>
> In Eclipse (CDT) I have created a DLL. The DLL compiles and can be
> debuged within Eclipse using a testproject (C++).
> I have also a VB60 executable that is using the c++ dll. When I run the
> executable (without debugging) the DLL returns the correct values. But
> when I want to debug the DLL using this VB60 executable a message box
> pops-up with the following message: Unable to set the temporary
> breakpoint in main.
> Reason: Target request failed: No symbol table is loaded. Use the "file"
> command...
> Continue?
>
> If I select the [Yes]: the program is running fine, but with debugging
> functionality...
> Additional info:
> I have set the option -g in the debug option.
>
> Part of the messages in the console when compiling/building.
> Invoking: GCC C++ Compiler
> g++ -O0 -g3 -g -Wall -c -fmessage-length=0 -oMain_C_Wrapper.o
> ./Main_C_Wrapper.cpp
>
> What am I doing wrong?
>
> Tanks in advance.
>
> Rene
>
>
>
I assume you are using gdb to debug? I know that gdb has a hell of a
time with VisualStudio built executables. I tried the same thing writing
a plugin for Microsoft Flight Simulator. It was hell and I didn't get
very far.
Now if we had full support for Microsoft's tool chain...
Doug
|
|
|
Re: CDT, DBG: debug C++ dll with VB60 executable [message #167089 is a reply to message #166934] |
Fri, 31 March 2006 13:03 |
Eclipse User |
|
|
|
Originally posted by: divis1969.mail.ru
I had similar problems and I've found the following method to debug my DLL
(It is not VB60, but probably VS6).
I've created Debug configuration to run C++ Local Application and specified
the exe.
On the Debugger page I've specified the gdb init file to use while debugging
this application.
This file contains the following:
dll-symbols <your-dll> -readnow
b <Your DLL exported simbol>
This will cause debugger to stop at the breakpoint while running your
application.
After this you will be able to set breakpoint in other functions
Dmitry
"Rene Nijboer" <rene.nijboer@siemens.com> wrote in message
news:00c3ed519ea83664f4c98443cae3f6da$1@www.eclipse.org...
> Hello,
>
> Eclipse: Version: 3.1.2
> CDT: 3.0.2
>
> In Eclipse (CDT) I have created a DLL. The DLL compiles and can be debuged
> within Eclipse using a testproject (C++).
> I have also a VB60 executable that is using the c++ dll. When I run the
> executable (without debugging) the DLL returns the correct values. But
> when I want to debug the DLL using this VB60 executable a message box
> pops-up with the following message: Unable to set the temporary breakpoint
> in main.
> Reason: Target request failed: No symbol table is loaded. Use the "file"
> command...
> Continue?
>
> If I select the [Yes]: the program is running fine, but with debugging
> functionality...
> Additional info:
> I have set the option -g in the debug option.
>
> Part of the messages in the console when compiling/building.
> Invoking: GCC C++ Compiler
> g++ -O0 -g3 -g -Wall -c -fmessage-length=0 -oMain_C_Wrapper.o
> ./Main_C_Wrapper.cpp
>
> What am I doing wrong?
>
> Tanks in advance.
>
> Rene
>
>
>
|
|
|
|
|
Re: CDT, DBG: debug C++ dll with VB60 executable [message #167167 is a reply to message #167089] |
Fri, 31 March 2006 15:03 |
Eclipse User |
|
|
|
Originally posted by: rene.nijboer.siemens.com
At 1st thanks for your answers.
I'm new to "gdb init files". What do you mean with <Your DLL exported
symbol>? Is it a function that I want to call or should I specifiy the
name of a class?
I have created a "gdb init file" containing the following information:
dll-symbols
C:/Data/rnij1/Dev/StageSpacing-cpp/stagespacingdll/Debug/sta gespacingdll.dll
-readnow
b iniStageSpacing_vb
Thanks in advance.
Rene
|
|
|
Re: CDT, DBG: debug C++ dll with VB60 executable [message #167993 is a reply to message #166934] |
Wed, 12 April 2006 19:33 |
Eclipse User |
|
|
|
Originally posted by: jancewicz.comcast.net
I had similar difficulties when trying to use Eclipse to debug a Java app
that called native C code in a DLL. I could not get the Eclipse C/C++
debugger to set the breakpoint in my C code in the DLL, even after the Java
JVM had loaded the DLL into its process space. I ended up having to use the
Insight debugger to debug my C DLL. This link explains how I did it:
http://www.kineteksystems.com/white-papers/mixedjavaandc.htm l
You might be able to do something similar by attaching the Insight debugger
to your VB process *after* it has loaded your DLL but *before* it calls the
C function or C++ method in your DLL that you want to debug.
Hope it helps,
Nick Jancewicz
"Rene Nijboer" <rene.nijboer@siemens.com> wrote in message
news:00c3ed519ea83664f4c98443cae3f6da$1@www.eclipse.org...
> Hello,
>
> Eclipse: Version: 3.1.2
> CDT: 3.0.2
>
> In Eclipse (CDT) I have created a DLL. The DLL compiles and can be debuged
> within Eclipse using a testproject (C++).
> I have also a VB60 executable that is using the c++ dll. When I run the
> executable (without debugging) the DLL returns the correct values. But
> when I want to debug the DLL using this VB60 executable a message box
> pops-up with the following message: Unable to set the temporary breakpoint
> in main.
> Reason: Target request failed: No symbol table is loaded. Use the "file"
> command...
> Continue?
>
> If I select the [Yes]: the program is running fine, but with debugging
> functionality...
> Additional info:
> I have set the option -g in the debug option.
>
> Part of the messages in the console when compiling/building.
> Invoking: GCC C++ Compiler
> g++ -O0 -g3 -g -Wall -c -fmessage-length=0 -oMain_C_Wrapper.o
> ./Main_C_Wrapper.cpp
>
> What am I doing wrong?
>
> Tanks in advance.
>
> Rene
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03121 seconds