Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Svante Signell <svante.signell@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
	Pedro Alves <palves@redhat.com>,
	 gdb-patches@sourceware.org
Subject: Re: Small patch to enable build of gdb-7.6 for GNU/Hurd
Date: Mon, 27 May 2013 12:21:00 -0000	[thread overview]
Message-ID: <1369657278.8127.90.camel@s1499.it.kth.se> (raw)
In-Reply-To: <20130527121028.GB5751@adacore.com>

On Mon, 2013-05-27 at 16:10 +0400, Joel Brobecker wrote:
> > 2013-05-27  Svante Signell  <srs@hurd-2013.my.own.domain>
> > 
> > 	* nto-tdep.c (nto_init_solib_absolute_prefix): Solve build
> > 	problems for systems not defining PATH_MAX by using xstrprintf and
> > 	a cleanup.
> 
> Is the domain name above really valid?

No, it's a local one. I forgot to change that one.

> > Attached is an updated patch for the build problems on systems where
> > PATH_MAX is not defined.
> 
> In this case, I think you need to use what we call a "cleanup",
> because execute_command might trigger an "error" (GDB's poor man's
> exception mechanism), thus prevening the last xfree from releasing
> buf.

I thought of that problem and looking into the code for execute_command
convinced me that that command should always return. Obviously I was
wrong, you are the experts.

> A formatting nit: The GNU Coding Standard, which we follow in GDB,
> requires a space before opening parens.

I just realized that after submitting the mail.

> While looking at this code, I don't think you'll need 2 xstrprintf
> either. Can you try the attached patch?

Yes, of course this code is much neater. I will report build status
soon.



  reply	other threads:[~2013-05-27 12:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 16:36 Svante Signell
2013-05-23 17:08 ` Tom Tromey
2013-05-23 17:21   ` Svante Signell
2013-05-23 17:27     ` Tom Tromey
2013-05-23 17:54       ` Svante Signell
2013-05-24  3:01         ` Sergio Durigan Junior
2013-05-24  2:59 ` Sergio Durigan Junior
2013-05-24  4:27   ` Joel Brobecker
2013-05-24  8:53     ` Pedro Alves
2013-05-24  9:07       ` Svante Signell
2013-05-24  9:13         ` Sergio Durigan Junior
2013-05-27 11:41           ` Svante Signell
2013-05-27 12:10             ` Joel Brobecker
2013-05-27 12:21               ` Svante Signell [this message]
2013-05-27 13:48                 ` Svante Signell
2013-05-27 13:57                   ` Svante Signell
2013-05-27 14:31                     ` Joel Brobecker
2013-05-27 15:59                       ` Svante Signell
2013-05-29  9:26                         ` Joel Brobecker
2013-05-29 12:18                           ` Svante Signell
2013-05-27 16:03                       ` New patch: " Svante Signell
2013-05-29  9:42                         ` Joel Brobecker
2013-05-29 12:49                           ` Svante Signell
2013-05-27 14:55                   ` Thomas Schwinge

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=1369657278.8127.90.camel@s1499.it.kth.se \
    --to=svante.signell@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=sergiodj@redhat.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