From: Denis PILAT <denis.pilat@st.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sourceware.org
Subject: Re: Query user with gdb MI intepreter
Date: Thu, 23 Oct 2008 12:57:00 -0000 [thread overview]
Message-ID: <49007456.6090208@st.com> (raw)
In-Reply-To: <18688.23242.783095.562854@kahikatea.snap.net.nz>
Nick Roberts wrote:
> > If actual behavior is not correct, then I will propose a simple patch
> > that is already in place in my version of gdb sources.
>
> I don't think anyone has considered how MI should behave after an internal
> error which really means there is a bug in GDB anyway.
There is, but I don't have any patch to submit about it, sorry.
dwarf2_restore_rule() is called from execute_cfa_program() with
fs->initial.reg set to 0 which leads to a gdb_assert().
That, for sure, comes from a problem we have in our in-house compiler
that do not generate right debug information.
next prev parent reply other threads:[~2008-10-23 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 6:45 Nick Roberts
2008-10-23 10:21 ` Denis PILAT
2008-10-23 11:08 ` Nick Roberts
2008-10-23 12:57 ` Denis PILAT [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-21 12:18 Denis PILAT
2008-10-23 10:30 ` Vladimir Prus
2008-10-23 11:08 ` Denis PILAT
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=49007456.6090208@st.com \
--to=denis.pilat@st.com \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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