public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: graph (plotutils) seg-faulting
Date: Sun, 19 Jul 2020 08:04:48 +0200	[thread overview]
Message-ID: <cf4e8e11-0289-f3e2-da26-bef9ac5c3284@gmail.com> (raw)
In-Reply-To: <20200718141223.0736bb2c@quarternote>

On 18.07.2020 23:12, briand@pounceofcats.com wrote:
> Hi,
> 
> So i noticed graph wasn't doing anything, i could even get it to respond to the help argument.
> 
> I attached strace to it, and it shows that it was seg-faulting.
> 
> I _just_ did an update, specifically to see if that would fix it and it did not.
> 
> 1 could someone reproduce this ?
> 2 what should i do for a bug report ?
> 
> I was running graph in a terminal in X not in a terminal window under win10.
> 
> Thanks,
> 

Hi Brian,
graph is working for me.

Please provide the cygcheck.out, as attachment, for your system,
  as mentioned in

Problem reports:      https://cygwin.com/problems.html


So first, is a simple test working ?

$ echo 0 0 1 1 2 0 | spline | graph > test.meta
$ plot -T X test.meta

if yes, how I can replicate your segfault ?

If the strace is not too large, can you attach to your reply ?
If it is too long send to me directly by private mail.


Regards
Marco

  reply	other threads:[~2020-07-19  6:04 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 [this message]
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
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=cf4e8e11-0289-f3e2-da26-bef9ac5c3284@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).