Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] [1/2] auto-loading scripts from .debug_gdb_scripts section
Date: Tue, 20 Apr 2010 21:45:00 -0000	[thread overview]
Message-ID: <m2ve394668d1004201445t2395c0c0g603fe6eadb608d7e@mail.gmail.com> (raw)
In-Reply-To: <83bpdjccpc.fsf@gnu.org>

On Fri, Apr 16, 2010 at 2:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 16 Apr 2010 11:06:44 -0700
>> From: Doug Evans <dje@google.com>
>> Cc: gdb-patches@sourceware.org
>>
>> > The existing Python Auto-loading section is not too long, so how about
>> > simply adding the description of this new feature to that section?  I
>> > think ripping it out of "Python API" is not a good idea.
>>
>> To me the Auto-loading section is not really part of the API.
>
> Well, yes, but this feature is currently specific to Python, so why
> move it out of the Python chapter?

I moved it from the "Python API" node to the "Python" node.
It's up one level but it's still in the Python chapter.

>> >> +  if (!input && debug_file_directory)
>> >> +    {
>> >> +      /* Also try the same file in the separate debug info directory.  */
>> >> +      debugfile = xmalloc (strlen (filename)
>> >> +                        + strlen (debug_file_directory) + 1);
>> >> +      strcpy (debugfile, debug_file_directory);
>> >> +      /* FILENAME is absolute, so we don't need a "/" here.  */
>> >> +      strcat (debugfile, filename);
>> >
>> > What will that last strcat do if FILENAME has a drive letter?
>> >
>> >> +      strcpy (debugfile, gdb_datadir);
>> >> +      strcat (debugfile, "/auto-load");
>> >> +      /* FILENAME is absolute, so we don't need a "/" here.  */
>> >> +      strcat (debugfile, filename);
>> >
>> > Ditto.
>>
>> This is cut-n-pasted from the existing code to auto-load -gdb.py
>> scripts.  I don't know if filename can have a drive letter here.
>
> Yes, it can.  It depends how the files were called out in the
> compilation command line.
>
> I think we should strip the drive letter and the colon before
> concatenating the rest with the leading directory.

Sure.
I'll do that.


  reply	other threads:[~2010-04-20 21:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16  7:06 Doug Evans
2010-04-16  9:38 ` Eli Zaretskii
2010-04-16 18:06   ` Doug Evans
2010-04-16 21:25     ` Eli Zaretskii
2010-04-20 21:45       ` Doug Evans [this message]
2010-04-21 19:23         ` Doug Evans
2010-04-21 20:39           ` Eli Zaretskii
2010-04-21 21:54             ` Doug Evans
2010-04-22  3:13               ` Eli Zaretskii
2010-04-23 18:10                 ` Doug Evans
2010-04-20 19:13 ` Tom Tromey
2010-04-20 21:38   ` 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=m2ve394668d1004201445t2395c0c0g603fe6eadb608d7e@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --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