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

On 10/11/2013 03:10 PM, Jan Kratochvil wrote:
> On Fri, 11 Oct 2013 19:53:12 +0200, Luis Machado wrote:
>> On 10/11/2013 01:56 PM, Jan Kratochvil wrote:
>>> On Fri, 11 Oct 2013 18:46:15 +0200, Luis Machado wrote:
>>>> --- a/gdb/gcore.in
>>>> +++ b/gdb/gcore.in
>>>> @@ -49,9 +49,26 @@ rc=0
>>>>   # Loop through pids
>>>>   for pid in $*
>>>>   do
>>>> +# Attempt to fetch the absolute path to the gcore script that was
>>>> +# called.
>>>> +binary_path=`dirname "$0"`
>>>> +
>>>> +	if test "x$binary_path" = x. ; then
>>>> +	  # 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).  We use
>>>> +	  # the "which" command to locate the real path of the gcore
>>>> +	  # script, disambiguating this situation.
>>>> +	  binary_path_from_env=`which "$0"`
>>>> +	  binary_path=`dirname $binary_path_from_env`
>>>
>>> In generally OK, just still ... is there some reason for this 'which' search?
>>> Moreover if one really runs ./gcore then it should IMO take ./gdb (and not some
>>> other gdb), if we should really pick GDB from the directory of gcore.
>>
>> Yes. The reason is to pick the gdb binary from the directory that
>> contains the gcore script the user invoked.
>>
>> If the user issued "sh gcore" and /usr/bin/gcore was picked (based
>> on $PATH), then we should use /usr/bin/gdb.
>>
>> Now, if the user issued "./gcore", ./gdb will be picked up, and so on.
>>
>> Does it make sense?
>
> Great we agree.  But your code does pick /usr/bin/gdb for ./gcore, doesn't it?
> Which is why I proposed the change I proposed.

Hmmm... unless there is some discrepancy between shell interpreters, 
mine (bash) does the following:

Invocation: ./gcore
dirname ./gcore -> .

So we go inside the if block and locate the real binary that is being 
called based on $PATH.

which ./gcore -> ./gcore

So we pick the dirname of ./gcore (which is ".") and add a slash to it, 
resulting in ./gdb.

Do you see something different or a corner case?

Luis


  reply	other threads:[~2013-10-11 18:22 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 [this message]
2013-10-11 19:58               ` Jan Kratochvil
2013-10-14 12:24                 ` Luis Machado
2013-10-15 15:10                   ` Jan Kratochvil
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=525841CD.8070506@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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