public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Christina Schimpe <cschimpe@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb, testsuite: Remove unnecessary call of "set print pretty on"
Date: Thu,  9 Feb 2023 18:50:48 +0000 (GMT)	[thread overview]
Message-ID: <20230209185048.A01F83858C5F@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=31cf28c7842497aa1f6472b7d76828cf009d2298

commit 31cf28c7842497aa1f6472b7d76828cf009d2298
Author: Christina Schimpe <christina.schimpe@intel.com>
Date:   Fri Oct 21 09:02:57 2022 -0700

    gdb, testsuite: Remove unnecessary call of "set print pretty on"
    
    The command has no effect for the loading of GDB pretty printers and is
    removed by this patch to avoid confusion.
    
    Documentation for "set print pretty"
    "Cause GDB to print structures in an indented format with one member per line"

Diff:
---
 gdb/testsuite/gdb.python/pretty-print-call-by-hand.exp                | 4 ----
 .../gdb.python/py-autoloaded-pretty-printers-in-newobjfile-event.exp  | 2 --
 2 files changed, 6 deletions(-)

diff --git a/gdb/testsuite/gdb.python/pretty-print-call-by-hand.exp b/gdb/testsuite/gdb.python/pretty-print-call-by-hand.exp
index 7ab2b1facf7..01ee7b9d3d2 100644
--- a/gdb/testsuite/gdb.python/pretty-print-call-by-hand.exp
+++ b/gdb/testsuite/gdb.python/pretty-print-call-by-hand.exp
@@ -50,8 +50,6 @@ proc start_test { breakpoint_comment } {
     gdb_breakpoint [gdb_get_line_number ${breakpoint_comment} ${testfile}.c ]
     gdb_continue_to_breakpoint ${breakpoint_comment} ".*"
 
-    gdb_test_no_output "set print pretty on" "starting to pretty print"
-
     set remote_python_file [gdb_remote_download host ${srcdir}/${subdir}/${testfile}.py]
     gdb_test_no_output "source ${remote_python_file}" "load python file"
 
@@ -64,8 +62,6 @@ with_test_prefix "run to frame" {
 	untested "couldn't run to main"
     }
 
-    gdb_test_no_output "set print pretty on" "starting to pretty print"
-
     set remote_python_file [gdb_remote_download host ${srcdir}/${subdir}/${testfile}.py]
     gdb_test_no_output "source ${remote_python_file}" "load python file"
 
diff --git a/gdb/testsuite/gdb.python/py-autoloaded-pretty-printers-in-newobjfile-event.exp b/gdb/testsuite/gdb.python/py-autoloaded-pretty-printers-in-newobjfile-event.exp
index 2217e2e6527..eefa99c8fa1 100644
--- a/gdb/testsuite/gdb.python/py-autoloaded-pretty-printers-in-newobjfile-event.exp
+++ b/gdb/testsuite/gdb.python/py-autoloaded-pretty-printers-in-newobjfile-event.exp
@@ -61,8 +61,6 @@ gdb_test_no_output "source ${remote_python_event_handler_file}" "load python fil
 
 gdb_load ${binfile}
 
-gdb_test_no_output "set print pretty on"
-
 if { ![runto_main] } {
     return
 }

                 reply	other threads:[~2023-02-09 18:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230209185048.A01F83858C5F@sourceware.org \
    --to=cschimpe@sourceware.org \
    --cc=gdb-cvs@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).