Bug 103568 - XDefaultColormap crashes
Summary: XDefaultColormap crashes
Alias: None
Product: XQuartz
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: Jeremy Huddleston Sequoia
QA Contact: Jeremy Huddleston Sequoia
Depends on:
Reported: 2017-11-04 03:47 UTC by Yannick Heinrich
Modified: 2019-05-23 18:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Stack trace (48.55 KB, text/plain)
2017-11-04 03:47 UTC, Yannick Heinrich

Description Yannick Heinrich 2017-11-04 03:47:37 UTC
Created attachment 135235 [details]
Stack trace

I'm trying to install the magic VLSI tools on macOS High Sierra 10.13.1 (17B48) and XQuartz 2.7.11 (xorg-server 1.18.4).

The software is using tcl_tk with X11.

When I open the software a crash occurs when the function XDefaultColormap is called. This looks similar to another issue mentionned here http://opencircuitdesign.com/pipermail/magic-dev/2008-January/000497.html and here http://opencircuitdesign.com/pipermail/magic-dev/2008-January/000499.html and here http://opencircuitdesign.com/pipermail/xcircuit-dev/2010/000483.html.

The code of the program can be downloaded here: http://opencircuitdesign.com/magic/archive/magic-8.1.191.tgz

The function that causes the crash is named GrTkInit and can be located in graphics/grTk1.c.

To install the software on mac:

brew install tcl-tk
export TCL_DIR=$(brew --prefix tcl-tk)
./configure --prefix=$(pwd)/mac --with-tcl=$TCL_DIR/lib --with-tk=$TCL_DIR/lib
make install

Stack trace is attached.
Comment 1 GitLab Migration User 2019-05-23 18:32:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/796.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.