On 19 Feb 2005 at 14:50, Frank Heckenbach wrote:
Prof A Olowofoyeku (The African Chief) wrote:
On 19 Feb 2005 at 5:36, Waldek Hebisch wrote:
I have discovered code generation problem on AMD64. The patch below corrects code generation. It causes spurious warnings in some other tests (fjf1014.pas, fjf1021h.pas, fjf1021i.pas, fjf768c.pas, fjf768e.pas, fjf768f.pas) but those will require separate fix.
[...]
Didn't help with the Mingw problem. I ran xgpc.exe through gdb, it tells me that there was an access violation in strncmp(). Have no idea what that is all about - but the previous snapshots don't cause this access violation, so it doesn't seem like a library issue ...
Can you post a complete traceback or at least error position? (There are many strncmp's in gpc.c, and know which one it is might help.)
Attached ...
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/
(Mingw)/src/mingw/gcc-3.2.3/build/gcc $gdb xgpc.exe GNU gdb 6.3 Copyright 2004 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"... Breakpoint 1 at 0x404446: file ../../gcc/p/gpc.c, line 7569. Breakpoint 2 at 0x4141a0 Breakpoint 3 at 0x414250 (gdb) run Starting program: c:\src\mingw\gcc-3.2.3\build\gcc/xgpc.exe gdb: do_initial_child_stuff: process 2488 gdb: kernel event for pid=2488 tid=2736 code=CREATE_PROCESS_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 2488.0xab0 ContinueDebugEvent (cpid=2488, ctid=2736, DBG_CONTINUE); gdb: kernel event for pid=2488 tid=2736 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 2488.0xab0 ContinueDebugEvent (cpid=2488, ctid=2736, DBG_CONTINUE); gdb: kernel event for pid=2488 tid=2736 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 2488.0xab0 ContinueDebugEvent (cpid=2488, ctid=2736, DBG_CONTINUE); gdb: kernel event for pid=2488 tid=2736 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 2488.0xab0 ContinueDebugEvent (cpid=2488, ctid=2736, DBG_CONTINUE); gdb: kernel event for pid=2488 tid=2736 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 2488.0xab0 ContinueDebugEvent (cpid=2488, ctid=2736, DBG_CONTINUE); gdb: kernel event for pid=2488 tid=2736 code=LOAD_DLL_DEBUG_EVENT) gdb: child_resume.SetThreadContext: thread 2488.0xab0 ContinueDebugEvent (cpid=2488, ctid=2736, DBG_CONTINUE); gdb: kernel event for pid=2488 tid=2736 code=EXCEPTION_DEBUG_EVENT) gdb: Target exception EXCEPTION_BREAKPOINT at 0x7c901230 gdb: child_resume.SetThreadContext: thread 2488.0xab0 ContinueDebugEvent (cpid=2488, ctid=2736, DBG_CONTINUE); gdb: kernel event for pid=2488 tid=2736 code=EXCEPTION_DEBUG_EVENT) gdb: Target exception EXCEPTION_ACCESS_VIOLATION at 0x77c47a64
Program received signal SIGSEGV, Segmentation fault. 0x77c47a64 in strncmp () (gdb) info line *0x77c47a64 No line number information available for address 0x77c47a64 <strncmp+20>