From: msnyder@sonic.net
To: "Jim Blandy" <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] solib_open, memory leak
Date: Thu, 09 Aug 2007 18:37:00 -0000 [thread overview]
Message-ID: <9351.12.7.175.2.1186684646.squirrel@webmail.sonic.net> (raw)
In-Reply-To: <m3hcn9isrk.fsf@codesourcery.com>
>
> msnyder@sonic.net writes:
>> [Jim:]
>>> The code clearly deserves a comment like:
>>>
>>> /* We try to find the library in various ways. After each
>>> attempt, either found_file >= 0 and temp_pathname is a malloc'd
>>> string, or found_file < 0 and temp_pathname does not point to
>>> storage that needs to be freed. */
>>>
>>> In that light, it seems clearer to me to just put:
>>>
>>> if (found_file < 0)
>>> temp_pathname = NULL;
>>> else
>>> temp_pathname = xstrdup (temp_pathname);
>>>
>>> immediately after the open, to make it obvious that the rule is
>>> followed there.
>>>
>> [...]
>>> Don't you want those new lines to replace the two that followed them,
>>> not just precede them?
>>
>> Yes, thanks. How about this?
>
> Poifect.
Committed.
prev parent reply other threads:[~2007-08-09 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 3:17 msnyder
2007-08-06 22:28 ` Jim Blandy
2007-08-06 22:39 ` Kevin Buettner
2007-08-08 18:29 ` msnyder
2007-08-08 21:46 ` Jim Blandy
2007-08-08 21:58 ` msnyder
2007-08-08 22:08 ` Jim Blandy
2007-08-09 18:37 ` msnyder [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=9351.12.7.175.2.1186684646.squirrel@webmail.sonic.net \
--to=msnyder@sonic.net \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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