Mail Archives: geda-user/2020/05/19/08:16:31
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--8323329-1901925522-1589889317=:1209
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Hi Shashank,
On Tue, 19 May 2020, Shashank Chintalagiri
(shashank DOT chintalagiri AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> All of a sudden, gschem (1.10.0 and git head) has started segfaulting
> on startup for me. To the best of my knowledge, nothing has changed on
> my computer. It was working one minute and then it wasn't.
>
> […]
>
> (gschem:27169): Gtk-WARNING **: 05:52:22.277: Unable to locate theme
> engine in module_path: "murrine",
as far as I can tell, this is a new bug. The first message indicates
what's wrong: for some reason, GTK isn't initializing properly.
Could you please run gschem under gdb, once with G_DEBUG=fatal_warnings
and once with G_DEBUG=fatal_criticals, and see where execution breaks?
On Mon, 18 May 2020, John Conover wrote:
> Yes, gschem(1) is doing a lot of core dumps, coming from the GTK/GDK
> system.
If this is reproducible on your system, that would be really helpful.
gschem only very rarely crashes on my system (once a year or so) which
makes this hard for me to debug.
> I tried to find it from gdb after a compile on amd64, but to no avail.
I believe it is some kind of memory corruption, which would mean memcheck
or something similar is required for meaningful debugging. Unfortunately,
messages are flooded with problems with Guile, so I postponed this until
gEDA/gaf can run without Guile.
Roland
--8323329-1901925522-1589889317=:1209--
- Raw text -