From: Eric Blake <ebb9@byu.net>
To: cygwin-talk@cygwin.com
Subject: Re: fun? with libsigsegv
Date: Sat, 18 Jul 2009 12:55:00 -0000 [thread overview]
Message-ID: <4A61C658.7040707@byu.net> (raw)
In-Reply-To: <loom.20090717T224758-877@post.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Eric Blake on 7/17/2009 4:50 PM:
>> 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
I hate it when a typo changes the course of my entire weekend. I thought
for sure that I was home free, until I realized that I wasn't testing the
snapshot like I thought I was. Almost as bad as the feeling you get when
you see a hippo charging you.
With m4, it's interesting how many pieces have to interact, and yet how
concise a reproducible test case is:
echo | m4 >&-
It requires cygwin 1.7 (1.5 passes, as does Linux), closed stdout (who
does that, normally?), and libsigsegv (no crash if the library is omitted
from m4) - in other words, not your most common combinations.
At any rate, it looks like the crash can be independently avoided from any
one of three locations (gnulib's use of fflush[1], newlib's fault in
fflush[2], and libsigsegv's overreacting to faults that cygwin wants to
claim[3]). But although any one of the patches fixes the simple m4 test
case, I'm hoping that all three get accepted in their respective upstream
repositories.
[1] http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/18046/focus=18052
[2] http://sourceware.org/ml/newlib/2009/msg00770.html
[3] URL to libsigsegv patch not yet known - wanna help me write it? ;)
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkphxlgACgkQ84KuGfSFAYCDpQCgkMnCxOiWq3MInHukLETKHv3N
DtMAoM6pqNOg0jF3M/mF1EB4rzOtMyZY
=bRRu
-----END PGP SIGNATURE-----
parent reply other threads:[~2009-07-18 12:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <loom.20090717T224758-877@post.gmane.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A61C658.7040707@byu.net \
--to=ebb9@byu.net \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).