From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Tomas Martinec <fyzmat@gmail.com>
Subject: Re: Stepping of multithreaded application
Date: Tue, 10 May 2011 18:37:00 -0000 [thread overview]
Message-ID: <201105101936.55707.pedro@codesourcery.com> (raw)
In-Reply-To: <BANLkTimdW6nk=7LA0QLEFk8PbahskcDcUQ@mail.gmail.com>
On Tuesday 10 May 2011 17:27:20, Tomas Martinec wrote:
> Sorry for quite a story. I have been solving it for some time and
> advice would be appreciated. Any idea why the GDB does not send the
> Hc3 command? Maybe I just cannot see something simple.
Can you paste the relevant logs again, but with "set debug infrun 1"
enabled in addition to "set debug remote 1" ? It's probably possible to
infer what's going on from the remote log alone, but the infrun
log should make it easier.
--
Pedro Alves
next prev parent reply other threads:[~2011-05-10 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 16:27 Tomas Martinec
2011-05-10 18:37 ` Pedro Alves [this message]
2011-05-11 6:06 ` Tomas Martinec
2011-05-11 17:29 ` Pedro Alves
2011-05-12 10:45 ` Tomas Martinec
2011-05-16 11:17 ` Pedro Alves
2011-05-16 15:23 ` Tomas Martinec
2011-05-17 12:03 ` Pedro Alves
2011-05-17 14:07 ` Tomas Martinec
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=201105101936.55707.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=fyzmat@gmail.com \
--cc=gdb@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).