gdb20030901-1: aborts with stack dump

Bryan Higgins
Fri Sep 19 21:10:00 GMT 2003

Here is gdb.exe.stackdump, for what it's worth:

Exception: STATUS_ACCESS_VIOLATION at eip=610B7374
eax=00000010 ebx=00000010 ecx=00000004 edx=00000000 esi=D012
ebp=0022F518 esp=0022F50C program=c:\cygwin\bin\gdb.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022F518  610B7374  (100F7160, D0127169, 00000010, 00001284)
0022F548  004A767A  (100F7098, 00000020, D0127169, 004C26D8)
0022F568  004A75C1  (00000020, D0127169, 00000000, 00000000)
0022F588  004B6175  (00000020, 00000000, 00000000, 00001284)
0022F5B8  004A5B8D  (100F7098, 00000020, 0022F610, 100F7324)
0022F5D8  004A5085  (100F7098, 00000020, 0022F610, 00422D7A)
0022F638  004A4F14  (100F7260, 004A5050, 100F7098, 00000001)
0022F658  004A51C5  (100F7260, 100F7098, 00000001, 00000006)
0022F688  0049A016  (FFFFFFFF, 00000090, 00000000, 0040513D)
0022F6F8  004373E9  (00000000, 00000001, 0022F728, 00407A8C)
0022F708  00405839  (100D28D0, 00000000, 00000001, 00000001)
0022F728  00407A8C  (100D28D0, 00000000, 00000001, 00000000)
0022F768  0042317D  (100C04C6, 00000001, 0022F798, 005B7263)
0022F798  004843AB  (100C04C0, 10103D90, 0022F7D8, 005C71BC)
0022F7D8  0048483C  (100E0E70, 00000000, FFFFFFFF, 100E0E70)
0022F7F8  005C5B95  (00000000, 100E39C0, 0022F818, 0048420D)
End of stack trace (more stack frames may be present)

As reported yesterday, this happens when typing "finish" after a breakpoint.
Happens every time with my (large) program; I couldn't reproduce the problem
with a simple program, alas.

The problem doesn't happen with gdb20030303-1.

Unsubscribe info:
Problem reports:

More information about the Cygwin mailing list