From: Bruno Larsen <blarsen@redhat.com>
To: Bruno Larsen <blarsen@redhat.com>,
Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Subject: [PING][PATCH v2] gdb/testsuite: explicitly test for stderr in gdb.mi/mi-dprintf.exp
Date: Thu, 3 Aug 2023 15:43:39 +0200 [thread overview]
Message-ID: <21cdd6b8-62e9-a1e5-94ad-8b748f0ee80d@redhat.com> (raw)
In-Reply-To: <20230721095809.3479260-2-blarsen@redhat.com>
Ping!
--
Cheers,
Bruno
On 21/07/2023 11:58, Bruno Larsen wrote:
> As mentioned in commit 3f5bbc3e2075ef5061a815c73fdc277218489f22, some
> compilers such as clang don't add debug information about stderr by
> default, leaving it to external debug packages.
>
> This commit adds a way to check if GDB has access to stderr information
> when in MI mode, and uses this new mechanism to skip the related section
> of the test gdb.mi/mi-dprintf.exp. It also fixes an incorrect name for a
> test in that file.
>
> Co-Authored-By: Andrew Burgess <aburgess@redhat.com>
> ---
> gdb/testsuite/gdb.mi/mi-dprintf.exp | 11 ++++++++---
> gdb/testsuite/lib/mi-support.exp | 14 ++++++++++++++
> 2 files changed, 22 insertions(+), 3 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.mi/mi-dprintf.exp b/gdb/testsuite/gdb.mi/mi-dprintf.exp
> index e40fa6121fa..d771993386b 100644
> --- a/gdb/testsuite/gdb.mi/mi-dprintf.exp
> +++ b/gdb/testsuite/gdb.mi/mi-dprintf.exp
> @@ -127,6 +127,7 @@ proc mi_continue_dprintf {args} {
> mi_continue_dprintf "gdb"
>
> # The "call" style depends on having I/O functions available, so test.
> +set has_stderr_symbol [mi_gdb_is_stderr_available]
>
> if ![target_info exists gdb,noinferiorio] {
>
> @@ -136,9 +137,13 @@ if ![target_info exists gdb,noinferiorio] {
> mi_gdb_test "set dprintf-style call" ".*" "mi set dprintf style to call"
> mi_continue_dprintf "call"
>
> - mi_gdb_test "set dprintf-function fprintf" ".*" "mi set dprintf-channel stderr"
> - mi_gdb_test "set dprintf-channel stderr" ".*" "mi set dprintf channel"
> - mi_continue_dprintf "fprintf"
> + # Some compilers don't add information about stderr,
> + # so skip these tests if needed.
> + if {$::has_stderr_symbol} {
> + mi_gdb_test "set dprintf-function fprintf" ".*" "mi set dprintf function"
> + mi_gdb_test "set dprintf-channel stderr" ".*" "mi set dprintf channel"
> + mi_continue_dprintf "fprintf"
> + }
> }
>
> set target_can_dprintf 0
> diff --git a/gdb/testsuite/lib/mi-support.exp b/gdb/testsuite/lib/mi-support.exp
> index 49d5e2ef272..468c481ab95 100644
> --- a/gdb/testsuite/lib/mi-support.exp
> +++ b/gdb/testsuite/lib/mi-support.exp
> @@ -2883,3 +2883,17 @@ proc foreach_mi_ui_mode { var_name body } {
> }
> }
> }
> +
> +# Check if GDB has information about the stderr symbol.
> +proc mi_gdb_is_stderr_available {} {
> + set has_stderr_symbol false
> + gdb_test_multiple "-data-evaluate-expression stderr" "stderr symbol check" {
> + -re "\\^error,msg=\"'stderr' has unknown type; cast it to its declared type\"\r\n$::mi_gdb_prompt$" {
> + # Default value of false is fine.
> + }
> + -re "$::mi_gdb_prompt$" {
> + set has_stderr_symbol true
> + }
> + }
> + return $has_stderr_symbol
> +}
next prev parent reply other threads:[~2023-08-03 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 9:58 [PATCH " Bruno Larsen
2023-08-03 13:43 ` Bruno Larsen [this message]
2023-08-10 13:52 ` [PINGv2][PATCH " Guinevere Larsen
2023-08-23 9:59 ` [PINGv3][PATCH " Guinevere Larsen
2023-09-14 13:03 ` [PINGv4][PATCH " Guinevere Larsen
2023-09-15 0:29 ` [PATCH " Kevin Buettner
2023-09-15 7:36 ` Guinevere Larsen
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=21cdd6b8-62e9-a1e5-94ad-8b748f0ee80d@redhat.com \
--to=blarsen@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).