From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: [commit/Tru64] bring back the Tru64 port to life...
Date: Fri, 06 Mar 2009 01:00:00 -0000 [thread overview]
Message-ID: <200903060100.28738.pedro@codesourcery.com> (raw)
In-Reply-To: <20090306005753.GG3744@adacore.com>
On Friday 06 March 2009 00:57:53, Joel Brobecker wrote:
> In both cases, if nsecs is zero, we end up allocating less memory
> than sizeof (struct lm_info). Intuitively, it seems OK, since we
> shouldn't really access the secs array if nsecs is null.
Ah, you're right.
>
> One easy way out is to change the allocation to allocate one extra
> entry in the secs array. It's slightly wasteful, but it's just a
> few bytes times the number of shared libraries.
>
> What do you think?
>
Nah, it's fine as is. Sorry about the noise. :-)
--
Pedro Alves
prev parent reply other threads:[~2009-03-06 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 23:55 Joel Brobecker
2009-03-06 0:28 ` Pedro Alves
2009-03-06 0:58 ` Joel Brobecker
2009-03-06 1:00 ` Pedro Alves [this message]
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=200903060100.28738.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.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