Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Frederic RISS <frederic.riss@st.com>
Cc: Jim Blandy <jimb@red-bean.com>,
		GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Don't lose compilation directory in Dwarf2 line-tables
Date: Tue, 18 Apr 2006 13:04:00 -0000	[thread overview]
Message-ID: <20060418130432.GC10130@nevyn.them.org> (raw)
In-Reply-To: <1145363529.14807.848.camel@crx549.cro.st.com>

On Tue, Apr 18, 2006 at 02:32:09PM +0200, Frederic RISS wrote:
> All this file matching seems quite fragile, and the current approach
> will get it wrong sometimes. Shouldn't the loop in dwarf2_start_subfile
> be killed in favor of a search using both xfullpath(dirname'/'filename)
> at the start of buildsym.c::start_subfile?

The problem with using xfullpath is that it requires the file to exist
and already be found; as long as we are consistent, it's not too
fragile, because we're checking against our own output.

> @@ -6757,6 +6756,19 @@ dwarf2_start_subfile (char *filename, ch
>  	}
>        xfree (fullname);
>      }
> +
> +  /* Make the dirname as absolute as possible. */

Two spaces after periods please.

> +
> +  if (dirname == NULL)
> +    dirname = comp_dir;
> +  else
> +    if (!IS_ABSOLUTE_PATH (dirname) && comp_dir != NULL)
> +      {
> +	dirname = concat (comp_dir, SLASH_STRING, dirname, (char *)NULL);
> +	/* do_cleanups is called after line info procesing */
> +	make_cleanup (xfree, dirname);

Comment formatting again (and "processing").  But this is really nasty. 
Why not free it before we return?  We don't return dirname, and
start_subfile takes a copy.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-18 13:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 11:25 [RFC] Don't loose " Frederic RISS
2006-04-13 17:49 ` Jim Blandy
2006-04-14  7:32   ` [RFC] Don't lose " Frederic RISS
2006-04-14  7:41     ` Jim Blandy
2006-04-14  8:23       ` Frederic RISS
2006-04-14 14:04         ` Daniel Jacobowitz
2006-04-14 14:51           ` Frederic RISS
2006-04-18 12:32             ` Frederic RISS
2006-04-18 13:04               ` Daniel Jacobowitz [this message]
2006-04-18 14:00                 ` Frederic RISS
2006-04-20 16:27                   ` Daniel Jacobowitz
2006-04-21  7:14                     ` Frederic RISS
2006-04-21  1:10                   ` Jim Blandy
2006-04-21  8:35                     ` Frederic RISS
2006-04-21 16:46                       ` Jim Blandy
2006-04-21 17:00                         ` Frederic RISS
2006-04-24 12:49                         ` Andrew STUBBS
2006-04-14  8:44     ` Eli Zaretskii
2006-04-14 11:44       ` Frederic RISS
2006-04-14 13:08         ` Eli Zaretskii
2006-04-14 13:42           ` Frederic RISS
2006-04-14 14:21             ` Eli Zaretskii
2006-04-14 14:58               ` Daniel Jacobowitz
2006-04-14 15:03                 ` Eli Zaretskii
2006-04-14 18:39               ` Frédéric Riss
2006-04-13 19:58 ` [RFC] Don't loose " Jason Molenda

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=20060418130432.GC10130@nevyn.them.org \
    --to=drow@false.org \
    --cc=frederic.riss@st.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.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