[fpc-devel] win32 debugging broken in fixes_2_2?

Martin Schreiber fpmse at bluewin.ch
Wed Jul 11 07:41:40 CEST 2007

On Tuesday 10 July 2007 17.04, Jonas Maebe wrote:
> You can also disable gdb catching SIGILL from the start of the
> program using "handle SIGILL nostop noprint" (in case gdb for win32
> is broken in this respect), but then you should re-enable it later on
> (unless you don't want the debugger to break when an illegal
> instruction is executed).
Does not work:
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32"...
(gdb) handle SIGILL nostop noprint
Signal        Stop      Print   Pass to program Description
SIGILL        No        No      Yes             Illegal instruction
(gdb) r
Starting program: G:\msegui\testcase\mse\console/console.exe
Loaded symbols for C:\WINNT\system32\KERNEL32.DLL
Loaded symbols for C:\WINNT\system32\OLEAUT32.DLL
Loaded symbols for C:\WINNT\system32\OLE32.DLL
Loaded symbols for C:\WINNT\system32\rpcrt4.dll
Loaded symbols for C:\WINNT\system32\ADVAPI32.DLL
Loaded symbols for C:\WINNT\system32\GDI32.DLL
Loaded symbols for C:\WINNT\system32\USER32.DLL

Program exited with code 0200.
It seems to be a blocking issue for developing with FPC 2.2 on win32 with PII 


More information about the fpc-devel mailing list