This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/15717] New: Printing style()-><whatever method AFAICT>() when running Chromium/Blink freezes
- From: "mstensho at opera dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 03 Jul 2013 10:41:15 +0000
- Subject: [Bug c++/15717] New: Printing style()-><whatever method AFAICT>() when running Chromium/Blink freezes
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15717
Bug ID: 15717
Summary: Printing style()-><whatever method AFAICT>() when
running Chromium/Blink freezes
Product: gdb
Version: 7.6
Status: NEW
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: mstensho at opera dot com
When I build the content_shell executable that is part of the Chromium browser
[1] and set a breakpoint in e.g. RenderBlock::paint() (in
third_party/WebKit/Source/core/rendering/RenderBlock.cpp) and attempt to print
style()->display(), gdb 7.6 just freezes. I waited several minutes. This is
something that used to work.
I built content_shell like this, FWIW:
GYP_PARALLEL=1 GYP_GENERATORS=ninja build/gyp_chromium
ninja -C out/Debug content_shell
I start content_shell from gdb like this:
r --single-process
(otherwise it will be impossible to set breakpoints at all)
I initially discovered this with Debian jessie, which uses a provides a
(somewhat modified, I suppose) gdb 7.6 package, but the problem persisted when
I compiled my own vanilla gdb 7.6 and tried there.
I then downgraded to Debian wheezy (current stable), which has gdb 7.4, removed
my self-built gdb 7.6, and the problem went away again (without rebuilding
content_shell). Then I tried again with my self-built gdb 7.6, and the freeze
was back.
What I'm trying to say is that this doesn't appear to be a Debian-only problem,
and also that it actually appears to be a gdb problem.
[1] http://dev.chromium.org/developers/how-tos/get-the-code
--
You are receiving this mail because:
You are on the CC list for the bug.