Re: [pbmserv-dev] Segmentation fault

[Paul van Wamelen <wamelen@math.lsu.edu>]

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