public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tatsuro MATSUOKA <tmacchant2@yahoo.co.jp>
To: cygwin@cygwin.com
Subject: Re: gnuplot caca terminal work on Cygwin-x86 but not Cygwin-x86_64
Date: Wed, 14 May 2014 11:37:00 -0000	[thread overview]
Message-ID: <543751.52799.qm@web101106.mail.kks.yahoo.co.jp> (raw)
In-Reply-To: <20140513082932.GI2436@calimero.vinschen.de>

--- On Tue, 2014/5/13, Corinna Vinschen wrote:
> On May 13 08:54, Tatsuro MATSUOKA wrote:
> > --- On Mon, 2014/5/12, Corinna Vinschen  wrote:
> > > First, are you shure this is running under the snapshot?  what does
> > > `uname -a' print when called right before the below gdb call?
> > 
> > I have mis-operated. I have copied snapshot cywin1.dll to Cygwin_x86 but not Cygwin_x86_64.  I corrected makatake and found :
> > 
> > $ gdb src/gnuplot
> > [...]
> > 
> >         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 5892.0xba4]
> > [New Thread 5892.0x41c]
> > [New Thread 5892.0x142c]
> > [New Thread 5892.0x10ec]
> > [Thread 5892.0x10ec exited with code 0]
> > [New Thread 5892.0xae0]
> > [New Thread 5892.0x1a68]
> > [New Thread 5892.0x1bf0]
> > Could not connect to gnuplot_qt "qtgnuplot3112" . Starting a new one
> > 
> > Warning: slow font initializationgnuplot> Quit
> > (gdb) Undefined command: "rq".  Try "help".
> > (gdb) Undefined command: "q2qqqqqqqq".  Try "help".
> > (gdb) A debugging session is active.
> > 
> > ********************************************
> > Segmentation fault is no longer happned.
> > The behavior similar to that happened at Cygwin_x86.
> > 
> > Anyway thanks your advise.
> 
> Ok, so we know now that the crash was spurious and fixed in the
> snapshots.  That's good to know.  I can't help you with the other
> problems, unfortunately.
> 
> 
> Corinna

Perhaps it is better to carry out the further question at Qt forums.
Thank for your pointer so far.

I will hope that I can build gnuplot with qt terminal in the near future.

Tatsuro


--
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

      reply	other threads:[~2014-05-14  7:27 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
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 [this message]

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=543751.52799.qm@web101106.mail.kks.yahoo.co.jp \
    --to=tmacchant2@yahoo.co.jp \
    --cc=cygwin@cygwin.com \
    --cc=matsuoka@nuce.nagoya-u.ac.jp \
    /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).