This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug python/12127] gdb with python support still get crash on showing uninitialized local variables


http://sourceware.org/bugzilla/show_bug.cgi?id=12127

--- Comment #3 from asmwarrior <asmwarrior at gmail dot com> 2013-05-07 05:09:29 UTC ---
Today, I managed to find one crash problem. See the debug log (crash.txt) as
attachment. 
I use the same sample program to create a "a1.exe", then one debugger_gdb to
start a debugee_gdb, then let the debugee_gdb to load stlc++ python script,
then a1.exe was loaded in debugee_gdb, and I can make debugee_gdb crash when
simply type "p v" command (At the time v is a std::vector auto variable which
was not initialized).

Look at the bt, you can see that gdb (in apply_val_pretty_printer function
call) try to malloc a big buffer which size is 2009291924.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]