Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: msnyder@sonic.net
Cc: gdb-patches@sourceware.org
Subject: Re: [OB] Add cleanup, source.c
Date: Thu, 28 Jun 2007 22:49:00 -0000	[thread overview]
Message-ID: <20070628224815.GC12578@caradoc.them.org> (raw)
In-Reply-To: <9270.12.7.175.2.1183069663.squirrel@webmail.sonic.net>

On Thu, Jun 28, 2007 at 03:27:43PM -0700, msnyder@sonic.net wrote:
> A missed opportunity for cleanup, flagged by Coverity.
> 
> I'm cut'and'pasting the patch to avoid my browser turning it into a
> binary stream.  This may eliminate tabs, but I don't expect anybody
> to actually apply this with 'patch'...
> 
> 2007-06-28  Michael Snyder  <msnyder@access-company.com>
> 
>         * source.c (unset_substitute_path_command): Plug leak (Coverity).

I think you need to do these a little slower...

>     /* This function takes either 0 or 1 argument.  */
> 
> +   make_cleanup_freeargv (argv);
>     if (argv != NULL && argv[0] != NULL && argv[1] != NULL)
>       error (_("Incorrect usage, too many arguments in command"));

There's no call to do_cleanups in this function, so it's quite hard to
see if this cleanup will be run or discarded if error is not called.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-28 22:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 22:35 msnyder
2007-06-28 22:49 ` Daniel Jacobowitz [this message]
2007-06-28 23:12   ` msnyder
     [not found]   ` <655C3D4066B7954481633935A40BB36F041427@ussunex02.svl.access-company.com>
2007-06-29  0:24     ` Daniel Jacobowitz
2007-06-29  2:05       ` msnyder
2007-06-29 11:37         ` Daniel Jacobowitz
2007-06-29 17:02           ` Joel Brobecker
2007-06-29 20:34             ` Michael Snyder
2007-06-30 10:19           ` Michael Snyder
2007-06-30 14:17             ` Eli Zaretskii
2007-06-30 16:39               ` Michael Snyder
2007-06-30 16:40                 ` Daniel Jacobowitz
2007-06-30 18:25                 ` Eli Zaretskii
2007-07-03 18:13                   ` Jim Blandy
2007-07-04 17:35                     ` Joel Brobecker

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=20070628224815.GC12578@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@sonic.net \
    /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