From: asmwarrior <asmwarrior@gmail.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFA] DWARF frame unwinder executes one too many rows
Date: Fri, 27 Jul 2012 11:15:00 -0000 [thread overview]
Message-ID: <50127853.5010701@gmail.com> (raw)
In-Reply-To: <50127671.70400@gmail.com>
On 2012-7-27 19:07, asmwarrior wrote:
> After applying your patch, those messages were gone.
Oh, sorry. I still see such messages after applying the patch, like:
[debug]> bt 30
[debug]#0 NativeParserBase::BreakUpComponents (this=0x22fc44, actual=..., components=...) at nativeparser_base.cpp:716
[debug]#1 0x0041a38f in NativeParserTest::TestExpression (this=0x22fc44, expression=..., tree=0x16309b0, searchScope=..., result=...) at nativeparsertest.cpp:83
[debug]#2 0x0040ed74 in Frame::Start (this=0x16280d8) at frame.cpp:336
[debug]#3 0x004360ea in ParserTestApp::OnInit (this=0x161a028) at app.cpp:117
[debug]#4 0x0045da0c in wxAppConsole::CallOnInit (this=0x161a028) at E:/code/cb/wx/wxWidgets-2.8.12/include/wx/app.h:76
[debug]#5 0x0088a23d in wxEntryReal(int&, wchar_t**) () from E:\code\cb\wx\wxWidgets-2.8.12\lib\gcc_dll\wxmsw28u_gcc_custom.dll
[debug]#6 0x01616d28 in ?? ()
[debug]#7 0x00000001 in ?? ()
[debug]#8 0x01619f48 in ?? ()
[debug]Backtrace stopped: previous frame inner to this frame (corrupt stack?)
next prev parent reply other threads:[~2012-07-27 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 22:51 Joel Brobecker
2012-07-27 11:07 ` asmwarrior
2012-07-27 11:15 ` asmwarrior [this message]
2012-07-27 12:14 ` Joel Brobecker
2012-07-30 17:43 ` Tom Tromey
2012-08-16 15:47 ` Joel Brobecker
2012-08-04 12:30 ` Jan Kratochvil
2012-08-06 14:05 ` Tom Tromey
2012-08-06 15:06 ` Jan Kratochvil
2012-08-06 15:10 ` Tom Tromey
2012-08-06 15:19 ` Jan Kratochvil
2012-08-17 18:14 ` [patch] testsuite: Test the unwinder off-by-one [Re: [RFA] DWARF frame unwinder executes one too many rows] Jan Kratochvil
2012-08-27 16:35 ` [commit] " Jan Kratochvil
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=50127853.5010701@gmail.com \
--to=asmwarrior@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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