Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Sender: cwilson@ece.gatech.edu
Message-ID: <37498E94.79D9EFE@ece.gatech.edu>
Date: Mon, 24 May 1999 13:38:28 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: earnie_boyd@yahoo.com
CC: cygwin@sourceware.cygnus.com
Subject: Re: gdb + cygwin
References: <19990524170118.23881.rocketmail@web114.yahoomail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Earnie Boyd wrote:
<snip>

> Hi Chuck,
>
> I've seen this when I have a pointer reference that isn't being referenced
> correctly.  Perhaps a prototype is incorrect or not specified.  Perhaps you
> have a pointer becoming an integer or an integer becoming a pointer, either way
> you're in trouble.
>
> Use the -Wall switch on the compilation and don't ignore the warnings.  If it
> has to do with a pointer, it's an ERROR not a WARNING.

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.

Thanks,
Chuck


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com