From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>,
Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: Pedro Alves <pedro@palves.net>,
Simon Marchi <simon.marchi@efficios.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v3 6/6] gdb/solib: C++ify solib_ops
Date: Sat, 28 Jun 2025 08:27:33 +0200 [thread overview]
Message-ID: <b9443041-bd69-4f60-ac24-6a7136c8092a@suse.de> (raw)
In-Reply-To: <2eb0f5ea-b11d-4e9d-8f94-e85a74a47bf9@simark.ca>
On 6/28/25 07:25, Simon Marchi wrote:
>
>
> On 2025-06-27 18:46, Thiago Jung Bauermann wrote:
>> Tom de Vries <tdevries@suse.de> writes:
>>
>>> On 6/26/25 20:04, Simon Marchi wrote:
>>>> I will push the series shortly, when I'm done
>>>> addressing these comments.
>>>
>>> I did a mingw cross build from trunk, and ran into:
>>> ...
>>> /usr/lib64/gcc/x86_64-w64-mingw32/9.2.0/../../../../x86_64-w64-mingw32/bin/ld:
>>> arch-utils.o:arch-utils.c:(.rdata$.refptr._Z21make_target_solib_opsv[.refptr._Z21make_target_solib_opsv]+0x0):
>>> undefined reference to `make_target_solib_ops()'
>>> collect2: error: ld returned 1 exit status
>>> make[1]: *** [Makefile:2253: gdb.exe] Error 1
>>> make[1]: Leaving directory '/data/vries/w/build/gdb'
>>> make: *** [Makefile:11391: all-gdb] Error 2
>>> $
>>> ...
>>>
>>> I suppose due to this commit.
>>
>> I'm also seeing it on a native build with FreeBSD on aarch64:
>>
>> CXXLD gdb
>> ld: error: undefined symbol: make_target_solib_ops()
>>>>> referenced by dicos-tdep.c:30 (/home/bauermann/src/binutils-gdb-wt/gdb/dicos-tdep.c:30)
>>>>> dicos-tdep.o:(dicos_init_abi(gdbarch*))
>>>>> referenced by dicos-tdep.c:30 (/home/bauermann/src/binutils-gdb-wt/gdb/dicos-tdep.c:30)
>>>>> dicos-tdep.o:(dicos_init_abi(gdbarch*))
>>>>> referenced by gdbarch-gen.c:160 (/home/bauermann/src/binutils-gdb-wt/gdb/gdbarch-gen.c:160)
>>>>> arch-utils.o:(gdbarch::gdbarch())
>>>>> referenced 1 more times
>> c++: error: linker command failed with exit code 1 (use -v to see invocation)
>> gmake[2]: *** [Makefile:2253: gdb] Error 1
>>
>
> Sorry about that. Unfortunately, I didn't manage to reproduce. I
> tried:
>
> - a native build on FreeBSD/amd64
> - a native build on FreeBSD/amd64 --enable-targets=all
> - a cross-build for mingw64 on Linux
>
> What I don't understand from your logs is that make_target_solib_ops is
> defined in solib-target.c, which is always included in the build
> (solib-target.c is specified in COMMON_SFILES, in gdb/Makefile.in). Do
> you see solib-target.c being compiled in these builds?
>
Hi Simon,
I see it being compiled and included in the link line.
I've attached the build log to a PR I've filed for this issue (
https://sourceware.org/bugzilla/show_bug.cgi?id=33118 ).
Thanks,
- Tom
> Simon
next prev parent reply other threads:[~2025-06-28 6:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 19:32 [PATCH v3 1/6] gdb/testsuite: check that "info shared" and "info linker-namespaces" before running don't crash Simon Marchi
2025-06-16 19:33 ` [PATCH v3 2/6] gdb/solib: fix formatting of "info linker-namespaces" error message Simon Marchi
2025-06-20 18:12 ` Pedro Alves
2025-06-26 17:35 ` Simon Marchi
2025-06-16 19:33 ` [PATCH v3 3/6] gdb/solib: add solib -> solib_ops backlink Simon Marchi
2025-06-20 18:17 ` Pedro Alves
2025-06-16 19:33 ` [PATCH v3 4/6] gdb/solib: use solib::ops for operations that concern a single solib Simon Marchi
2025-06-20 18:17 ` Pedro Alves
2025-06-16 19:33 ` [PATCH v3 5/6] gdb/progspace: add solib_ops pointer in program_space Simon Marchi
2025-06-17 19:45 ` Guinevere Larsen
2025-06-17 20:33 ` Simon Marchi
2025-06-18 11:51 ` Guinevere Larsen
2025-06-18 14:43 ` Simon Marchi
2025-06-18 15:01 ` Guinevere Larsen
2025-06-20 18:19 ` Pedro Alves
2025-06-26 17:37 ` Simon Marchi
2025-09-02 14:49 ` Tom de Vries
2025-09-02 16:05 ` Simon Marchi
2025-09-02 16:34 ` Tom de Vries
2025-06-16 19:33 ` [PATCH v3 6/6] gdb/solib: C++ify solib_ops Simon Marchi
2025-06-20 18:20 ` Pedro Alves
2025-06-26 18:04 ` Simon Marchi
2025-06-27 22:04 ` Tom de Vries
2025-06-27 22:46 ` Thiago Jung Bauermann
2025-06-28 5:25 ` Simon Marchi
2025-06-28 6:27 ` Tom de Vries [this message]
2025-06-20 18:12 ` [PATCH v3 1/6] gdb/testsuite: check that "info shared" and "info linker-namespaces" before running don't crash Pedro Alves
2025-06-26 17:30 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9443041-bd69-4f60-ac24-6a7136c8092a@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.com \
--cc=thiago.bauermann@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox