libxt xthreads support completely broken

Bug #21171 reported by Reinhard Tartler
8
Affects Status Importance Assigned to Milestone
libxt (Ubuntu)
Fix Released
Medium
Daniel Stone

Bug Description

ddd seems to trigger this bug. Already reported in malone:
https://launchpad.net/malone/bugs/2129

Steps to reproduce:
apt-get source hello
cd hello-*
./configure
make

ddd src/hello

backtracing with libxt-dbg gets me this:

#0 0xb7d6172e in _XtWaitForSomething (app=0x8350868, ignoreEvents=0,
ignoreTimers=1,
    ignoreInputs=1, ignoreSignals=1, block=Variable "block" is not available.
) at ../../src/NextEvent.c:194
194 ../../src/NextEvent.c: Datei oder Verzeichnis nicht gefunden.
        in ../../src/NextEvent.c

I think this is a segfault in libxt, can you confirm this?

Revision history for this message
Daniel Stone (daniels) wrote :

awesome.

yeah, it is, probably related to the threading support. looks like it's quite
badly botched.

Revision history for this message
Daniel Stone (daniels) wrote :

okay, so I've just uploaded a version which should largely fix this. can't tell
at the moment whether the problem is lesstif or libxt.

Revision history for this message
Klaus Stengel (proger2) wrote :

(In reply to comment #2)
> okay, so I've just uploaded a version which should largely fix this. can't tell
> at the moment whether the problem is lesstif or libxt.

I can confirm the problem and still encounter it. Downloading the lesstif source
package (0.93.94-11.4ubuntu2) and recompiling solved the problem for me. I guess
the lesstif package is no longer ABI compatible with the current libraries and
just needs a recompile against the current versions.

Revision history for this message
Klaus Stengel (proger2) wrote :

lesstif1-1 (1:0.93.94-11.4ubuntu3) breezy; urgency=low
  * rebuild for new libxt (Related to Ubuntu #14943)
 -- Reinhard Tartler <email address hidden> Fri, 16 Sep 2005 22:00:09 +0200

Thanks, ddd now works again as expected.

Revision history for this message
Reinhard Tartler (siretart) wrote :

For me too. I'm closing this bug therefore. Thanks daniel!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.