From: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
To: Francois Rigault <francois.rigault@amadeus.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Patch] Improve path lookup of absolute source file
Date: Fri, 26 Sep 2008 04:15:00 -0000 [thread overview]
Message-ID: <48DC61B9.2070603@br.ibm.com> (raw)
In-Reply-To: <OF93DA0F60.81E48D43-ONC12574C1.00378C52-C12574C1.00463B4A@amadeus.com>
Hi,
Francois Rigault schrieb:
> On a slow IO filesystem, like a network file system, this can slow down
> the performances. gdb takes here 15s to complete the setting of the
> first breakpoint on an absolute source file path.
>
> In order to let gdb find the files without generating IOs, a simple
> trick is to check that symbol source file and target source file have
> the same basename, as source file used at compilation time and the one
> used for debugging are unlikely to have different basenames. See the
> patch below against gdb-6.8.
This patch is a good idea, thanks. Some comments:
We need it against current CVS HEAD of GDB. Also, could you run the
testsuite before and after applying your patch, to be sure it introduces
no regression? It doesn't seem to me it will, but this is good practice
anyway.
Also, some nits regarding formatting, since GDB uses the GNU Coding
Standard:
> *** gdb/symtab.c Thu Sep 11 11:10:13 2008
> --- gdb/symtab.c Thu Sep 11 11:31:46 2008
> *************** lookup_partial_symtab (const char *name)
> *** 259,264 ****
> --- 259,270 ----
> return (pst);
> }
>
> + /* Skip this symbol if basenames differ. */
s/symbol/symbol table/
Also, you need two spaces after the full stop.
> + if (FILENAME_CMP (lbasename(name), lbasename(pst->filename)) != 0)
There should be a space between the function name and the parenthesis.
> + {
> + continue;
> + }
You don't need the curly braces here, since there's only one statement
inside the if.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2008-09-26 4:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 12:48 Francois Rigault
2008-09-26 4:15 ` Thiago Jung Bauermann [this message]
2008-09-26 13:02 ` Daniel Jacobowitz
2009-03-11 10:32 Francois Rigault
2009-03-15 19:44 ` Joel Brobecker
2009-03-17 15:57 ` Francois Rigault
2009-04-24 14:52 ` Tom Tromey
2009-04-24 15:12 ` Eli Zaretskii
2009-07-15 17:16 Francois Rigault
2009-07-30 0:07 ` 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=48DC61B9.2070603@br.ibm.com \
--to=thiago.bauermann@gmail.com \
--cc=francois.rigault@amadeus.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