Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: Re: [patch] Bring QNX Neutrino support forward.
Date: Wed, 31 Mar 2004 22:21:00 -0000	[thread overview]
Message-ID: <20040331222120.GB6811@nevyn.them.org> (raw)
In-Reply-To: <4060A9C0.1090906@qnx.com>

Some small comments.

On Tue, Mar 23, 2004 at 04:18:56PM -0500, Kris Warkentin wrote:
> ChangeLog entry:
> * nto-tdep.h: Include osabi.h.  Prototypes for generic Neutrino

Leading tabs in the ChangeLog entry, please :)  Post what you would
check in.

> +#define nto_fetch_link_map_offsets \
> +(current_nto_target.nto_fetch_link_map_offsets)

I believe this should be indented.  I'm not sure how far, I usually use
two spaces.

> -  return openp (buf, 1, solib, o_flags, 0, temp_pathname);
> +  /* Don't assume basename() isn't destructive.  */
> +  base = strrchr (solib, '/');
> +  if (!base)
> +    base = solib;
> +  else
> +    base++;			/* Skip over '/'.  */

There's an lbasename in libiberty, for this reason.  You should use
that instead.

> +  ret = openp (buf, 1, base, o_flags, 0, temp_pathname);
> +  if (ret < 0 && base != solib)
> +    {
> +      sprintf (arch_path, "/%s", solib);
> +      ret = open (arch_path, o_flags, 0);

Er... automatically falling back to the host library?  Why?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2004-03-31 22:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 21:18 Kris Warkentin
2004-03-23 23:21 ` Andrew Cagney
2004-03-24 13:38   ` Kris Warkentin
2004-03-24 14:35     ` Andrew Cagney
2004-03-24 16:32       ` Kris Warkentin
2004-03-25 17:22         ` Kris Warkentin
2004-03-26  3:43           ` Andrew Cagney
2004-03-31 22:21 ` Daniel Jacobowitz [this message]
2004-04-01 14:59   ` Kris Warkentin
2004-04-01 15:04     ` Daniel Jacobowitz

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=20040331222120.GB6811@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kewarken@qnx.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