Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb-patches@sourceware.org, Chris Sutcliffe <ir0nh34d@gmail.com>
Subject: Re: [windows] patch to set breakpoint in a dll
Date: Thu, 08 Mar 2012 22:39:00 -0000	[thread overview]
Message-ID: <CADPb22TVY2Zg5q3Y+vpfkbrSV=d_SPf3zV5Dc6FvcZOtgGftmQ@mail.gmail.com> (raw)
In-Reply-To: <4F5816EE.4050908@gmail.com>

On Wed, Mar 7, 2012 at 6:18 PM, asmwarrior <asmwarrior@gmail.com> wrote:
> On 2012-3-8 2:46, Doug Evans wrote:
>>
>> The patch has a few nits that need to be fixed, but I like the idea:
>
> Hi, Doug, Thanks for the reply.
>
>> have find_and_open_source consistently return the canonicalized path.
>> However, openp (called by find_and_open_source later on) uses
>> xfullpath, so for consistency I think that should be used here too
>> instead of gdb_realpath.
>> What do others think?
>
> By reading the function body of xfullpath, I see that it do more checks.
> And transfer from gdb_realpath to xfullpath will adding an extra xmalloc and
> xfree call.
>
> BTW: are there any simple way we can quickly check a path is cononicalized
> or not, because even gdb_realpath have internally call xmalloc and xfree.
> but once the *fullname is already cononicalized(after the first call of
> find_and_open_source()), I think we can avoid calling any xmalloc and xfree.
> Am I right?

No such quick check is available, but I think we can ignore the cost
of the xmalloc/xfree for this particular case until the data shows
it's a problem.


  reply	other threads:[~2012-03-08 22:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 15:10 asmwarrior
2012-03-07 18:46 ` Doug Evans
2012-03-08  2:18   ` asmwarrior
2012-03-08 22:39     ` Doug Evans [this message]
2012-03-10  4:39       ` asmwarrior
2012-03-14 18:26         ` Doug Evans
2012-03-16  1:52           ` asmwarrior
2012-03-16 22:23             ` Doug Evans
2012-03-17  1:13               ` asmwarrior
2012-04-11 15:25             ` asmwarrior
2012-04-11 18:43               ` Doug Evans

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='CADPb22TVY2Zg5q3Y+vpfkbrSV=d_SPf3zV5Dc6FvcZOtgGftmQ@mail.gmail.com' \
    --to=dje@google.com \
    --cc=asmwarrior@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ir0nh34d@gmail.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