Re: Debugging containerized glibc tests with gdb (a developer use case for outside-of-container debugging).
Carlos O'Donell <[email protected]>
| Newsgroups | gmane.comp.lib.glibc.alpha,gmane.comp.gdb.devel |
|---|---|
| Message-ID | <[email protected]> |
On 12/26/19 3:21 PM, Gabriel F. T. Gomes wrote: > Hi, Carlos, > > I tried this on several systems (varying archs and distros), but I wasn't > able to reproduce it (with elf/tst-ldconfig-bad-aux-cache)... > > On Fri, 20 Dec 2019, Carlos O'Donell wrote: > >> GNU gdb (GDB) Fedora 8.3-7.fc30 >> [...] >> This GDB was configured as "x86_64-redhat-linux-gnu". > > ... even on Fedora 30 for x86_64, so I'm wondering if there's anything in > your configure options that I should try and mimic (I already tried some > combinations of --enable-profile --enable-addons --enable-multi-arch > --enable-tunables --enable-stack-protector=all, but I only tried that with > the system compiler (gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)). > >> warning: Could not load shared library symbols for /home/carlos/build/glibc-gr-localedef/elf/ld.so. > > I never got this. Did you try --enable-hardcoded-path-in-tests? >> warning: Unable to find dynamic linker breakpoint function. > > Nor this. > >> warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable. Connect to gdbserver inside the container. > > But this one, I got, too. > -- Cheers, Carlos.