[Bug 8756] New: Dynamic Linker with Standalone Support does not print any messages on mips arch

bugzilla at busybox.net bugzilla at busybox.net
Sat Mar 5 17:19:03 UTC 2016


https://bugs.busybox.net/show_bug.cgi?id=8756

            Bug ID: 8756
           Summary: Dynamic Linker with Standalone Support does not print
                    any messages on mips arch
           Product: uClibc
           Version: 0.9.33.2
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at uclibc.org
          Reporter: nixscripter at gmail.com
                CC: uclibc-cvs at uclibc.org
  Target Milestone: ---

Back in 2014, there was an issue reported on the mailing with the dynamic
linker on MIPS refusing to print any messages:

http://lists.uclibc.org/pipermail/uclibc/2014-January/048199.html

There was trouble recreating it, but I believe I have found the key: as alluded
to on the mailing list, there is no _dl_dprintf anywhere in the MIPS
architecture.

So how did it ever work? Well, apparently most people enable NPTL-style
threads, and this definition in libpthread/nptl/sysdeps/generic/dl-tls.c makes
it work:

#define _dl_malloc      malloc
#define _dl_memset      memset
#define _dl_mempcpy     mempcpy
#define _dl_dprintf     fprintf
#define _dl_debug_file  stderr
#define _dl_exit        exit

Whereas I have threads turned off:

HAS_NO_THREADS=y
# LINUXTHREADS_OLD is not set
# LINUXTHREADS_NEW is not set
# UCLIBC_HAS_THREADS_NATIVE is not set

And there is apparently no _dl_dprintf, so it doesn't print.

I would submit a patch, but I don't know where would be best to add it.

And no, I cannot just enable threads because I have both target and toolchain
problems that made me turn them off.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the uClibc-cvs mailing list