From: Daniel Jacobowitz <drow@false.org>
To: msnyder@sonic.net
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] null pointer guard, target-descriptions.c
Date: Sun, 01 Jul 2007 16:00:00 -0000 [thread overview]
Message-ID: <20070701160007.GG10872@caradoc.them.org> (raw)
In-Reply-To: <17674.12.7.175.2.1183064463.squirrel@webmail.sonic.net>
On Thu, Jun 28, 2007 at 02:01:03PM -0700, Michael Snyder wrote:
> Possible null pointer ref, flagged by Coverity
>
> 2007-06-28 Michael Snyder <msnyder@access-company.com>
>
> * target-descriptions.c (tdesc-_named_type): Guard against null
> type-id argument which may be passed by tdesc_create_reg (Coverity).
Whoops, yeah - this one's my fault. There's another place in the same
file which will crash if reg->type == NULL. How about we never set it
to NULL instead? Like below.
--
Daniel Jacobowitz
CodeSourcery
2007-07-01 Daniel Jacobowitz <dan@codesourcery.com>
* target-descriptions.c (tdesc_create_reg): Do not set reg->type
to NULL.
Index: target-descriptions.c
===================================================================
RCS file: /cvs/src/src/gdb/target-descriptions.c,v
retrieving revision 1.9
diff -u -p -r1.9 target-descriptions.c
--- target-descriptions.c 13 Jun 2007 18:26:59 -0000 1.9
+++ target-descriptions.c 1 Jul 2007 15:59:10 -0000
@@ -792,7 +792,7 @@ tdesc_create_reg (struct tdesc_feature *
reg->save_restore = save_restore;
reg->group = group ? xstrdup (group) : NULL;
reg->bitsize = bitsize;
- reg->type = type ? xstrdup (type) : NULL;
+ reg->type = type ? xstrdup (type) : xstrdup ("<unknown>");
/* If the register's type is target-defined, look it up now. We may not
have easy access to the containing feature when we want it later. */
next prev parent reply other threads:[~2007-07-01 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 21:12 msnyder
2007-07-01 16:00 ` Daniel Jacobowitz [this message]
2007-07-03 0:40 ` msnyder
2007-07-03 1:23 ` 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=20070701160007.GG10872@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