Re: Keep local symbols of rump libraries

[Ryota Ozaki <ozaki-r%netbsd.org@localhost>]

On Mon, Apr 10, 2017 at 11:15 PM, Kamil Rytarowski <n54%gmx.com@localhost> wrote:
> On 10.04.2017 12:22, Ryota Ozaki wrote:
>> Hi,
>>
>> I'm using ATF tests running rump kernels (rump_server)
>> for development and debugging. When a rump kernel gets
>> panic, it dumps a core file from which we can obtain
>> a backtrace by using gdb.
>>
>> Unfortunately local symbols (i.e., static functions)
>> in a backtrace are unresolved because they are stripped
>> by the linker (and objdump). That makes debugging a bit
>> difficult.
>>
>> The patch introduces a compile option for rump kernels
>> called RUMP_KEEPSYMBOLS to keep such symbols:
>>   http://www.netbsd.org/~ozaki-r/rumplibs-keep-symbols.diff
>>
>> The option is disabled by default to not increase
>> the size of all rump libraries.
>>
>> I'm not so familiar with the NetBSD build system and
>> Makefiles, so the patch may be wrong or clumsy.
>>
>> Any comments?
>>
>> Thanks,
>>   ozaki-r
>>
>
> There are already available the following options:
> MKDEBUG
> MKDEBUGLIB
> MKKDEBUG
>
> How about MKDEBUGRUMP or MKRUMPDEBUG?

I intended to provide the option as a rump-specific option
(like options described in sys/rump/README.compileopts), not
a global build option, because it's rump-specific.

But as Chuck suggested in another mail, if the option is useful
for other than rump libraries, making the option global would
be good. Though I'm not sure if the word DEBUG suits for the
purpose (keep local symbols) while DEBUG indicates that it adds
debugging symbols.

  ozaki-r