From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: muller@ics.u-strasbg.fr (Pierre Muller)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Avoid internal error in paddress
Date: Wed, 08 Jul 2009 12:10:00 -0000 [thread overview]
Message-ID: <200907081209.n68C9b6t029376@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <000501c9ffa2$7ed3e2d0$7c7ba870$@u-strasbg.fr> from "Pierre Muller" at Jul 08, 2009 10:02:53 AM
Hi Pierre,
> I reported an internal error
> in gdbtui at startup
> concerning the recently modified paddress function:
>
> http://sourceware.org/ml/gdb/2009-07/msg00052.html
>
> I suspect that this internal error could bite
> us elsewhere, this is why I propose the following patch:
I don't really like this, there is no other place in GDB
where a NULL gdbarch is silently accepted. I think we should
really make sure we know a proper gdbarch ...
I've now checked in this patch:
http://sourceware.org/ml/gdb-patches/2009-07/msg00231.html
to fix the gdbtui crash.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2009-07-08 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 8:03 Pierre Muller
2009-07-08 12:10 ` Ulrich Weigand [this message]
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=200907081209.n68C9b6t029376@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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