U++ forum: Welcome to the forum

Re: How I do to debug my programs? [message #18882 is a reply to message #18877]

Thu, 30 October 2008 12:18

jasperlotus
Messages: 4
Registered: October 2008

Junior Member

zaurus wrote on Thu, 30 October 2008 05:45

Hi!

You can still debug in Upp. Once the debugger reach the breakpoint just wait for a while. Don't press F10 or anything. After 10-20 seconds the variables under 'Auto' or 'Local' will come up and you can start stepping through your program with F10.

It somehow seems that the communication between Upp and GDB is very slow. I don't know what's the reason for it. It used to be ok with older versions of Upp with MinGW.

It's a bit annoying, but still can do some debugging.

Zaurus

It produces like this...

----- jasper_testing ( MAIN GCC DEBUG DEBUG_FULL BLITZ WIN32 )
cd D:\MyApps\coding\jasper_testing
D:\MyApps\apps\MINGW.Debug.Debug_full\jasper_testing.exe (17521 B) is up to date.

OK. (0:00.04)
gdb D:\MyApps\apps\MINGW.Debug.Debug_full\jasper_testing.exe
set prompt <>
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32"...
(gdb) 
set disassembly-flavor intel

set exec-done-display off

set annotate 1

set height 0

set width 0

set confirm off

set print asm-demangle

b D:/MyApps/coding/jasper_testing/main.c:10
Breakpoint 1 at 0x4013fa: file D:/MyApps/coding/jasper_testing/main.c, line 10.

run

...and no more things happen.

I can only press Shift+F5 to stop this procedure.

[Updated on: Thu, 30 October 2008 12:22]

Report message to a moderator