From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: nc-1.107-2
Date: Tue, 08 May 2012 17:35:00 -0000 [thread overview]
Message-ID: <CAGHJv4d+ApLMtNJgFCOowoQxT6cOvQnMsCYVaCvrveV3tZVBdQ@mail.gmail.com> (raw)
In-Reply-To: <20120508172305.GA17185@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On 8 May 2012 13:23, Corinna Vinschen wrote:
> On May 8 10:43, Harry G McGavran Jr wrote:
>> If I try the example in the nc manpage for cygwin:
>>
>> printf "GET / HTTP/1.0\r\n\r\n" | nc host.example.com 80
>>
>> I get a segfault and a stackdump every time.
>
> Well, sorry, but the above example works fine for me. I just installed
> the latest nc and nc6 packages from scratch and it just works with both
> nc variants.
I also see the segfault behaviour running on a fresh 1.7.14 install
running on Win7 Pro.
> Please send the stackdump and your obligatory cygcheck -svr output
> *as attachment*.
Attached.
Cheers,
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
[-- Attachment #2: nc.exe.stackdump --]
[-- Type: application/octet-stream, Size: 566 bytes --]
Exception: STATUS_ACCESS_VIOLATION at eip=00403F9A
eax=00405F60 ebx=00000016 ecx=00000000 edx=00000000 esi=00000001 edi=610054C0
ebp=00226A18 esp=002269B0 program=C:\cygwin\bin\nc.exe, pid 7200, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
00226A18 00403F9A (6127BEA4, 00000001, 0000FFFF, 00226A4C)
00226A68 00401B0A (6127BEA4, 00000000, 00000000, 00000000)
0022AC68 00402B80 (00000003, 0022AC90, 20010100, 6127B8FC)
0022ACF8 610070D8 (00000000, 0022CD78, 610066D0, 00000000)
End of stack trace
[-- Attachment #3: cygcheck.out --]
[-- Type: application/octet-stream, Size: 26691 bytes --]
[-- Attachment #4: Type: text/plain, Size: 218 bytes --]
--
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
next prev parent reply other threads:[~2012-05-08 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 16:44 Harry G McGavran Jr
2012-05-08 17:02 ` Erik Falor
2012-05-08 17:23 ` Corinna Vinschen
2012-05-08 17:35 ` Chris Sutcliffe [this message]
2012-05-08 17:59 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2012-05-08 17:39 Harry G McGavran Jr
2012-05-08 7:44 Corinna Vinschen
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=CAGHJv4d+ApLMtNJgFCOowoQxT6cOvQnMsCYVaCvrveV3tZVBdQ@mail.gmail.com \
--to=ir0nh34d@gmail.com \
--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).