From: Tom Tromey <tromey@redhat.com>
To: "André Pönitz" <andre.poenitz@nokia.com>
Cc: gdb@sourceware.org
Subject: Re: gdb breaking down at printing variable
Date: Fri, 27 Aug 2010 15:22:00 -0000 [thread overview]
Message-ID: <m38w3sulm9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201008271140.58307.andre.poenitz@nokia.com> (=?utf-8?Q?=22An?= =?utf-8?Q?dr=C3=A9_P=C3=B6nitz=22's?= message of "Fri, 27 Aug 2010 11:40:58 +0200")
>>>>> "André" == André Pönitz <andre.poenitz@nokia.com> writes:
André> I do acknowledge that there are two independent issues, one gcc
André> and one gdb related. I mostly meant to say that even if gdb were
André> not at fault Vikas Mishra's problem would still exist due to the
André> gcc bug (and I was assuming that the problems of uninitialized
André> data and gdb's own pretty- printers had been discussed often
André> enough in the past to not reiterate ;-)).
Yeah, sorry I misunderstood.
Tom
next prev parent reply other threads:[~2010-08-27 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 11:41 Vikas Mishra
2010-08-26 12:25 ` André Pönitz
2010-08-26 20:55 ` Tom Tromey
2010-08-27 9:41 ` André Pönitz
2010-08-27 15:22 ` Tom Tromey [this message]
[not found] <AANLkTimFU22phqb1uScS7PZ5WGJ65+1uD6RtkWMt352h@mail.gmail.com>
2010-08-26 15:21 ` Vikas Mishra
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=m38w3sulm9.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=andre.poenitz@nokia.com \
--cc=gdb@sourceware.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