From: Eli Zaretskii <eliz@gnu.org>
To: Freddie Chopin <freddie_chopin@op.pl>
Cc: gdb@sourceware.org, palves@redhat.com
Subject: Re: Problem with continue/halt - async support
Date: Fri, 27 Jun 2014 08:35:00 -0000 [thread overview]
Message-ID: <834mz692dg.fsf@gnu.org> (raw)
In-Reply-To: <53AD2AC8.6040307@op.pl>
> Date: Fri, 27 Jun 2014 10:26:48 +0200
> From: Freddie Chopin <freddie_chopin@op.pl>
> CC: palves@redhat.com
>
> This commit (before whole "async support" series) works fine:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=434415618f6bb9ac428a8d18ab33111920cd04dc
>
> This commit (after whole "async support" series) has the problem:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=a09dd4413d1a4ea063173d4822635f41c885f6fe
>
> For completeness - current HEAD still has the problem.
>
> If anyone didn't notice that, then this probably is Windows specific, or
> even mingw-w64 specific, or maybe remote-target-OpenOCD specific. As I
> wrote previously - GDB is compiled with the most recent package from
> Arch Linux, so that's GCC 4.9.0 mingw-w64. The problem is the same for
> 32-bit and 64-bit compilation.
>
> Any ideas what can I test to help with the bug? I'm going to post a bug
> report too...
Thanks for digging into this.
I suggest to start by posting a full self-contained recipe for
reproducing the problem. It would be nice if the problem were
reproducible in native debugging, but if that's impossible, then a
target-specific recipe is also OK.
prev parent reply other threads:[~2014-06-27 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 6:52 Problem with continue/halt Freddie Chopin
2014-06-26 8:44 ` Freddie Chopin
2014-06-26 15:24 ` Eli Zaretskii
2014-06-26 15:39 ` Freddie Chopin
2014-06-26 16:23 ` Eli Zaretskii
2014-06-27 7:23 ` Freddie Chopin
2014-06-27 8:26 ` Problem with continue/halt - async support Freddie Chopin
2014-06-27 8:35 ` Eli Zaretskii [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=834mz692dg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=freddie_chopin@op.pl \
--cc=gdb@sourceware.org \
--cc=palves@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