From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: gnuplot caca terminal work on Cygwin-x86 but not Cygwin-x86_64
Date: Mon, 12 May 2014 10:03:00 -0000 [thread overview]
Message-ID: <20140512094930.GA2436@calimero.vinschen.de> (raw)
In-Reply-To: <776162.73173.qm@web101101.mail.kks.yahoo.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]
On May 12 16:51, Tatsuro MATSUOKA wrote:
> I have downdoaded x86_64/cygwin1-20140509.dll.xz and execute gnuplot on gdb
First, are you shure this is running under the snapshot? what does
`uname -a' print when called right before the below gdb call?
> $ gdb src/gnuplot
> <snip>
> Reading symbols from /cygdrive/e/usr/Tatsu/cyg64work/gnuplotcvs/build/src/gnuplot...done.
> (gdb) r
> Starting program: /cygdrive/e/usr/Tatsu/cyg64work/gnuplotcvs/build/src/gnuplot
> [New Thread 9176.0x2614]
> [New Thread 9176.0x1494]
>
> G N U P L O T
> Version 5.0 patchlevel alpha last modified 2014-05-11
>
> Copyright (C) 1986-1993, 1998, 2004, 2007-2014
> Thomas Williams, Colin Kelley and many others
>
> gnuplot home: http://www.gnuplot.info
> mailing list: gnuplot-beta@lists.sourceforge.net
> faq, bugs, etc: type "help FAQ"
> immediate help: type "help" (plot window: hit 'h')
>
> Terminal type set to 'qt'
> gnuplot> plot sin(x)
> [New Thread 9176.0x1b50]
> [New Thread 9176.0x269c]
> [New Thread 9176.0x2780]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000007782a5a0 in vsprintf_s () from /cygdrive/c/Windows/system32/ntdll.dll
> (gdb) bt
> #0 0x000000007782a5a0 in vsprintf_s ()
> from /cygdrive/c/Windows/system32/ntdll.dll
>
> Is this information helpful?
Not really. We can't quite trust the information returned for frames
in one of the OS DLLs, but if this is really a vsprintf_s call, it's
weird since no Cygwin application would call a vsprintf functions
from ntdll.dll, if it's linked correctly.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-05-12 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 10:07 Tatsuro MATSUOKA
2014-05-01 10:51 ` Tatsuro MATSUOKA
2014-05-05 10:42 ` Corinna Vinschen
2014-05-11 23:47 ` Tatsuro MATSUOKA
2014-05-11 23:58 ` Tatsuro MATSUOKA
2014-05-12 7:28 ` Christopher Faylor
2014-05-12 7:51 ` Csaba Raduly
2014-05-12 9:35 ` Tatsuro MATSUOKA
2014-05-12 10:03 ` Corinna Vinschen [this message]
2014-05-13 0:00 ` Tatsuro MATSUOKA
2014-05-13 5:49 ` Tatsuro MATSUOKA
2014-05-13 9:18 ` Corinna Vinschen
2014-05-14 11:37 ` 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=20140512094930.GA2436@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).