From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: graph (plotutils) seg-faulting
Date: Sun, 19 Jul 2020 21:15:26 +0200 [thread overview]
Message-ID: <d1fd6d18-e398-b6c8-5553-1ee2129d05a5@gmail.com> (raw)
In-Reply-To: <20200719112321.4d66f748@quarternote>
On 19.07.2020 20:23, briand@pounceofcats.com wrote:
> On Sun, 19 Jul 2020 19:46:31 +0200
> Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
>
>> it seems a problem with loading cygiconv-2.dll
>>
>> --- Process 3080 loaded C:\cygwin64\bin\cygiconv-2.dll at 0000000001130000
>> --- Process 3080 unloaded DLL at 0000000001130000
>> --- Process 3080 loaded C:\cygwin64\bin\cygiconv-2.dll at 0000000001130000
>> --- Process 3080, exception c0000005 at 00000000014f5075
>>
>> but the address fault seems in cygwin1.dll
>>
>> --- Process 3080 loaded C:\cygwin64\bin\cygwin1.dll at 00000000014f0000
>>
>> what version is installed ?
>>
>> Can you try to reinstall it ?
>
> I wasn't sure which package you were talking about. i reinstalled both cygwin and base-cygwin.
I was referring to libiconv2
>>
>> $ cygcheck -f /usr/bin/cygiconv-2.dll
>> libiconv2-1.14-3
>
> yes, libiconv2-1.14-3, is what i see also
>
> i really, really need to re-install cygwin from scratch on this machine. it seems that every problem i see cannot be replicated.
>
> While trying to debug my "graphics characters don't appear correctly" issue, i did try to set-up a new install directory and use that, but maybe that's not good enough.
>
> Can I just back up my home directory, kill the entire cygwin64 directory and start over ?
>
I suggest to install in a parallel directory, they works fine without
interference, eg in my system I have:
08.06.2020 19:37 <DIR> cygwin32
22.04.2020 21:32 <DIR> cygwin32T
19.07.2020 19:17 <DIR> cygwin64
22.04.2020 21:37 <DIR> cygwin64T
In this way you can copy your home more easily and kill the old one when
everything is fine.
Regards
Marco
next prev parent reply other threads:[~2020-07-19 19:15 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 [this message]
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
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=d1fd6d18-e398-b6c8-5553-1ee2129d05a5@gmail.com \
--to=marco.atzeri@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).