public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: debugging cygwin / octave plot problem
Date: Tue, 24 May 2011 12:20:00 -0000	[thread overview]
Message-ID: <BANLkTikGyuvF3v9G79EHeG1ncN28AnUDhA@mail.gmail.com> (raw)

Hi,
I am trying to understand (eventually solve) the octave cygwin problem
present in cygwin-1.7.9.
http://cygwin.com/ml/cygwin/2011-03/msg00863.html

The issue arisen with

http://cygwin.com/ml/cygwin-cvs/2011-q1/msg00102.html

and it is due to the communication between octave and gnuplot.

Octave forks, execs gnuplot and communicate with gnuplot
for sending commands and receiving feedback.
The return channel is a named pipe in the form of "/tmp/oct-22xxx"

The problem seems on the return channel and octave receives EOF instead of the
expected message.

What is really making me mad is that
- if I use the internal debug mode of octave the problem disappear,
the return channels works fine.
- If I manually exec gnuplot and send command (with internal octave
popen2 / fputs /fgets) it also works
- if I try to run octave inside gdb, at plot gdb frozen and gnuplot never arise.

All these tests are performed from xterm using both 1.7.9 and the
latest cvs sources.

Have anyone suggestion how to overcome the gdb frozen behaviour ?


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

                 reply	other threads:[~2011-05-24 12:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BANLkTikGyuvF3v9G79EHeG1ncN28AnUDhA@mail.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).