From: Sami Wagiaalla <swagiaal@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
Project Archer <archer@sourceware.org>
Subject: gdb hang
Date: Thu, 03 Sep 2009 18:58:00 -0000 [thread overview]
Message-ID: <4AA01167.6000300@redhat.com> (raw)
Hi Jan,
This should fix the gdb hang problem with open office:
108568024684babfeb3876f76064ff9cfced827a
I was not able to get the reproducer to work the commit
includes a test case which causes the hang.
I still use find_pc_line, although more responsibly now :)
Is there a better way to find out the current line of execution ?
I have tried get_current_source_symtab_and_line but it seems to
always be off by 5 lines.
Sami
next reply other threads:[~2009-09-03 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 18:58 Sami Wagiaalla [this message]
2009-09-03 19:12 ` Jan Kratochvil
2009-09-03 19:27 ` Sami Wagiaalla
2009-09-04 5:42 ` Jan Kratochvil
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=4AA01167.6000300@redhat.com \
--to=swagiaal@redhat.com \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).