[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netbsd-current-users
Subject:    Re: odd missing symbols like rumpns_lockdebug_* in an i386 build
From:       christos () astron ! com (Christos Zoulas)
Date:       2020-05-29 12:02:05
Message-ID: raqtjs$usk$1 () ciao ! gmane ! io
[Download RAW message or body]

In article <m1jePSL-0036tPC@more.local>,
Greg A. Woods <current-users@netbsd.org> wrote:
>
>They are still there on the real i386 build:
>
>	$ nm usr/lib/librump.so | fgrep rumpns_lockdebug_
>	         U rumpns_lockdebug_alloc
>	         U rumpns_lockdebug_barrier
>	         U rumpns_lockdebug_free
>	         U rumpns_lockdebug_locked
>	         U rumpns_lockdebug_mem_check
>	         U rumpns_lockdebug_unlocked
>	         U rumpns_lockdebug_wantlock
>
>So, I thought I'd try to find out where these symbols might have come
>from, but I came up completely empty with no matches:
>
>	$ cd /usr/src
>	$ find . -type f -print0 | xargs -0 fgrep rumpns_lockebug_
>	$
>
>So, now what?  Where else should I look to debug this mess?
>
>I'm guessing they are formed either with merging operator (##) in a
>macro somewhere, but where, and how do I find it without carefully
>reading everything related?

I believe they are generated by symbol renaming at the link phase,
by prepending "rumpns_" to the real symbols in the object files.

christos

[prev in list] [next in list] [prev in thread] [next in thread]