#511463 [ddd] ddd: Symbol `_XmStrings' has different size in shared object, consider re-linking

Package:
ddd
Source:
ddd
Description:
Data Display Debugger, a graphical debugger frontend
Submitter:
Kaiwang Chen
Date:
2025-01-27 01:36:02 UTC
Severity:
normal
#511463#5
Date:
2009-01-11 09:01:27 UTC
From:
To:
--- Please enter the report below this line. ---
when start ddd, got warning:
ddd: Symbol `_XmStrings' has different size in shared object, consider re-linking

ignoring the warning, got:
Warning: XmStringGetNextComponent: unknown type 142846224

(Annoyed?  Try 'Edit->Preferences->General->Suppress X Warnings'!)


Debian Release: 5.0
  500 testing         security.debian.org
  500 testing         ftp.us.debian.org
--- Package information. ---
Depends                 (Version) | Installed
=================================-+-==================
lesstif2                          | 1:0.95.0-2.1
libc6           (>= 2.3.2.ds1-21) | 2.7-16
libgcc1            (>= 1:4.0.0-7) | 1:4.3.2-1.1
libice6                           | 2:1.0.4-1
 OR xlibs              (>> 4.1.0) |
libncurses5            (>= 5.4-5) | 5.7+20081213-1
libsm6                            | 2:1.0.3-2
 OR xlibs              (>> 4.1.0) |
libstdc++6          (>= 4.0.0-10) | 4.3.2-1.1
libx11-6                          | 2:1.1.5-2
 OR xlibs              (>> 4.1.0) |
libxaw7                (>> 4.1.0) | 2:1.0.4-2
libxext6                          | 2:1.0.4-1
 OR xlibs              (>> 4.1.0) |
libxmu6                           | 2:1.0.4-1
 OR xlibs              (>> 4.1.0) |
libxp6                            | 1:1.0.0.xsf1-2
 OR xlibs              (>> 4.1.0) |
libxpm4                           | 1:3.5.7-1
 OR xlibs              (>> 4.1.0) |
libxt6                            | 1:1.0.5-3
 OR xlibs              (>> 4.1.0) |



*** This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the intended recipient.  Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited.  If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto. ***

#511463#10
Date:
2009-07-10 01:54:51 UTC
From:
To:
Same problem as described, with version 3.3.11 (on Debian testing, amd64):


ddd: Symbol `_XmStrings' has different size in shared object, consider re-linking
GNU DDD 3.3.11 (x86_64-pc-linux-gnu), by Dorothea Luetkehaus and Andreas Zeller.
Copyright (C) 1995-1999 Technische Universitaet Braunschweig, Germany.
Copyright (C) 1999-2001 Universitaet Passau, Germany.
Copyright (C) 2001 Universitaet des Saarlandes, Germany.
Copyright (C) 2001-2004 Free Software Foundation, Inc.
(gdb) Warning: XmStringGetNextComponent: unknown type 32549072

(Annoyed?  Try 'Edit->Preferences->General->Suppress X Warnings'!)
Warning: XmStringGetNextComponent: unknown type 30800752


(gdb) quit


After moving the old configuration directory (~/.ddd), ddd is running
now:


ddd: Symbol `_XmStrings' has different size in shared object, consider re-linking
Creating "/home/lee/.ddd/"...
Creating "/home/lee/.ddd/"...done.
Creating "/home/lee/.ddd/sessions/"...
Creating "/home/lee/.ddd/sessions/"...done.
Creating "/home/lee/.ddd/themes/"...
Creating "/home/lee/.ddd/themes/"...done.
Warning: XmStringGetNextComponent: unknown type 24727264

(Annoyed?  Try 'Edit->Preferences->General->Suppress X Warnings'!)
Warning: XmStringGetNextComponent: unknown type 24801568

Warning: XmStringGetNextComponent: unknown type 24618304

Warning: XmStringGetNextComponent: unknown type 24464352

Warning: XmStringGetNextComponent: unknown type 24504624

Warning: XmStringGetNextComponent: unknown type 24498656

Warning: XmStringGetNextComponent: unknown type 25514336

Warning: XmStringGetNextComponent: unknown type 25494560

Warning: XmStringGetNextComponent: unknown type 24498656

#511463#15
Date:
2010-08-11 01:53:50 UTC
From:
To:
I have/had this bug running ddd under a new installation of Debian Lenny
5.05 amd64.  It is now solved.

In my case this bug didn't only cause the error message, but also caused
ddd to become sluggish or unresponsive, consume large amounts of CPU or
hang when accessing menus.  For example, clicking on Edit->Preferences
and then changing tabs from General to Source would take many seconds,
with top showing 10-20% CPU.  Changing tabs to Data would sometimes
complete and sometimes just hang, with CPU going to 40%.  Clicking OK
would then hang completely with CPU going to 100%.  I would then have to
kill ddd.  This made ddd close to unusable.

The problem can be fixed by downgrading your version of the lesstif2
library /usr/lib/libXm.so.2.0.1

Unfortunately at the time of writing the oldstable Etch packages don't
seem to be online.  It looks like they've been removed from
http://packages.debian.org/oldstable/ and don't yet show up in
http://archive.debian.net/   I don't know if the Etch package would have
been old enough anyway.

Going back further there is Sarge, available from http://archive.debian.net/
I used the Xm lib from the lesstif2 package version 0.93.94-11.4 and
this solves the problem.  Note that the library is still called
libXm.so.2.0.1 but it's clearly different, since it works.

I've seen ddd fail on 4 successive invocations when using the original
library, then succeed on 8 invocations using the new Xm library,
changing tabs multiple times and opening and closing windows.  I gave it
this testing because the very first time I ran with the new library it
worked for a moment and then failed.  I can't explain this and can't
reproduce it.  My best (admittedly feeble) guess is that something was
cached somewhere.  Anyway, with the new lib in place I now can't get it
to fail again.  Yet :)

On many architectures you can probably download the Sarge package
directly from the website, unpack it with dpkg -x, and copy the libXm to
/usr/lib/ and be done.

Unfortunately Sarge packages aren't available for the amd64
architecture, so to get this to work I had to compile the package from
source.  Below therefore is a quick how-to for amd64 users who want to
fix this problem on their system.

Thanks to the folks on this thread
http://www.mail-archive.com/cooker@linux-mandrake.com/msg129902.html
back in 2003 for providing the solution to this problem.

/rob
--------------------------------------------------------------------------------------------- amd64 how-to under Debian Lenny 1) the source can be downloaded from the Debian Sarge package page : http://archive.debian.net/sarge/lesstif2 the three links on the right hand side under Download Source Package. 2) Packages you need which are/are used as generic code-building packages: sudo aptitude install fakeroot sudo aptitude install autoconf sudo aptitude install bison sudo aptitude install debhelper sudo aptitude install flex sudo aptitude install libtool autoconf gets automake which is automake1.10 You actually need automake1.6 but that isn't available from the Lenny Repositories. We'll deal with this below. Packages you need which are development and specific to this build: sudo aptitude install libice-dev libsm-dev libx11-dev libxext-dev libxp-dev libxt-dev libxrender-dev libxft-dev libfontconfig1-dev libfreetype6-dev 3) Following http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html In the directory containing your source tar files: dpkg-source -x lesstif1-1_0.93.94-11.4.dsc 4) You have to edit the lesstif1-1-0.93.94/debian/rules file to remove the 1.6 references to aclocal and automake. Make sure you end up with calls to aclocal and automake just like that. 5) Run this. It takes a few minutes. cd lesstif1-1-0.93.94 dpkg-buildpackage -rfakeroot -b -d 6) It falls over eventually complaining about a man page, but not before it compiles the libs. They are available from debian/lesstif2/usr/lib/ You might like to archive your original /usr/lib library before you sudo cp libXm.so.2.0.1 /usr/lib/libXm.so.2.0.1
#511463#20
Date:
2010-08-11 17:53:08 UTC
From:
To:
I think I should add that the more serious consequences of this bug
(machine hanging, etc) were seen when running ddd on my 64bit Linux
server via a ssh session from, and with the display exported to, a 32bit
Windows XP machine running the Cygwin X server.  I haven't tried running
an X server directly on the Linux box, but I did just try NX NoMachine
in place of the Cygwin X server, which I think essentially fakes an X
server on the Linux box, and I found that the newer (package supplied)
Xm library does not cause the hanging problem (though clicking on the
ddd window did once disconnect my NX session).  If console X sessions
are similarly tolerant of this bug that might explain why the more
serious consequences I reported haven't been reported before.

#511463#25
Date:
2010-12-08 10:26:51 UTC
From:
To:
I have had this problem for a long time, but it recently got fixed
automatically during a dist-upgrade. It may have been the move
to 3.3.12, but I am not sure. Can the reporters maybe check
if they can still reproduce the bug with an up-to-date installation?

#511463#30
Date:
2025-01-26 22:15:19 UTC
From:
To:
I  have  a  profitable  business  deal  I'd  like  to  share  for your  perusal. It  needs  int'l  collaboration  a?d  might  interest  you.
zhaojiangwenli@yahoo.com