[Bug translator/11735] similarly named executables/libraries get probed/detected wrongly

mjw at redhat dot com sourceware-bugzilla@sourceware.org
Tue Jun 22 01:27:00 GMT 2010


------- Additional Comments From mjw at redhat dot com  2010-06-21 12:34 -------
After commit 23c2d7 [PR11722 user_long(uaddr) should fetch a user space long (in
case of 32-on-64)] make installcheck RUNTESTFLAGS=usymbols.exp should PASS on
x86_64.

But if you revert commit 2c8f96 from comment #1 it actually fails:

Host: Linux springer.wildebeest.org 2.6.32-36.el6.x86_64 #1 SMP Wed Jun 16
15:48:48 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
Snapshot: version 1.2/0.147 commit release-1.2-298-g23c2d7d + changes
GCC: 4.4.4 [gcc (GCC) 4.4.4 20100611 (Red Hat 4.4.4-8)]
Distro: Red Hat Enterprise Linux release 6.0 Beta (Santiago)

Running /usr/local/src/systemtap/testsuite/systemtap.context/usymbols.exp ...
FAIL: usymbols -m32

		=== systemtap Summary ===

# of expected passes		1
# of unexpected failures	1


End of testsuite/systemtap.log:

Executing on host: gcc
/usr/local/src/systemtap/testsuite/systemtap.context/usymbols_lib.c  -fPIC
-shared  -lm   -o /usr/local/build/systemtap-obj/testsuite/libusymbols.so   
(timeout = 300)
spawn -ignore SIGHUP gcc
/usr/local/src/systemtap/testsuite/systemtap.context/usymbols_lib.c -fPIC
-shared -lm -o /usr/local/build/systemtap-obj/testsuite/libusymbols.so
Executing on host: gcc
/usr/local/src/systemtap/testsuite/systemtap.context/usymbols.c  -g -O
-L/usr/local/build/systemtap-obj/testsuite -lusymbols
-Wl,-rpath,/usr/local/build/systemtap-obj/testsuite  -lm   -o
/usr/local/build/systemtap-obj/testsuite/usymbols    (timeout = 300)
spawn -ignore SIGHUP gcc
/usr/local/src/systemtap/testsuite/systemtap.context/usymbols.c -g -O
-L/usr/local/build/systemtap-obj/testsuite -lusymbols
-Wl,-rpath,/usr/local/build/systemtap-obj/testsuite -lm -o
/usr/local/build/systemtap-obj/testsuite/usymbols
cmd: stap -w -d /usr/local/build/systemtap-obj/testsuite/usymbols --ldd -c
/usr/local/build/systemtap-obj/testsuite/usymbols -e $script
cmd output: handler: main_handler (usymbols)
handler: lib_handler (libusymbols.so)
PASS: usymbols default
Executing on host: gcc
/usr/local/src/systemtap/testsuite/systemtap.context/usymbols_lib.c  -fPIC
-shared -m32  -lm   -o /usr/local/build/systemtap-obj/testsuite/libusymbols.so 
  (timeout = 300)
spawn -ignore SIGHUP gcc
/usr/local/src/systemtap/testsuite/systemtap.context/usymbols_lib.c -fPIC
-shared -m32 -lm -o /usr/local/build/systemtap-obj/testsuite/libusymbols.so
Executing on host: gcc
/usr/local/src/systemtap/testsuite/systemtap.context/usymbols.c  -g -O
-L/usr/local/build/systemtap-obj/testsuite -lusymbols
-Wl,-rpath,/usr/local/build/systemtap-obj/testsuite -m32  -lm   -o
/usr/local/build/systemtap-obj/testsuite/usymbols    (timeout = 300)
spawn -ignore SIGHUP gcc
/usr/local/src/systemtap/testsuite/systemtap.context/usymbols.c -g -O
-L/usr/local/build/systemtap-obj/testsuite -lusymbols
-Wl,-rpath,/usr/local/build/systemtap-obj/testsuite -m32 -lm -o
/usr/local/build/systemtap-obj/testsuite/usymbols
cmd: stap -w -d /usr/local/build/systemtap-obj/testsuite/usymbols --ldd -c
/usr/local/build/systemtap-obj/testsuite/usymbols -e $script
cmd output: handler: dtor_idx.6340 (usymbols)
handler: 0x00000000007e944c (libusymbols.so)
FAIL: usymbols -m32
line 1: expected "handler: main_handler (usymbols)", Got "handler: dtor_idx.6340
(usymbols)"


Note how it looks like the second -m32 testcase is using the symbol tables from
the default (64bit) testcase executables. How can that be?

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11735

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the Systemtap mailing list