From: "H. J. Lu" <hjl@lucon.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Markus Deuling <deuling@de.ibm.com>,
Joel Brobecker <brobecker@adacore.com>,
gdb@sourceware.org
Subject: Re: GDB 6.5.90 available for testing (GDB 6.6 pre-release)
Date: Tue, 05 Dec 2006 20:35:00 -0000 [thread overview]
Message-ID: <20061205203516.GA30315@lucon.org> (raw)
In-Reply-To: <m3lklm2m2s.fsf@codesourcery.com>
On Tue, Dec 05, 2006 at 11:12:59AM -0800, Jim Blandy wrote:
>
> Here's the patch I've been using for this. It'd be better to rework
> the way those functions use those obstacks, but...
>
> 2006-12-05 Jim Blandy <jimb@codesourcery.com>
>
> * cp-valprint.c (cp_print_value_fields, cp_print_value):
> Initialize tmp_obstack, to avoid warnings.
> * p-valprint.c (pascal_object_print_value_fields)
> (pascal_object_print_value): Same.
>
What is wrong with
http://sources.redhat.com/ml/gdb-patches/2006-12/msg00008.html
H.J.
next prev parent reply other threads:[~2006-12-05 20:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 19:23 Joel Brobecker
2006-12-04 9:35 ` Markus Deuling
2006-12-04 18:22 ` Joel Brobecker
2006-12-04 18:23 ` Daniel Jacobowitz
2006-12-05 7:02 ` Markus Deuling
2006-12-05 19:02 ` Joel Brobecker
2006-12-05 19:12 ` Jim Blandy
2006-12-05 20:09 ` Daniel Jacobowitz
2006-12-05 21:56 ` Jim Blandy
2006-12-05 20:35 ` H. J. Lu [this message]
2006-12-05 21:37 ` Mark Kettenis
2006-12-05 21:41 ` Daniel Jacobowitz
2006-12-06 16:06 ` Markus Deuling
2006-12-13 11:47 ` Markus Deuling
2006-12-04 12:09 ` Marc Kleine-Budde
2006-12-04 18:29 ` Joel Brobecker
2006-12-04 19:38 ` Ulrich Weigand
2006-12-05 7:40 ` Markus Deuling
2006-12-05 18:56 ` Joel Brobecker
2006-12-06 12:02 ` Markus Deuling
2006-12-06 17:48 ` Joel Brobecker
2006-12-07 10:00 ` Markus Deuling
2006-12-04 20:37 Kaz Kylheku
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=20061205203516.GA30315@lucon.org \
--to=hjl@lucon.org \
--cc=brobecker@adacore.com \
--cc=deuling@de.ibm.com \
--cc=gdb@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