This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: fun? with libsigsegv
- From: Eric Blake <ebb9 at byu dot net>
- To: cygwin at cygwin dot com
- Date: Fri, 17 Jul 2009 22:50:17 +0000 (UTC)
- Subject: Re: fun? with libsigsegv
- References: <loom.20090717T213846-627@post.gmane.org>
Eric Blake <ebb9 <at> byu.net> writes:
> Now, upgrade to the latest snapshot, 20090717.
>
> Without libsigsegv, things operate as before. But with libsigsegv, I now
see...
Aargh. I spoke too soon. For my previous mail, I fat-fingered my command
line, and ended up compiling with:
$ gcc -o foo foo.c -lsigsegv -Dsigsegv
instead of the intended
$ gcc -o foo foo.c -lsigsegv -Dlibsigsegv
Of course, given the code, that meant I wasn't using libsigsegv like I thought
I was. So, with my typo corrected, I'm (unfortunately) still seeing libsigsegv
interference:
$ ./foo
fclose -1, errno 9
Aborted (core dumped)
> Meanwhile, I am considering working on a newlib patch that changes fflush to
> immediately die with EBADF rather than trying to _flockfile(fp) if fp->_flags
> is 0, if for no other reason than to be more like Linux in returning EBADF
> instead of success on my unspecified STC.
But this front may still have hope.
--
Eric Blake
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple