Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix calling gcore when gdb is not in $PATH.
Date: Tue, 15 Oct 2013 15:10:00 -0000	[thread overview]
Message-ID: <20131015151015.GA7805@host2.jankratochvil.net> (raw)
In-Reply-To: <525BE269.9070907@codesourcery.com>

On Mon, 14 Oct 2013 14:24:09 +0200, Luis Machado wrote:
> --- a/gdb/gcore.in
> +++ b/gdb/gcore.in
> @@ -43,6 +43,40 @@ then
>      shift; shift
>  fi
>  
> +# Attempt to fetch the absolute path to the gcore script that was
> +# called.
> +binary_path=`dirname "$0"`
> +
> +if test "x$binary_path" = x. ; then

I find this test needlessly complicating the code a bit as it is true for both
"sh gcore" and for "./gcore" while the conditionalized block of code is needed
only in the "sh gcore" case.  I was proposing a different test before.  But it
works even for the "./gcore" execution case so technically it is correct.


> +  # We got "." back as a path.  This means the user executed
> +  # the gcore script locally (i.e. ./gcore) or called the
> +  # script via a shell interpreter (i.e. sh gcore).
> +  binary_basename=`basename "$0"`
> +
> +  # If the gcore script was called like "sh gcore" and the script
> +  # lives in the current directory, "which" will not give us "gcore".
> +  # So first we check if the script is in the current directory
> +  # before using the output "which".
> +  if test -f "$binary_basename" ; then
> +    # We have a local gcore script in ".".  This covers the case of
> +    # doing "./gcore" or "sh gcore".
> +    binary_path="."
> +  else
> +    # The gcore script was not found in ".", which means the script
> +    # was called from somewhere else in $PATH.  Extract the correct

       # was called from somewhere else in $PATH by "sh gcore". [...]


> +    # path now.
> +    binary_path_from_env=`which "$0"`
> +    binary_path=`dirname "$binary_path_from_env"`
> +  fi
> +fi
> +
> +# 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"
> +  exit 1
> +fi
> +
>  # Initialise return code.
>  rc=0
>  
> @@ -51,7 +85,7 @@ for pid in $*
>  do
>  	# `</dev/null' to avoid touching interactive terminal if it is
>  	# available but not accessible as GDB would get stopped on SIGTTIN.
> -	@GDB_TRANSFORM_NAME@ </dev/null --nx --batch \
> +	$binary_path/@GDB_TRANSFORM_NAME@ </dev/null --nx --batch \
>  	    -ex "set pagination off" -ex "set height 0" -ex "set width 0" \
>  	    -ex "attach $pid" -ex "gcore $name.$pid" -ex detach -ex quit
>  

OK for check-in.


Thanks,
Jan


  reply	other threads:[~2013-10-15 15:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 14:10 Luis Machado
2013-10-11 14:31 ` Jan Kratochvil
2013-10-11 14:46   ` Luis Machado
2013-10-11 16:46     ` Luis Machado
2013-10-11 16:56       ` Jan Kratochvil
2013-10-11 17:53         ` Luis Machado
2013-10-11 18:10           ` Jan Kratochvil
2013-10-11 18:22             ` Luis Machado
2013-10-11 19:58               ` Jan Kratochvil
2013-10-14 12:24                 ` Luis Machado
2013-10-15 15:10                   ` Jan Kratochvil [this message]
2013-10-16 15:13                     ` Luis Machado

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=20131015151015.GA7805@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    /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