From: Roland Schwingel <roland.schwingel@onevision.de>
To: Tristan Gingold <gingold@adacore.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb-patches@sourceware.org ml"
<gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>
Subject: Re: [RFA] Windows x64 SEH unwinder (v2)
Date: Mon, 19 Aug 2013 15:14:00 -0000 [thread overview]
Message-ID: <52123653.7000006@onevision.de> (raw)
Hi Tristan...
> > Stack frames are way better... Congratulations... But:
> > When inspecting frames I see problems showing the content of
> variables. I cannot look into any of the applications vars. gdb
> just shows eg:
>
> > #1: 0x0000000000401577 in func4 (num=<error reading variable:
> can't compute CFA for this frame>) at gdb_crash.c:26
> >
> > also a "p num" show the same error.
> >
> > Did I do something wrong? Is there a hidden trick that needs to be
> applied to get this going that I couldn't find from reading the patch?
>
> Doesn't ring a bell here. Can you post gdb_crash.c ?
The example program is part of my initial post.
(http://sourceware.org/ml/gdb/2005-04/msg00113.html)
For compiling it I simply did a
/path/to/my/x86_64-w64-mingw32-gcc.exe -g gdb_crash.c -o gdb_crash.exe
But the concrete example does not matter. Whichever program I compile
variable viewing is totally broken for me (gcc 4.8.2 prelease 20130730
with mingw-w64 runtime from 20130730) all with above error messages.
Thanks for your help. I hope this can be resolved soon. I would love to
enrich my gdb with SEH2 unwinding!
Roland
next reply other threads:[~2013-08-19 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 15:14 Roland Schwingel [this message]
2013-08-19 15:32 ` Tristan Gingold
-- strict thread matches above, loose matches on Subject: below --
2013-08-22 11:22 Roland Schwingel
2013-08-19 16:01 Roland Schwingel
2013-08-21 13:45 ` Tristan Gingold
2013-08-22 10:22 ` Pedro Alves
2013-08-05 11:25 Roland Schwingel
2013-08-19 13:53 ` Tristan Gingold
2013-01-09 10:53 Add Windows x64 SEH unwinder (take 2) Joel Brobecker
2013-01-09 10:53 ` [RFA/commit+doco 2/2] Windows x64 SEH unwinder Joel Brobecker
2013-01-09 15:52 ` Pedro Alves
2013-01-09 16:28 ` Tristan Gingold
2013-01-09 17:10 ` Pedro Alves
2013-01-09 20:07 ` Tristan Gingold
2013-01-10 16:24 ` Pedro Alves
2013-07-08 10:55 ` [RFA] Windows x64 SEH unwinder (v2) Tristan Gingold
2013-07-26 15:22 ` Pedro Alves
2013-08-19 13:59 ` Tristan Gingold
2013-08-19 14:13 ` Pedro Alves
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=52123653.7000006@onevision.de \
--to=roland.schwingel@onevision.de \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).