From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: xgraph 12.1-3 segfaults when run
Date: Sat, 02 Apr 2016 13:24:00 -0000 [thread overview]
Message-ID: <56FFC7E1.2010903@gmail.com> (raw)
In-Reply-To: <56FA9B95.4070305@iki.fi>
On 29/03/2016 17:13, Stefan Parviainen wrote:
> Dear list,
>
> I installed xgraph 12.1-3 using the Cygwin installer, but it seems to
> segfault immediately when run (e.g. "xgraph data.txt"). GDB gives the
> following:
>
> Starting program: /usr/bin/xgraph data.txt
> [New Thread 7848.0x2040]
> [New Thread 7848.0x548]
> [New Thread 7848.0x249c]
> [New Thread 7848.0x11fc]
> [New Thread 7848.0x94]
> [New Thread 7848.0x15b0]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000010040f946 in st_lookup (table=0x60004dc0c, key=0x1004227ac
> "Debug", value=0xffffc4c8) at st.c:153
> 153 st.c: No such file or directory.
> (gdb) backtrace
> #0 0x000000010040f946 in st_lookup (table=0x60004dc0c, key=0x1004227ac
> "Debug", value=0xffffc4c8) at st.c:153
> #1 0x0000000100410b84 in param_set (name=0x1004227ac "Debug",
> type=BOOL, val=0x1004227a6 "false") at params.c:114
> #2 0x0000000100417cc7 in InitSets (o=4) at init.c:152
> #3 0x00000001004011ef in main (argc=2, argv=0xffffcc30) at xgraph.c:126
>
> Any ideas what's going on? cygcheck.out is attached.
>
I can confirm the issue, also rebuilding from source
does not solve the issue.
I am looking to rebuild using debian patches, I will let you know
Marco
--
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:[~2016-04-02 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 15:13 Stefan Parviainen
2016-04-02 13:24 ` Marco Atzeri [this message]
2016-04-08 18:06 ` Marco Atzeri
2016-04-09 9:39 ` Stefan Parviainen
2016-04-10 3:14 ` Query of type of memcpy (and sys_errlist) on Cygwin Tatsuro MATSUOKA
2016-04-10 7:10 ` Hans-Bernhard Bröker
2016-04-10 22:48 ` Tatsuro MATSUOKA
2016-04-10 7:12 ` Marco Atzeri
2016-04-10 22:52 ` Tatsuro MATSUOKA
2016-04-10 23:20 ` Tatsuro MATSUOKA
2016-04-11 7:52 ` Csaba Raduly
2016-04-11 8:13 ` Tatsuro MATSUOKA
2016-04-10 23:27 ` Tatsuro MATSUOKA
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=56FFC7E1.2010903@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).