Author Topic: Debugger sometimes stalls when using "Step Into".  (Read 39475 times)

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11939
    • Travis build status
Re: Debugger sometimes stalls when using "Step Into".
« Reply #15 on: November 20, 2012, 10:47:43 pm »
Look at the log for the correct command:)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline and4cb

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: Debugger sometimes stalls when using "Step Into".
« Reply #16 on: November 21, 2012, 12:28:17 am »
I think understand your request.  I opened a MinGW Command Prompt window and entered commands based on the previous log.  If I misunderstood, please let me know.  ... and Thank You.
Code: [Select]
C:\Code\test5>C:\MinGW32\bin\gdb.exe -nx -fullname  -quiet  -args C:/Code/test5/bin/Debug/test5.exe
Reading symbols from C:\Code\test5\bin\Debug\test5.exe...done.
(gdb) show version
GNU gdb (GDB) 7.5
Copyright (C) 2012 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".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) set confirm off
(gdb) set width 0
(gdb) set height 0
(gdb) set breakpoint pending on
(gdb) set print asm-demangle on
(gdb) set unwindonsignal on
(gdb) set print elements 0
(gdb) set new-console on
(gdb) set disassembly-flavor att
(gdb) source C:\cb20121112\share\codeblocks/scripts/stl-views-1.0.3.gdb
(gdb) directory C:/Code/test5/
Source directories searched: C:/Code/test5;$cdir;$cwd
(gdb) tbreak "C:/Code/test5/main.c:10"
Temporary breakpoint 1 at 0x40133f: file C:\Code\test5\main.c, line 10.
(gdb) run
Starting program: C:\Code\test5\bin\Debug\test5.exe
[New Thread 4140.0xcc8]

Temporary breakpoint 1, main () at C:\Code\test5\main.c:12
→→C:\Code\test5\main.c:12:233:beg:0x40133f
(gdb) bt 30
#0  main () at C:\Code\test5\main.c:12
(gdb) si
Initialize () at C:\Code\test5\main.c:18
→→C:\Code\test5\main.c:18:309:beg:0x40134b
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:18
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
→→C:\Code\test5\main.c:19:312:beg:0x401351
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:19
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
→→C:\Code\test5\main.c:24:508:beg:0x401366
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:24
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) si
→→C:\Code\test5\main.c:24:508:middle:0x40136d
(gdb) bt 30
#0  0x0040136d in Initialize () at C:\Code\test5\main.c:24
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) si
InitNum (num=4) at C:\Code\test5\main.c:30
(gdb) bt 30
#0  InitNum (num=4) at C:\Code\test5\main.c:30
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) si
0x0040138f      (gdb) bt 30
#0  0x0040138f in InitNum (num=4) at C:\Code\test5\main.c:30
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) si
(gdb) bt 30
#0  InitNum (num=4) at C:\Code\test5\main.c:31
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) print
The history is empty.
(gdb) show values [10]
A syntax error in expression, near `[10]'.
(gdb) show values
(gdb) show values 10
(gdb) bt 30
#0  InitNum (num=4) at C:\Code\test5\main.c:31
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
(gdb) bt 30
#0  InitNum (num=8) at C:\Code\test5\main.c:32
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
(gdb) bt 40
#0  InitNum (num=8) at C:\Code\test5\main.c:33
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) b
Breakpoint 2 at 0x40136d: file C:\Code\test5\main.c, line 24.
(gdb) bt 30
#0  InitNum (num=8) at C:\Code\test5\main.c:33
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
Initialize () at C:\Code\test5\main.c:26
→→C:\Code\test5\main.c:26:592:beg:0x401377
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:26
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
→→C:\Code\test5\main.c:27:595:beg:0x40138c
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:27
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
main () at C:\Code\test5\main.c:14
→→C:\Code\test5\main.c:14:269:beg:0x401344
(gdb) bt 30
#0  main () at C:\Code\test5\main.c:14
(gdb) n
→→C:\Code\test5\main.c:15:281:beg:0x401349
(gdb) bt 30
#0  main () at C:\Code\test5\main.c:15
(gdb) c
Continuing.
[Inferior 1 (process 4140) exited normally]
(gdb)
OS = Vista Home Premium; Coding Language: C; CB Version = SVN 10122; Compiler = MinGW32 gcc 4.7.1 Windows/unicode - 32 bit; Debugger name and version: GNU gdb (GDB) 7.5

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11939
    • Travis build status
Re: Debugger sometimes stalls when using "Step Into".
« Reply #17 on: November 21, 2012, 12:37:25 am »
Hm, it seems this a gdb problem, because it does it the same on the command line :(

Can you try without these:
Code: [Select]
(gdb) set confirm off
(gdb) set width 0
(gdb) set height 0
(gdb) set breakpoint pending on
(gdb) set print asm-demangle on
(gdb) set unwindonsignal on
(gdb) set print elements 0
(gdb) set new-console on
(gdb) set disassembly-flavor att

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline and4cb

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: Debugger sometimes stalls when using "Step Into".
« Reply #18 on: November 21, 2012, 01:28:39 am »
I guess I did something wrong, because now when I type
C:\MinGW32\bin\gdb.exe -nx -fullname  -quiet  -args C:/Code/test5/bin/Debug/test5.exe
at the c:\code\test5>
I get an error message:
C:\MinGW32\bin\gdb.exe is not a valid Win32 application.

I checked to see if the gdb.exe file exists, and it only has 0 bytes now, and a modified date of 11/20/2012.

Should I restart the computer, reinstall the gdb, or do you have a better suggestion?
« Last Edit: November 21, 2012, 01:30:51 am by and4cb »
OS = Vista Home Premium; Coding Language: C; CB Version = SVN 10122; Compiler = MinGW32 gcc 4.7.1 Windows/unicode - 32 bit; Debugger name and version: GNU gdb (GDB) 7.5

Offline and4cb

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: Debugger sometimes stalls when using "Step Into".
« Reply #19 on: November 21, 2012, 02:02:00 am »
I reinstalled gdb, and here is the result of leaving out the commands you suggested.
Code: [Select]
c:\Code\test5>C:\MinGW32\bin\gdb.exe -nx -fullname  -quiet  -args C:/Code/test5/bin/Debug/test5.exe
Reading symbols from C:\Code\test5\bin\Debug\test5.exe...done.
(gdb) show version
GNU gdb (GDB) 7.5
Copyright (C) 2012 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".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) source C:\cb20121112\share\codeblocks/scripts/stl-views-1.0.3.gdb
(gdb) directory C:/Code/test5/
Source directories searched: C:/Code/test5;$cdir;$cwd
(gdb) tbreak "C:/Code/test5/main.c:10"
Temporary breakpoint 1 at 0x40133f: file C:\Code\test5\main.c, line 10.
(gdb) run
Starting program: C:\Code\test5\bin\Debug\test5.exe
[New Thread 5408.0x12c8]

Temporary breakpoint 1, main () at C:\Code\test5\main.c:12
→→C:\Code\test5\main.c:12:233:beg:0x40133f
(gdb) bt 30
#0  main () at C:\Code\test5\main.c:12
(gdb) si
Initialize () at C:\Code\test5\main.c:18
→→C:\Code\test5\main.c:18:309:beg:0x40134b
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:18
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
→→C:\Code\test5\main.c:19:312:beg:0x401351
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:19
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n

Before call to InitNum(), INUM1 = 0→→C:\Code\test5\main.c:24:508:beg:0x401366
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:24
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) si
→→C:\Code\test5\main.c:24:508:middle:0x40136d
(gdb) bt 30
#0  0x0040136d in Initialize () at C:\Code\test5\main.c:24
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) si
InitNum (num=4) at C:\Code\test5\main.c:30
(gdb) bt 30
#0  InitNum (num=4) at C:\Code\test5\main.c:30
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) si
0x0040138f      (gdb) bt 30
#0  0x0040138f in InitNum (num=4) at C:\Code\test5\main.c:30
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) si
(gdb) bt 30
#0  InitNum (num=4) at C:\Code\test5\main.c:31
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
(gdb) bt 30
#0  InitNum (num=8) at C:\Code\test5\main.c:32
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
(gdb) bt 30
#0  InitNum (num=8) at C:\Code\test5\main.c:33
#1  0x00401372 in Initialize () at C:\Code\test5\main.c:24
#2  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
Initialize () at C:\Code\test5\main.c:26
→→C:\Code\test5\main.c:26:592:beg:0x401377
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:26
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n

After call to InitNum(), INUM1 = 8→→C:\Code\test5\main.c:27:595:beg:0x40138c
(gdb) bt 30
#0  Initialize () at C:\Code\test5\main.c:27
#1  0x00401344 in main () at C:\Code\test5\main.c:12
(gdb) n
main () at C:\Code\test5\main.c:14
→→C:\Code\test5\main.c:14:269:beg:0x401344
(gdb) bt 30
#0  main () at C:\Code\test5\main.c:14
(gdb) n
→→C:\Code\test5\main.c:15:281:beg:0x401349
(gdb) bt 30
#0  main () at C:\Code\test5\main.c:15
(gdb) n
0x004010fd in __mingw_CRTStartup ()
(gdb) bt 30
#0  0x004010fd in __mingw_CRTStartup ()
#1  0x00401295 in mainCRTStartup ()
(gdb) n
Single stepping until exit from function __mingw_CRTStartup,
which has no line number information.
0x00401c00 in ExitProcess@4 ()
(gdb) bt 30
#0  0x00401c00 in ExitProcess@4 ()
#1  0x0040110c in __mingw_CRTStartup ()
#2  0x7efde000 in ?? ()
#3  0x772ad819 in ntdll!RtlWow64CallFunction64 () from C:\Windows\system32\ntdll.dll
#4  0x7efde000 in ?? ()
#5  0x772ada2b in ntdll!RtlCloneMemoryStream () from C:\Windows\system32\ntdll.dll
#6  0x00401280 in _gnu_exception_handler@4 ()
#7  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ExitProcess@4,
which has no line number information.
0x763ea553 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
(gdb) bt 30
#0  0x763ea553 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#1  0x0040110c in __mingw_CRTStartup ()
#2  0x7efde000 in ?? ()
#3  0x772ad819 in ntdll!RtlWow64CallFunction64 () from C:\Windows\system32\ntdll.dll
#4  0x7efde000 in ?? ()
#5  0x772ada2b in ntdll!RtlCloneMemoryStream () from C:\Windows\system32\ntdll.dll
#6  0x00401280 in _gnu_exception_handler@4 ()
#7  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function MapViewOfFileEx,
which has no line number information.
0x77268660 in ntdll!RtlDeactivateActivationContextUnsafeFast () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x77268660 in ntdll!RtlDeactivateActivationContextUnsafeFast () from C:\Windows\system32\ntdll.dll
#1  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#2  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!RtlDeactivateActivationContextUnsafeFast,
which has no line number information.
0x7724e570 in ntdll!RtlApplyRXactNoFlush () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7724e570 in ntdll!RtlApplyRXactNoFlush () from C:\Windows\system32\ntdll.dll
#1  0x77268673 in ntdll!RtlDeactivateActivationContextUnsafeFast () from C:\Windows\system32\ntdll.dll
#2  0x7731001c in ?? ()
#3  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#4  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!RtlApplyRXactNoFlush,
which has no line number information.
0x77268673 in ntdll!RtlDeactivateActivationContextUnsafeFast () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x77268673 in ntdll!RtlDeactivateActivationContextUnsafeFast () from C:\Windows\system32\ntdll.dll
#1  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!RtlDeactivateActivationContextUnsafeFast,
which has no line number information.
0x7728eb35 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7728eb35 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#1  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!EtwEventActivityIdControl,
which has no line number information.
0x7724e570 in ntdll!RtlApplyRXactNoFlush () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7724e570 in ntdll!RtlApplyRXactNoFlush () from C:\Windows\system32\ntdll.dll
#1  0x7728eb40 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#2  0x77310140 in ?? ()
#3  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#4  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!RtlApplyRXactNoFlush,
which has no line number information.
0x7728eb40 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7728eb40 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#1  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!EtwEventActivityIdControl,
which has no line number information.
0x7726a8d7 in ntdll!ZwCloseObjectAuditAlarm () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7726a8d7 in ntdll!ZwCloseObjectAuditAlarm () from C:\Windows\system32\ntdll.dll
#1  0x7728eb51 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#2  0x006b0000 in ?? ()
#3  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#4  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!ZwCloseObjectAuditAlarm,
which has no line number information.
0x7726a8d9 in ntdll!ZwDuplicateObject () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7726a8d9 in ntdll!ZwDuplicateObject () from C:\Windows\system32\ntdll.dll
#1  0x7728eb51 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#2  0x006b0000 in ?? ()
#3  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#4  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!ZwDuplicateObject,
which has no line number information.
0x7726a8f0 in ntdll!ZwQueryAttributesFile () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7726a8f0 in ntdll!ZwQueryAttributesFile () from C:\Windows\system32\ntdll.dll
#1  0x77310140 in ?? ()
#2  0x7728eb51 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#3  0x006b0000 in ?? ()
#4  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#5  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!ZwQueryAttributesFile,
which has no line number information.
0x7726a8b1 in ntdll!ZwWriteVirtualMemory () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7726a8b1 in ntdll!ZwWriteVirtualMemory () from C:\Windows\system32\ntdll.dll
#1  0x7726a8fb in ntdll!ZwQueryAttributesFile () from C:\Windows\system32\ntdll.dll
#2  0x006b0000 in ?? ()
#3  0x7728eb51 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#4  0x006b0000 in ?? ()
#5  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#6  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!ZwWriteVirtualMemory,
which has no line number information.
0x7726a8c4 in ntdll!ZwCloseObjectAuditAlarm () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7726a8c4 in ntdll!ZwCloseObjectAuditAlarm () from C:\Windows\system32\ntdll.dll
#1  0x7731001c in ?? ()
#2  0x7726a8fb in ntdll!ZwQueryAttributesFile () from C:\Windows\system32\ntdll.dll
#3  0x006b0000 in ?? ()
#4  0x7728eb51 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#5  0x006b0000 in ?? ()
#6  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#7  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!ZwCloseObjectAuditAlarm,
which has no line number information.
0x7726a8fb in ntdll!ZwQueryAttributesFile () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7726a8fb in ntdll!ZwQueryAttributesFile () from C:\Windows\system32\ntdll.dll
#1  0x77310140 in ?? ()
#2  0x7728eb51 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#3  0x006b0000 in ?? ()
#4  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#5  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!ZwQueryAttributesFile,
which has no line number information.
0x7726a90b in ntdll!ZwClearEvent () from C:\Windows\system32\ntdll.dll
(gdb) bt 30
#0  0x7726a90b in ntdll!ZwClearEvent () from C:\Windows\system32\ntdll.dll
#1  0x006b0130 in ?? ()
#2  0x7728eb51 in ntdll!EtwEventActivityIdControl () from C:\Windows\system32\ntdll.dll
#3  0x006b0000 in ?? ()
#4  0x763ea568 in MapViewOfFileEx () from C:\Windows\syswow64\kernel32.dll
#5  0x00000000 in ?? ()
(gdb) n
Single stepping until exit from function ntdll!ZwClearEvent,
which has no line number information.
[Inferior 1 (process 5408) exited normally]
(gdb) bt 30
No stack.
(gdb)
« Last Edit: November 22, 2012, 12:49:46 am by and4cb »
OS = Vista Home Premium; Coding Language: C; CB Version = SVN 10122; Compiler = MinGW32 gcc 4.7.1 Windows/unicode - 32 bit; Debugger name and version: GNU gdb (GDB) 7.5

Offline and4cb

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: Debugger sometimes stalls when using "Step Into".
« Reply #20 on: November 22, 2012, 12:52:02 am »
Please let me know what I can do in C::B to replicate the outcome of using the command line, and leaving out the set commands that you detailed.  ???
I thank you in advance for your help.   :)
Hm, it seems this a gdb problem, because it does it the same on the command line :(

Can you try without these:
Code: [Select]
(gdb) set confirm off
(gdb) set width 0
(gdb) set height 0
(gdb) set breakpoint pending on
(gdb) set print asm-demangle on
(gdb) set unwindonsignal on
(gdb) set print elements 0
(gdb) set new-console on
(gdb) set disassembly-flavor att

(Added this reply because I neglected to ask the question in my last post.)
OS = Vista Home Premium; Coding Language: C; CB Version = SVN 10122; Compiler = MinGW32 gcc 4.7.1 Windows/unicode - 32 bit; Debugger name and version: GNU gdb (GDB) 7.5

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11939
    • Travis build status
Re: Debugger sometimes stalls when using "Step Into".
« Reply #21 on: November 22, 2012, 08:59:47 am »
Nothing, the parser should be fixed. I guess it should detect the gdb prompt and then set the m_isProgramStopped to true...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline and4cb

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: Debugger sometimes stalls when using "Step Into".
« Reply #22 on: November 22, 2012, 09:08:56 am »
Thank you for explaining.  I appreciate the time you took to look at this issue.
OS = Vista Home Premium; Coding Language: C; CB Version = SVN 10122; Compiler = MinGW32 gcc 4.7.1 Windows/unicode - 32 bit; Debugger name and version: GNU gdb (GDB) 7.5

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Debugger sometimes stalls when using "Step Into".
« Reply #23 on: November 22, 2012, 09:13:09 am »
Nothing, the parser should be fixed. I guess it should detect the gdb prompt and then set the m_isProgramStopped to true...
What prompt do you mean? This one:
No stack.
? (Should be as easy as to add it to the entry I just made into trunk for the "Function out of bounds thing".

Will you take the action?

@and4cb: Can you try a patch, the one I attached?
« Last Edit: November 22, 2012, 09:16:15 am by MortenMacFly »
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline and4cb

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: Debugger sometimes stalls when using "Step Into".
« Reply #24 on: November 22, 2012, 10:06:37 am »
@and4cb: Can you try a patch, the one I attached?

MortenMacFly:  I have downloaded your patch, but please provide me with instructions on how to apply the patch.  I have never applied a patch before.  Thank you.
« Last Edit: November 22, 2012, 10:09:10 am by and4cb »
OS = Vista Home Premium; Coding Language: C; CB Version = SVN 10122; Compiler = MinGW32 gcc 4.7.1 Windows/unicode - 32 bit; Debugger name and version: GNU gdb (GDB) 7.5

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Debugger sometimes stalls when using "Step Into".
« Reply #25 on: November 22, 2012, 10:17:25 am »
MortenMacFly:  I have downloaded your patch, but please provide me with instructions on how to apply the patch.  I have never applied a patch before.  Thank you.
It requires you to self-compile C::B from the sources and modify the files using the "patch" tool. You'll find instructions in the WiKi accordingly for each platform. However, if you never did you maybe should not worry and let others try. Its not an easy task and requires knowledge about version control, third party libs dev packages, patching sources (using diff/patch) with specific platform tools and so on... There is plenty of help around in the WiKi, too and (of course) in the WWW on that topic.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline and4cb

  • Multiple posting newcomer
  • *
  • Posts: 35
Re: Debugger sometimes stalls when using "Step Into".
« Reply #26 on: November 22, 2012, 10:26:37 am »
It requires you to self-compile C::B from the sources and modify the files using the "patch" tool.
...
However, if you never did you maybe should not worry and let others try.
MortenMacFly:  I will take your advice at this time and let those that are more educated in this process handle the testing. I do not want my learning curve to hinder the problem being solved/tested.  However, I am adding this to my list of "things to learn", as it does sound like a useful skill.

If this patch is successful, will it be included in the next "nightly" that is published?

Thank you so much for your quick replies.
« Last Edit: November 22, 2012, 10:32:09 am by and4cb »
OS = Vista Home Premium; Coding Language: C; CB Version = SVN 10122; Compiler = MinGW32 gcc 4.7.1 Windows/unicode - 32 bit; Debugger name and version: GNU gdb (GDB) 7.5

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11939
    • Travis build status
Re: Debugger sometimes stalls when using "Step Into".
« Reply #27 on: November 22, 2012, 11:51:56 am »
What prompt do you mean? This one:
No stack.
? (Should be as easy as to add it to the entry I just made into trunk for the "Function out of bounds thing".
No, this one: ">>>>>>cb_gdb:"
If we detect this string as program stopped event, all other case could be removed, probably.

Will you take the action?
I doubt, I have some other things to do and this change will require major effort and testing.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11939
    • Travis build status
Re: Debugger sometimes stalls when using "Step Into".
« Reply #28 on: November 23, 2012, 12:20:56 pm »
Morten this commit is useless... r8596, because if you look at the initial log you'll see that the "No stack" string is not present there.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9496
Re: Debugger sometimes stalls when using "Step Into".
« Reply #29 on: November 23, 2012, 01:33:01 pm »
Morten this commit is useless... r8596, because if you look at the initial log you'll see that the "No stack" string is not present there.
Maybe for this, but in general it fixes the same show-stopper as this "Function out of bounds". this messages appears if you step deeply into somehow "special" Win32 apps and freeze the debugger. So the fix might not solve this, but another problem. That's why I committed anyways.

BUT: In one of the logs provided here I saw that message at the end, btw...
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ