Bug 204909 - valgrind warning on dlsym of non-existing symbol
valgrind warning on dlsym of non-existing symbol
Product: Fedora
Classification: Fedora
Component: glibc (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-09-01 05:37 EDT by Caolan McNamara
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 2.4.90-29
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-05 05:04:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Caolan McNamara 2006-09-01 05:37:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060830 Fedora/ Firefox/ pango-text

Description of problem:
#include <dlfcn.h>
int main(void)
        void *handle;
        handle = dlopen ("libm.so", RTLD_LAZY);
        dlsym(handle, "foobpe");
        return 0;

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. compile above -ldl
2. valgrind ./a.out

Actual Results:
==11913== Conditional jump or move depends on uninitialised value(s)
==11913==    at 0xA1C655: do_lookup_x (in /lib/ld-2.4.90.so)
==11913==    by 0xA1C96F: _dl_lookup_symbol_x (in /lib/ld-2.4.90.so)
==11913==    by 0xB353E2: do_sym (in /lib/libc-2.4.90.so)
==11913==    by 0xB35649: _dl_sym (in /lib/libc-2.4.90.so)
==11913==    by 0xB990A7: dlsym_doit (in /lib/libdl-2.4.90.so)
==11913==    by 0xA20B15: _dl_catch_error (in /lib/ld-2.4.90.so)
==11913==    by 0xB9956B: _dlerror_run (in /lib/libdl-2.4.90.so)
==11913==    by 0xB99032: dlsym (in /lib/libdl-2.4.90.so)
==11913==    by 0x804845E: main (in /home/caolan/a.out)

Expected Results:

Additional info:
Comment 1 Jakub Jelinek 2006-09-04 16:45:51 EDT
Ulrich fixed this in CVS, will show up in next rawhide build.

Note You need to log in before you can comment on or make changes to this bug.