This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: gdb + cygwin
Earnie Boyd wrote:
> --- Charles Wilson <cwilson@ece.gatech.edu> wrote:
> >
> > Okay, I tried this:
> > gcc -Wall -c smain.c ===> no errors
> > gcc -Wall -c gaaout.c ===> a few errors having to do with a return (no
> > args)
> > in a function that isn't supposed to return void. After I fixed 'em,
> >
> > gcc -Wall -c gaaout.c ===> no errors
> > gcc -o smain smain.o gaaout.o ===> no errors
> >
> > execute `smain' ==> core dump. sigh.
>
> How about referencing memory location zero due to a NULL pointer reference?
> This will always SIGSEGV.
>
> BTW, Mumit always suggests using Purify or ElectricFence to check the memory
> allocation. I've often suggested using the -lmmalloc library.
Well, linking with electricfence on HP-UX showed no problems. Will electricfence
run in cygwin? (I would just try it and see, but perens.com seems to be down right
now, so I can't get the source code). Also, does efence check for NULL pointer
references in addition to memory allocation errors?
--Chuck
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com