On Fri, Aug 01, 2008 at 03:24:26PM +0000, Steve Waldo wrote: >I've seen other postings that show stackdump examples that include the >expected list of addresses in the stack trace. I'm not getting that >list. When my app gets a seg fault it produces the expected stackdump >file: > >[1]- Segmentation fault (core dumped) ./ResourceMgr > >but the resulting file contains no stack trace: > >$ cat ResourceMgr.exe.stackdump >Exception: STATUS_ACCESS_VIOLATION at eip=00000000 >eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=611021A0 edi=004026B4 >ebp=0022CC28 esp=0022CC1C program=c:\code\ResourceMgr\ResourceMgr.exe, pid >3956, thread main >cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 >Stack trace: >Frame Function Args >End of stack trace > >Is there a setting I'm missing somewhere? My apologies if this is >something obvious. I did try searching FAQ's etc.
That just means that cygwin's crude stack dump code wasn't able to figure out a stack dump from the given esp and ebp registers. Run your program under gdb if you want to really track down the problem. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
