public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/12255] gdb hangs when trying to load a corefile.
Date: Tue, 23 Aug 2011 09:51:00 -0000	[thread overview]
Message-ID: <bug-12255-4717-qFW2TD5Zro@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12255-4717@http.sourceware.org/bugzilla/>

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

Paul Pluzhnikov <ppluzhnikov at google dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING

--- Comment #4 from Paul Pluzhnikov <ppluzhnikov at google dot com> 2011-08-19 16:53:12 UTC ---
(In reply to comment #3)

> I can't see that advice, the question was removed.

So it was.

> Do you recall what it was?

IIRC, it was to:

1) confirm that the problem still exists in latest GDB releases and
2) to build GDB with symbols and see where it is looping (and with what
parameters).

As is, this bug report appears pretty useless. Marking it as "waiting for
additional info".

-- 
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.


      parent reply	other threads:[~2011-08-19 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23  5:25 [Bug c++/12255] New: " dumrat at gmail dot com
2010-11-23  7:05 ` [Bug c++/12255] " dumrat at gmail dot com
2010-11-23  7:24 ` dumrat at gmail dot com
2010-11-23 10:54 ` dumrat at gmail dot com
2010-11-28 18:53 ` ppluzhnikov at google dot com
2011-08-19 15:50 ` tromey at redhat dot com
2011-08-23  9:51 ` ppluzhnikov at google dot com [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=bug-12255-4717-qFW2TD5Zro@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).