From: asmwarrior <asmwarrior@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Re: RFA: add python exception subclasses
Date: Sat, 18 Dec 2010 02:26:00 -0000 [thread overview]
Message-ID: <4D0C1C9D.30204@gmail.com> (raw)
In-Reply-To: <m3ei9g9q6y.fsf@fleche.redhat.com>
On 2010-12-18 3:04, Tom Tromey wrote:
>>> It seems this patch was already in the cvs trunk, but using the latest gdb I
>>> build myself yesterday(MSYS+MinGW). gdb still crashes when showing
>>> uninitialized vector<string>.
> Could you post the session and a backtrace?
>
> Tom
since the previous reply was reject by the mail-list, I create a compact
one.
log here(some text removed)
--------------------------------------------------------------------
> p v
$1 = std::vector of length -259079, capacity -521893089 = {<error
reading variable: Cannot access memory at address 0x900014b6>, <error
reading variable: Cannot access memory at address 0x34ac>, <error
reading variable: Cannot access memory at address 0x300b9f4>, <error
reading variable: Cannot access memory at address 0x12ff7ff2>, <error
reading variable: Cannot access memory at address 0x900010b6>, <error
reading variable: Cannot access memory at address 0x35ac>, <error
reading variable: Cannot access memory at address 0x300b9f4>, <error
reading variable: Cannot access memory at address 0x12ff7ff2>, <error
reading variable:
.....
<error reading variable: Cannot access memory at address 0x12ff7ff2>,
"s\000\037\066\003\326\025\000\000\001\020%\000\000\025_\037\000\000\025\020%\000\000\025\326\025\000\000\025\213$\000\000\000\063\004\221\036\000\000E\001putwc\000\037%\002\320\037\000\000\001\065%\000\000\025\244\026\000\000\025j#\000\000\000E\001putwchar\000\037\221\002\320\037\000\000\001R%\000\000\025\244\026\000\000\000E\001swscanf\000\037r\002\221\025\000\000\001t%\000\000\025e\037\000\000\025e\037\000\000F\000E\001ungetwc\000\037'\002\320\037\000\000\001\225%\000\000\025\320\037\000\000\025j#\000\000\000E\001vfwprintf\000\037/\002\221\025\000\000\001\275%\000\000\025j#\000\000\025e\037\000\000\025\236\037\000\000\000E\001vfwscanf\000\037B\002\221\025\000\000\001\344%\000\000\025j#\000\000\025e\037\000\000\025\236\037\000\000\000E\001vswscanf\000\037C\002\221\025\000\000\001\v&\000\000\025e\037\000\000\025e\037\000\000\025\236\037\000\000\000E\001vwprintf\000\037\060\002\221\025\000\000\001-&\000\000\025e\037\000\000\025\236\037\000\000\000E\001vwscanf\000\037A
....
<error reading variable: Cannot access memory at address 0xdd08ec77>,
<error reading variable: Cannot access memory at address 0x448b2408>,
<error reading variable: Cannot access memory at address 0xc4830418>,
<error reading variable: Cannot access memory at address 0x24fc>, <error
reading variable: Cannot access memory at address 0x3d747fe4>, <error
reading variable: Cannot access memory at address 0xf0000031>, <error
reading variable: Cannot access memory at address 0x665f7473>, <error
reading variable: Cannot access memory at address 0x6624047f>, <error
reading variable: Cannot access memory at address 0x74027f31>, <error
reading variable: Cannot access memory at address 0xe083661e>, <error
reading variable: Cannot access memory at address 0x9b217514>, <error
reading variable: Cannot access memory at address 0x8366e0d3>, <error
reading variable: Cannot access memory at address 0x187420d4>, <error
reading variable: Cannot access memory at address 0x8ac>, <error reading
variable: Cannot access memory at address 0x1dfa82f4>, <error reading
variable: Cannot access memory at address 0xb2e80768>, <error reading
variable: Cannot access memory at address 0x59fffff4>, <error reading
variable: Cannot access memory at address 0x94e8b7>, <error reading
variable: Cannot access memory at address 0xc359fff4>, <error reading
variable: Cannot access memory at address 0x5a242ccd>, <error reading
variable: Cannot access memory at address 0xe005ddb7>, <error reading
variable: Cannot access memory at address 0xd97c90d7>, <error reading
variable: Cannot access memory at address 0xddfdd9bd>, <error reading
variable: Cannot access memory at address 0xd9c0d9cd>, <error reading
variable: Cannot acces
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
--------------------------------------------------------------------
the test code was quite simple:
#include <wx/wx.h>
#include <string>
#include <map>
#include <list>
#include <stack>
#include <vector>
int main()
{
wxString wxStr(L"wxString");
wxStr += L" Value";
std::string stdStr("std::string");
stdStr.append(" value");
std::map<int, std::string> m;
m[0] = "000";
m[1] = "111";
wxString& wxStrRef = wxStr;
wxStrRef += L" Ref";
std::string& stdStrRef = stdStr;
stdStrRef += " Ref";
std::list<std::string> l = {"a", "b", "c"};
std::vector<std::string> v = {"a", "b", "c"};
std::stack<std::string> s;
s.push("a");
s.push("b");
return 0;
}
and set break-point in the first line. then run the "p v" command.
Hope this helps. thanks.
asmwarrior
prev parent reply other threads:[~2010-12-18 2:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CB66700.3000907@gmail.com>
[not found] ` <m3tykn2id8.fsf@fleche.redhat.com>
2010-10-19 20:17 ` RFA: add python exception subclasses (Was: gdb with python support still get crash on showing uninitialized local variables) Tom Tromey
2010-10-19 21:13 ` Eli Zaretskii
2010-10-20 5:19 ` gdb with python support still get crash on showing uninitialized local variables asmwarrior
2010-10-22 19:13 ` Tom Tromey
2010-10-22 21:22 ` Eli Zaretskii
2010-10-29 19:18 ` Joel Brobecker
2010-10-29 22:01 ` Eli Zaretskii
2010-10-31 2:24 ` asmwarrior
2010-11-12 20:47 ` RFA: add python exception subclasses Tom Tromey
[not found] ` <AANLkTinsJLTZT0ws=LbpYcq85_Z9_R=fcXz+J+kqScJU@mail.gmail.com>
2010-12-17 19:04 ` Tom Tromey
2010-12-18 2:26 ` asmwarrior [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=4D0C1C9D.30204@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=tromey@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