public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tony Richardson <richardson.tony@gmail.com>
To: briand@pounceofcats.com
Cc: Marco Atzeri via Cygwin <cygwin@cygwin.com>
Subject: Re: graph (plotutils) seg-faulting
Date: Thu, 23 Jul 2020 07:49:09 -0500	[thread overview]
Message-ID: <CAPp9Z=VWVg69fxYNMY5pnFeRYu8rze0rDUN0p0+6YYyyQYAYsw@mail.gmail.com> (raw)
In-Reply-To: <20200722224355.1d09e0c6@quarternote>

On Thu, Jul 23, 2020 at 12:44 AM <briand@pounceofcats.com> wrote:

> On Wed, 22 Jul 2020 20:10:44 +0200
> Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
>
> <snip>
>
> > If it is NOT a Bloda than may be it is Windows itself.
>
> Well I know that my work computer is running a lot of crap to "protect" me.
> I tried to go through and start disabling it today, and as you might guess
> I can't.
>
> I have since upgraded win10 and i'm still seeing the same problem.  And
> probably important to mention that my home win 10 box has no problems.
>
> Certainly on my work laptop it's probably a case of BLODA.
>
> BTW, i had a broken latex install that i couldn't figure out so i
> re-installed cygwin again, and that fixed my latex problem but graph was
> still broken.
>

I'm having issues on two computers.  The only thing that I'm running on the
BLODA FAQ list is Windows Defender.  I still have issues when I turn that
off.  It could be something else though, but I try to keep both machines as
clean as possible.  Everything else that I use (gcc, g++, make, vi,  rsync,
octave, cygwin-x, ...) all seem to work fine.

Tony

  reply	other threads:[~2020-07-23 12:49 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
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 [this message]
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='CAPp9Z=VWVg69fxYNMY5pnFeRYu8rze0rDUN0p0+6YYyyQYAYsw@mail.gmail.com' \
    --to=richardson.tony@gmail.com \
    --cc=briand@pounceofcats.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).