public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Akbarkhon Variskhanov <akbarkhon.variskhanov@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] gdb/gcore.in - Redirect error messages to stderr
Date: Sun, 6 Mar 2022 14:59:44 +0500	[thread overview]
Message-ID: <CANeoM1GOyWdcH7r+MaX_s9JROq_cL-MviZCHTwZJ82YW+0=igA@mail.gmail.com> (raw)

--- gdb_gcore.in 2022-03-06 14:47:51.724033755 +0500
+++ gcore.in.patch 2022-03-06 14:56:11.243630494 +0500
@@ -41,7 +41,8 @@
             prefix=$OPTARG
             ;;
         *)
-            echo "usage:  @GCORE_TRANSFORM_NAME@ [-a] [-o prefix] pid1
[pid2...pidN]"
+            echo >&2 "usage:  @GCORE_TRANSFORM_NAME@ [-a] [-o prefix] pid1
\
+             [pid2...pidN]"
             exit 2
             ;;
     esac
@@ -51,7 +52,7 @@

 if [ "$#" -eq "0" ]
 then
-    echo "usage:  @GCORE_TRANSFORM_NAME@ [-a] [-o prefix] pid1
[pid2...pidN]"
+    echo >&2 "usage:  @GCORE_TRANSFORM_NAME@ [-a] [-o prefix] pid1
[pid2...pidN]"
     exit 2
 fi

@@ -85,7 +86,7 @@
 # Check if the GDB binary is in the expected path.  If not, just
 # quit with a message.
 if [ ! -f "$binary_path/@GDB_TRANSFORM_NAME@" ]; then
-  echo "gcore: GDB binary (${binary_path}/@GDB_TRANSFORM_NAME@) not found"
+  echo >&2 "gcore: GDB binary (${binary_path}/@GDB_TRANSFORM_NAME@) not
found"
   exit 1
 fi

@@ -106,7 +107,7 @@
  if [ -r "$prefix.$pid" ] ; then
     rc=0
  else
-    echo "@GCORE_TRANSFORM_NAME@: failed to create $prefix.$pid"
+    echo >&2 "@GCORE_TRANSFORM_NAME@: failed to create $prefix.$pid"
     rc=1
     break
  fi

             reply	other threads:[~2022-03-06  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06  9:59 Akbarkhon Variskhanov [this message]
2022-03-09 17:21 ` Tom Tromey

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='CANeoM1GOyWdcH7r+MaX_s9JROq_cL-MviZCHTwZJ82YW+0=igA@mail.gmail.com' \
    --to=akbarkhon.variskhanov@gmail.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).