RE: [pbmserv-dev] Segmentation fault

["Michael Hammond" <MCTMike@AbacusTech.Info>]

Got the stack dump - but it means little to me...

Mike

  GNU nano 1.2.2             File: gomoku.exe.stackdump

Exception: STATUS_ACCESS_VIOLATION at eip=610E94A4
eax=0042C810 ebx=00000000 ecx=0042C810 edx=00000000 esi=61128080
edi=610066B8
ebp=0022EA68 esp=0022EA64 program=c:\temp\gomoku.exe, pid 320, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022EA68  610E94A4  (00000000, 0042C810, 0042C81D, 00000001)
0022EC98  0040C137  (0022EDC0, 00000000, 61822DD0, 610BC6CB)
0022ED48  0040A774  (0022EDC0, 00000004, 61822DC0, 00401081)
0022EFA8  004010FC  (00000004, 61822DC0, 004E00A8, 0022F000)
0022EFE8  61006A1D  (0022F000, 0022F020, 0022F368, 0022F880)
0022FF88  61006E41  (00000000, 00000000, 00000000, 00000000)
End of stack trace

-----Original Message-----
From: owner-pbmserv-dev@gamerz.net [mailto:owner-pbmserv-dev@gamerz.net] On
Behalf Of Paul van Wamelen
Sent: Wednesday, June 29, 2005 12:01 PM
To: pbmserv-dev@gamerz.net
Subject: Re: [pbmserv-dev] Segmentation fault


On Wed, 29 Jun 2005, Richard Rognlie wrote:

> On Wed, Jun 29, 2005 at 11:49:32AM -0500, Michael Hammond wrote:
> > I'm not sure where core files would be appearing (do you know?), so I
just
> > launched gomoku from within gdb.  Here's what I got.
> >
> > ----------------------------------------------
> >
> > (gdb) set args challenge test1 test2
> > (gdb) run
> > Starting program: /cygdrive/c/temp/gomoku.exe challenge test1 test2
> >
> > <snipped board output>
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x610e94a4 in strcmp () from /usr/bin/cygwin1.dll

Ah! Looks like some environment variable isn't set. Check that SENDER
is set. If you can find the exact strcmp, you could also replace it
with Strcmp (which is just a wrapper for strcmp that takes care of null
strings)

> if you add "-g" to the compile/link flags, it'll include debug infor that
will allow you to type "where" in gdb when it breaks to get a useful stack
trace.

But that's set by default so is probably on already. But you probably have
your limits set to 0 core file sizes. Try the ulimit command.
"ulimit -c unlimited" should do the trick. The core file should appear
where you are running gomoku.

fritzd


To unsubscribe, send a message to esquire@gamerz.net with
	unsubscribe pbmserv-dev@gamerz.net
as the BODY of the message.  The SUBJECT is ignored.