From: Sam Steingold <sds@gnu.org>
To: cygwin@cygwin.com
Subject: isatty bug
Date: Mon, 15 Sep 2003 21:19:00 -0000 [thread overview]
Message-ID: <usmmxyckr.fsf@gnu.org> (raw)
calling isatty(0) in a program results in a segfault:
Exception: STATUS_ACCESS_VIOLATION at eip=00000000
eax=00000000 ebx=00000004 ecx=610CEE30 edx=610CEE18 esi=004073B8 edi=0022FECC
ebp=00000400 esp=0022FE00 program=d:\sds\c\scratch.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame Function Args
End of stack trace
calling isatty(0) in gdb results in a segfault too:
Exception: STATUS_ACCESS_VIOLATION at eip=610B7374
eax=00000010 ebx=00000010 ecx=00000004 edx=00000000 esi=D0105E51 edi=100F7240
ebp=0022F178 esp=0022F16C program=d:\gnu\cygwin\bin\gdb.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame Function Args
0022F178 610B7374 (100F7240, D0105E51, 00000010, 000005EC)
0022F1A8 004A767A (100F7178, 00000020, D0105E51, 004C26D8)
0022F1C8 004A75C1 (00000020, D0105E51, 00000000, 00000000)
0022F1E8 004B6175 (00000020, 00000000, 00000000, 000005EC)
0022F218 004A5B8D (100F7178, 00000020, 0022F270, 10292E34)
0022F238 004A5085 (100F7178, 00000020, 0022F270, 0042EF07)
0022F298 004A4F14 (102CB4A8, 004A5050, 100F7178, 0042EF59)
0022F2B8 004A51C5 (102CB4A8, 100F7178, 0022F2E8, 0042DDC0)
0022F2E8 004A5403 (100F7178, FFFFFFE2, 0022F3A8, 004D1F07)
0022F2F8 0049B0A5 (00000001, 61602144, 0022F330, 00A00088)
0022F3A8 004D1F07 (101DBAE8, 00000001, 0022F3DC, 00446EB4)
0022F648 0044712F (00000000, 102AE3D8, 0022F684, 00000000)
0022F668 004443F6 (00000000, 102AE3D8, 0022F684, 00000000)
0022F688 0044461F (102AE3D8, 0022F6B8, 00000000, 00000000)
0022F6C8 0047D269 (100C050A, 00000000, 00000001, 00000001)
0022F6E8 0047D2E1 (100C050A, 00000001, 0022F718, 00407A8C)
End of stack trace (more stack frames may be present)
--
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
If brute force does not work, you are not using enough.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2003-09-15 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 21:19 Sam Steingold [this message]
2003-09-16 10:13 ` Corinna Vinschen
2003-09-16 15:01 ` Sam Steingold
2003-09-16 17:22 ` Christopher Faylor
2003-09-16 17:30 ` Sam Steingold
2003-09-16 17:37 ` Igor Pechtchanski
2003-09-16 18:23 ` Sam Steingold
2003-09-16 18:36 ` Igor Pechtchanski
2003-09-16 19:37 ` Christopher Faylor
2003-09-16 19:01 Brian Ford
2003-09-16 19:02 ` Sam Steingold
2003-09-16 19:34 Brian Ford
2003-09-16 20:28 ` Sam Steingold
2003-09-16 21:01 Brian Ford
2003-09-16 22:05 ` Christopher Faylor
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=usmmxyckr.fsf@gnu.org \
--to=sds@gnu.org \
--cc=cygwin@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).