From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: graph (plotutils) seg-faulting
Date: Wed, 22 Jul 2020 08:06:26 -0400 [thread overview]
Message-ID: <ad65e28e-125f-38c4-6d78-be2dfe7a408e@cornell.edu> (raw)
In-Reply-To: <3e1ba674-65b0-7efa-88a2-c256f6d819fb@gmail.com>
On 7/22/2020 1:36 AM, Marco Atzeri via Cygwin wrote:
> On 22.07.2020 02:10, Tony Richardson via Cygwin wrote:
>> I have attached both the cygcheck and strace output.
>>
>> Tony Richardson
>>
>
> something is clearly interfering with your Cygwin installation
>
> --- Process 11136 loaded C:\Applications\cygwin64\bin\cygwin1.dll at
> 0000000000c80000
> --- Process 11136 unloaded DLL at 0000000000c80000
I can reproduce the problem on my system:
$ strace graph
--- Process 30536 created
--- Process 30536 loaded C:\Windows\System32\ntdll.dll at 00007ff82a4c0000
--- Process 30536 loaded C:\Windows\System32\kernel32.dll at 00007ff8289c0000
--- Process 30536 loaded C:\Windows\System32\KernelBase.dll at 00007ff8280c0000
--- Process 30536 thread 14832 created
--- Process 30536 thread 31180 created
--- Process 30536 loaded C:\cygwin64\bin\cygplot-2.dll at 0000000000bc0000
--- Process 30536 unloaded DLL at 0000000000bc0000
--- Process 30536 loaded C:\cygwin64\bin\cygwin1.dll at 0000000000bc0000
--- Process 30536 unloaded DLL at 0000000000bc0000
[...]
--- Process 30536 loaded C:\cygwin64\bin\cygiconv-2.dll at 0000000001780000
--- Process 30536 unloaded DLL at 0000000001780000
[...]
--- Process 30536 exited with status 0xc0000005
Segmentation fault
I thought that simply rebuilding plotutils might fix the problem, but there were
a lot of compilation warnings, and the build failed. Some of the warnings look
serious to me, but I have no idea if they could cause Windows to try to load
DLLs at strange addresses.
Ken
next prev parent reply other threads:[~2020-07-22 12:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 21:12 briand
2020-07-19 6:04 ` Marco Atzeri
2020-07-19 15:55 ` briand
2020-07-19 17:46 ` Marco Atzeri
2020-07-19 18:23 ` briand
2020-07-19 19:15 ` Marco Atzeri
2020-07-21 3:12 ` briand
2020-07-21 4:28 ` Marco Atzeri
2020-07-21 14:50 ` Brian Inglis
2020-07-21 16:17 ` Tony Richardson
2020-07-21 23:59 ` Brian Inglis
2020-07-22 0:10 ` Tony Richardson
2020-07-22 5:36 ` Marco Atzeri
2020-07-22 12:06 ` Ken Brown [this message]
2020-07-22 20:47 ` Marco Atzeri
2020-07-22 22:07 ` Tony Richardson
2020-07-22 22:12 ` Ken Brown
2020-07-23 4:48 ` Marco Atzeri
2020-07-23 16:47 ` Ken Brown
2020-07-23 17:00 ` Tony Richardson
2020-07-23 17:17 ` Brian Inglis
2020-07-23 18:39 ` Tony Richardson
2020-07-24 6:24 ` ASSI
2020-07-22 16:30 ` Tony Richardson
2020-07-22 18:10 ` Marco Atzeri
2020-07-23 5:43 ` briand
2020-07-23 12:49 ` Tony Richardson
2020-07-23 14:40 ` marco atzeri
2020-07-23 14:48 ` Tony Richardson
2020-07-21 12:29 ` Jon Turney
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=ad65e28e-125f-38c4-6d78-be2dfe7a408e@cornell.edu \
--to=kbrown@cornell.edu \
--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).