public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "marian.buschsieweke at posteo dot net" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31851] GDB ignores absolute function symbols Date: Tue, 11 Jun 2024 21:45:37 +0000 [thread overview] Message-ID: <bug-31851-4717-xhTFQK4V0P@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31851-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31851 --- Comment #4 from Marian Buschsieweke <marian.buschsieweke at posteo dot net> --- Note: I extended the test application a bit: main.c: #include <stdio.h> extern void func(void); extern int data; extern int bss; int main(void) { volatile int *p; func(); printf("data = %d, bss = %d\n", data, bss); p = &data; *p = 1; p = &bss; *p = 2; printf("data = %d, bss = %d\n", data, bss); return 0; } func.c: #include <stdio.h> void func_impl(void) { puts("Hello from func"); } data.c: int data_impl = 42; int bss_impl = 0; additions to the linker script: PROVIDE(func = ABSOLUTE(func_impl)); /* ... */ PROVIDE(data = ABSOLUTE(data_impl)); /* ... */ PROVIDE(bss = ABSOLUTE(bss_impl)); With the above patch applied, the symbol "func" was correctly identified as a function, "bss" as .bss, and "data" as .data. I could successfully attach a break point to "func" and watch points to "data" and "bss", and they triggered as expected. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-11 21:45 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-06 12:35 [Bug gdb/31851] New: " marian.buschsieweke at posteo dot net 2024-06-06 13:50 ` [Bug gdb/31851] " marian.buschsieweke at posteo dot net 2024-06-06 13:51 ` marian.buschsieweke at posteo dot net 2024-06-11 21:38 ` marian.buschsieweke at posteo dot net 2024-06-11 21:45 ` marian.buschsieweke at posteo dot net [this message] 2024-06-12 11:11 ` marian.buschsieweke at posteo dot net 2024-06-12 12:40 ` tromey at sourceware dot org
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=bug-31851-4717-xhTFQK4V0P@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).