Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 7/7] gdb/testsuite: Handle "symtab" option on windows-msvc
Date: Tue, 11 Aug 2026 02:45:58 +0100	[thread overview]
Message-ID: <20260811014558.3606251-8-pedro@palves.net> (raw)
In-Reply-To: <20260811014558.3606251-1-pedro@palves.net>

On windows-msvc, lld-link does not emit a COFF symbol table by
default, even with -debug or -debug:pdb (but does with -debug:dwarf),
so most no-debug-info testcases fail, as they can't run to main, etc.

Handle a "symtab" option request by passing -Wl,-debug:symtab to
lld-link.

Change-Id: Idfd81e80c24dc27f4878a572b8efbea4c4fe9269
---
 gdb/testsuite/lib/gdb.exp | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 084f6ff8358..772f69d9633 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -6838,6 +6838,18 @@ proc gdb_compile {source dest type options} {
 	    } else {
 		error "No idea how to force DWARF-5 in this compiler"
 	    }
+	} elseif { $opt == "symtab" } {
+	    if { [istarget "*-*-windows-msvc*"] } {
+		# lld-link does not emit a COFF symbol table by
+		# default, even with -debug or -debug:pdb.  Note
+		# -debug:dwarf implies -debug:symtab, and order does
+		# not matter.  Order matters only when settings
+		# conflict -- e.g., /debug:symtab /debug:nosymtab
+		# leaves symtab off (nosymtab wins, last-applied).
+		lappend new_options "ldflags=-Wl,-debug:symtab"
+	    } else {
+		# All other systems emit a symbol table by default.
+	    }
 	} else {
 	    lappend new_options $opt
 	}
-- 
2.54.0


      parent reply	other threads:[~2026-08-11  1:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11  1:45 [PATCH 0/7] gdb_compile nodebug => symtab Pedro Alves
2026-08-11  1:45 ` [PATCH 1/7] gdb/testsuite: Don't build a program for cvexpr.exp's last tests Pedro Alves
2026-08-11  1:45 ` [PATCH 2/7] gdb/testsuite: Remove gdb_can_simple_compile_nodebug Pedro Alves
2026-08-11  1:45 ` [PATCH 3/7] gdb/testsuite: Let gdb_simple_compile take empty default flags Pedro Alves
2026-08-11  1:45 ` [PATCH 4/7] gdb/testsuite: Don't pass "nodebug" to object compilations Pedro Alves
2026-08-11  1:45 ` [PATCH 5/7] gdb/testsuite: Rename nodebug => symtab Pedro Alves
2026-08-11  1:45 ` [PATCH 6/7] gdb/testsuite: Pass "symtab" to testcases that rely on minsyms Pedro Alves
2026-08-12 21:41   ` Luis
2026-08-11  1:45 ` Pedro Alves [this message]

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=20260811014558.3606251-8-pedro@palves.net \
    --to=pedro@palves.net \
    --cc=gdb-patches@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: 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