a SEGV in Xlib doesn't mean it's actually caused by Xlib ...
the Subject: line is very Zen-like. :-) i can hear the sound of my left hand clapping in the woods.
Konsole for 3.4.1 was driving me nuts. it would crash every 3rd time i'd start it, but only on Solaris 10 x86, not on UltraSPARC. not the first time, and not the second time. only the third time, always in the same spot:
[email protected] ([email protected]) signal SEGV (no mapping at the fault address) in XCheckTypedWindowEvent at 0xfcb960b8
well this required some head scratching.
so, after some digging around, i decided to take a very bold step, and actually implement the constructors in sessioniface.cpp and konsoleiface.cpp (which don't even exist). nothing fancy, just vanilla constructors/destructor/assignment operator. then i changed the constructors for Konsole and TESession to initialize their immediate superclass(es):
Konsole::Konsole(const char* name, int histon, bool menubaron, bool tabbaron, bool frameon, bool scrollbaron, QCString type, bool b_inRestore, const int wanted_tabbar, const QString &workdir )
TESession::TESession(TEWidget* _te, const QString &_pgm, const QStrList & _args, const QString &_term, ulong _winId, const QString &_sessionId, const QString &_initial_cwd)
and now the SEGV disappeared without a trace. transparent Konsole, antialiased fonts, XRender support, Midnight Commander (i don't really use it, but i *could* if i wanted to) :-P
these little things in life which can make such a huge difference. like constructors, for instance. :-P
I hate bugs like that.