From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Re: [patch 1/2] physname reg.: linespec minsym fallback
Date: Mon, 04 Jul 2011 14:08:00 -0000 [thread overview]
Message-ID: <201107041313.p64DDvoS029301@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20110701202105.GA22980@host1.jankratochvil.net> from "Jan Kratochvil" at Jul 01, 2011 10:21:05 PM
Jan Kratochvil wrote:
> 2011-07-01 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> + Fall back linespec to minimal symbols.
> + * linespec.c (decode_line_1): New variable ex, saved_argptr. Protect
> + decode_compound by TRY_CATCH, fall back on minsyms if it failed.
> + (find_method, symbol_found): Change error to cplusplus_error.
On some machines (RHEL 5.6 with GCC 4.1.2 system compiler) I'm now seeing:
cc1: warnings being treated as errors
/home/kwerner/dailybuild/spu-tc-2011-07-04/gdb-head/src/gdb/linespec.c: In function 'decode_line_1':
/home/kwerner/dailybuild/spu-tc-2011-07-04/gdb-head/src/gdb/linespec.c:928: warning: 'values.nelts' may be used uninitialized in this function
/home/kwerner/dailybuild/spu-tc-2011-07-04/gdb-head/src/gdb/linespec.c:928: warning: 'values.sals' may be used uninitialized in this function
Should there be an initializer somewhere?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2011-07-04 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 20:27 Jan Kratochvil
2011-06-07 20:56 ` Tom Tromey
2011-06-08 15:04 ` Jan Kratochvil
2011-07-01 20:21 ` [commit] " Jan Kratochvil
2011-07-04 14:08 ` Ulrich Weigand [this message]
2011-07-04 16:22 ` [commit#2+7.3] " Jan Kratochvil
2011-07-04 16:35 ` Ulrich Weigand
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=201107041313.p64DDvoS029301@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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