Glance fails and coredumps?

[Matthew Pegge_1]

# glance
/usr/lib/dld.sl: Unresolved symbol: [Vtable]key:__dt__21__versioned_type_infoFv
(data) from /opt/perf/lib/libnums.sl
Abort(coredump)

thsi is running HPUX 10.20, but has worked fine for years.

[Steven E. Protter]

Might be useful to do this:

strings core

See what if anything useful is in there.

Get out your Application CD and isntall the latest version of Glance.

Get out your old pathes and make sure you are properly patched.

If none of this works, take a look at filesize and checksum on /opt/perf/lib/libnums.sl and consider copying it in from another 10.20 system.

Long run: Being on 10.20 is a bad place to be. Plan an upgrade.

SEP

[T G Manikandan]

Did you do any upgrade/insatllation of Measureware.
Probably the .sl file got updated with that latest installation.

Revert on any recent installations like Measureware.

[T G Manikandan]

Also any recent patches updated on the machine

[Robert-Jan Goossens]

Hi Matthew,

Check if you have the same versions running for measureware and glance,

# perfstat -v

http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&admit=552267591+1064822362199+28353475&docId=200000066940217

Hope it helps,

Robert-Jan.

[Stanimir]

/usr/lib/dld.sl: Unresolved symbol: x (code) from ./libmylib.sl
Abort(coredump)
The message says that there was a reference to x() found in libnums.sl, but neither the
executable nor one of the shared libraries contain it.
Usually there are two reasons for such a problem. Either this is a versioning problem where at runtime different versions of the shared libraries are used than at build time. In general, the
first approach to resolve this problem is to get the latest versions of all used shared libraries.
Or if this is a third party program, ask the vendor if it requires certain versions of the libraries, and install them.
This problem could also be caused by a link time problem. Normally, the linker checks if
there are unsatisfied symbols, but only for executables, not for shared libraries. If a shared library references symbols from another library, but it is not linked against this library, the linker will not complain. When linking an executable against this library, but not against the
dependent library, the linker again does not check for unresolved symbols in shared libraries and does not realize that there's something missing.
You must find the missing symbol with nm(1), and put the path to the library where
you found the symbol into LD_PRELOAD before starting the program.

[Jakes Louw]

Can also be caused if the server is out of memory. Use vmstat to check the current state of the server.

[ranganath ramachandra]

it seems that you have a newer /opt/perf/lib/libnums.sl (built with a newer aCC, perhaps) and an older application (built with aCC older than B.01.07).

i see the symbol defined in /usr/lib/libCsup.sl . you can try running the application by setting LD_PRELOAD=/usr/lib/libCsup.sl . this _may_ lead to unpredictable behaviour though.