From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Octave crashes with segfault
Date: Sat, 12 May 2018 03:38:00 -0000 [thread overview]
Message-ID: <20180512123747.419c765960e26a299a156f4f@nifty.ne.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
Hi, cygwin folks.
I found octave cannot start, or crashes by plot command in recent
32bit cygwin. This occurs in Windows 10 (1709 or later).
It seems that this is a problem of fontconfig package.
To reproduce this:
1. Install 32bit version of cygwin with the following packages.
- octave
- gnuplot
- xorg-server
- dbus
2. execute 'dbus-uuidgen'. Without this step, octave complains
about dbus.
3. execute 'run XWin -multiwindow'
4. execute 'export DISPLAY=':0.0'
5.1 execute 'octave'. This fails with the message:
octave exited with signal 11
5.2 execute 'octave -W' and issue the command 'plot([])'.
This fails with the message:
panic: Segmentation fault -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
Segmentation fault (core dumped)
Workaround 1:
Remove /usr/share/fonts/microsoft/bahnschrift.ttf
Workaround 2:
Build fontconfig package from source code and replace
cygfontconfig-1.dll.
cygcheck.out in failure environment is attached.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 205324 bytes --]
[-- Attachment #3: Type: text/plain, Size: 219 bytes --]
--
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 reply other threads:[~2018-05-12 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 3:38 Takashi Yano [this message]
2018-05-15 16:22 ` Takashi Yano
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=20180512123747.419c765960e26a299a156f4f@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).