On Fri, May 23, 2003 at 04:48:29PM +0200, Michael Stather wrote:
> Hi,
>
> I recently managed how to get debugging to work in Dev-C++, but I noticed 2
> problems:
>
> 1. I have to manually enable "create debug info" in the linker settings for
> debugging. Perhaps it should be enabled automatically (or by asking the
> user) when the "debug"-button is pressed the first time.
>
Generally setting the "create debung info" to "on", is a one time
operation. Do you mean that in your case, Dev-C++ does not retain
the setting between sessions?
As for enabling it automatically, default of Gcc is not to include
debug info unless user explicitly requires that, I guess that leaving
out debug info makes binary files smalles and faster to execute.
Asking user when the debug button is pressed would be too late :-)
Unless one is willing also to rebuild
> 2. If I set breakpoints, only the ones in my "int main"-
> function are reagrded and processed, but if I set them for example in the
> constructor of some of my classes the program never stops there.
> [...]
Guessing: could it be that you have some pieces of code compiled with
"Debug info" turned "on" and some with that option turned "off" ?
> If somebody has an idea how to fix #2, it would be very cool, since I need
> debugging very much (as a beginner :) )
Also try using the external GUI debugger called "Insight 5" (should be
available at: http://www.bloodshed.net/dev/packages/index.html)
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
--
>> gisan >>
A vivid and creative mind characterizes you.
|