After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757196 - Synopsys design compiler segfaults with glib version>2.44.1
Synopsys design compiler segfaults with glib version>2.44.1
Status: RESOLVED INCOMPLETE
Product: glib
Classification: Platform
Component: general
2.45.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2015-10-27 15:52 UTC by jckeerthan
Modified: 2017-11-17 14:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
backtrace (2.38 KB, text/plain)
2015-10-27 15:52 UTC, jckeerthan 		Details

Description jckeerthan 2015-10-27 15:52:05 UTC 
Created attachment 314243 [details]
backtrace

Synopsys design compiler (proprietary software) segfaults when current versions of glib2 are installed. The last known working glib2 version is 2.44.1

I've attached the backtrace of the coredump.
Comment 1 Emmanuele Bassi (:ebassi) 2015-10-27 15:55:29 UTC 
You should open a bug against the compiler, since we cannot test it and we're definitely not segfaulting in the compilers we can (and, indeed, do) test.
Comment 2 jckeerthan 2015-10-27 15:57:30 UTC 
The program I mentioned is not a C compiler, it is an EDA program. I installed glib2 from my distro's(Archlinux) repositories.
Comment 3 Dan Winship 2015-10-27 16:34:31 UTC 
already fixed in master and will be in 2.46.2

*** This bug has been marked as a duplicate of bug 755609 ***
Comment 4 jckeerthan 2015-10-28 07:24:08 UTC 
It looks like the Archlinux package already has the fix mentioned in the other bug. However, Synopsys DC still segfaults. I face this problem even with glib-git.
Comment 5 jckeerthan 2015-11-04 12:28:34 UTC 
Still broken with glib2-git-2.47.1.15.g236e804
Comment 6 Philip Withnall 2017-11-17 14:57:49 UTC 
That backtrace doesn’t contain any particularly useful information, and there hasn’t been any activity here for 2 years, so I’m going to close this bug.

If this is still an issue with the latest version of GLib, please re-open this bug and provide an updated backtrace, including debug symbols, with G_DEBUG=gc-friendly set in the environment. My guess is that this is some kind of memory corruption problem, so running with G_DEBUG=gc-friendly will see if it’s in GSlice or not. Getting a log from valgrind’s memcheck tool would also be useful. Thanks.