public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55358] Valgrind errors
Date: Wed, 21 Nov 2012 16:53:00 -0000 [thread overview]
Message-ID: <bug-55358-4-FBB985e91j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55358-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55358
--- Comment #2 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-11-21 16:52:59 UTC ---
==13066== Conditional jump or move depends on uninitialised value(s)
==13066== at 0x56333A: pp_c_specifier_qualifier_list(c_pretty_print_info*,
tree_node*) (c-pretty-print.c:449)
==13066== by 0x563668: pp_c_type_id(c_pretty_print_info*, tree_node*)
(c-pretty-print.c:621)
==13066== by 0x4FF780: c_tree_printer(pretty_print_info*, text_info*, char
const*, int, bool, bool, bool) (c-objc-common.c:149)
==13066== by 0xDB6682: pp_base_format(pretty_print_info*, text_info*)
(pretty-print.c:509)
==13066== by 0xDB4478: diagnostic_report_diagnostic(diagnostic_context*,
diagnostic_info*) (diagnostic.c:756)
==13066== by 0xDB5043: error_at(unsigned int, char const*, ...)
(diagnostic.c:1036)
==13066== by 0x4EA6BA: build_component_ref(unsigned int, tree_node*,
tree_node*) (c-typeck.c:2156)
==13066== by 0x50968B: c_parser_postfix_expression_after_primary(c_parser*,
unsigned int, c_expr) (c-parser.c:6946)
==13066== by 0x501568: c_parser_postfix_expression(c_parser*)
(c-parser.c:6779)
==13066== by 0x502F22: c_parser_unary_expression(c_parser*)
(c-parser.c:5978)
==13066== by 0x50733E: c_parser_cast_expression(c_parser*, c_expr*)
(c-parser.c:5830)
==13066== by 0x502E06: c_parser_unary_expression(c_parser*)
(c-parser.c:5892)
==13066==
==13066== Conditional jump or move depends on uninitialised value(s)
==13066== at 0x5633C8: pp_c_specifier_qualifier_list(c_pretty_print_info*,
tree_node*) (c-pretty-print.c:497)
==13066== by 0x563668: pp_c_type_id(c_pretty_print_info*, tree_node*)
(c-pretty-print.c:621)
==13066== by 0x4FF780: c_tree_printer(pretty_print_info*, text_info*, char
const*, int, bool, bool, bool) (c-objc-common.c:149)
==13066== by 0xDB6682: pp_base_format(pretty_print_info*, text_info*)
(pretty-print.c:509)
==13066== by 0xDB4478: diagnostic_report_diagnostic(diagnostic_context*,
diagnostic_info*) (diagnostic.c:756)
==13066== by 0xDB5043: error_at(unsigned int, char const*, ...)
(diagnostic.c:1036)
==13066== by 0x4EA6BA: build_component_ref(unsigned int, tree_node*,
tree_node*) (c-typeck.c:2156)
==13066== by 0x50968B: c_parser_postfix_expression_after_primary(c_parser*,
unsigned int, c_expr) (c-parser.c:6946)
==13066== by 0x501568: c_parser_postfix_expression(c_parser*)
(c-parser.c:6779)
==13066== by 0x502F22: c_parser_unary_expression(c_parser*)
(c-parser.c:5978)
==13066== by 0x50733E: c_parser_cast_expression(c_parser*, c_expr*)
(c-parser.c:5830)
==13066== by 0x502E06: c_parser_unary_expression(c_parser*)
(c-parser.c:5892)
==13066==
next prev parent reply other threads:[~2012-11-21 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 18:57 [Bug other/55358] New: " hjl.tools at gmail dot com
2012-11-21 15:31 ` [Bug other/55358] " markus at trippelsdorf dot de
2012-11-21 16:53 ` markus at trippelsdorf dot de [this message]
2012-11-21 17:17 ` markus at trippelsdorf dot de
2012-11-21 17:20 ` jakub at gcc dot gnu.org
2012-11-23 13:10 ` markus at trippelsdorf dot de
2012-11-28 8:51 ` markus at trippelsdorf dot de
2012-11-28 13:21 ` markus at trippelsdorf dot de
2012-11-28 14:48 ` jakub at gcc dot gnu.org
2012-11-28 16:50 ` jakub at gcc dot gnu.org
2012-11-28 19:59 ` markus at trippelsdorf dot de
2013-10-14 9:24 ` rguenth at gcc dot gnu.org
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=bug-55358-4-FBB985e91j@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).