public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mstensho at opera dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/15717] New: Printing style()-><whatever method AFAICT>() when running Chromium/Blink freezes
Date: Wed, 03 Jul 2013 10:41:00 -0000	[thread overview]
Message-ID: <bug-15717-4717@http.sourceware.org/bugzilla/> (raw)

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.


             reply	other threads:[~2013-07-03 10:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 10:41 mstensho at opera dot com [this message]
2013-09-27 14:47 ` [Bug c++/15717] " mstensho at opera dot com
2013-09-27 14:57 ` mstensho at opera dot com
2013-09-27 15:01 ` mstensho at opera dot com

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=bug-15717-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).