From: Pedro Alves <palves@redhat.com>
To: Ivo Raisr <ivosh@ivosh.net>
Cc: gdb@sourceware.org
Subject: Re: Multi-packet gdb server request/response - problem?
Date: Mon, 16 Dec 2013 14:31:00 -0000 [thread overview]
Message-ID: <52AF0EB5.5030300@redhat.com> (raw)
In-Reply-To: <CANXv6=tdRyennxro4x2r3HXRT4OvyNEDDY+SufE2F-6_DR2iJw@mail.gmail.com>
On 12/14/2013 03:39 AM, Ivo Raisr wrote:
> No regressions found by the test suite. Good.
Thanks.
>
> I filed the following bug:
> https://sourceware.org/bugzilla/show_bug.cgi?id=16329
>
> Could we get it fixed in the 7.6.x branch as well?
Sure, done:
https://sourceware.org/ml/gdb-patches/2013-12/msg00573.html
Not sure if there'll ever be another 7.6 release, though.
--
Pedro Alves
next prev parent reply other threads:[~2013-12-16 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 3:39 Ivo Raisr
2013-12-16 14:31 ` Pedro Alves [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-10 12:23 Ivo Raisr
2013-12-10 21:46 ` Philippe Waroquiers
[not found] ` <CANXv6=vFYfEDLPVHv_TRK4VTLmFX6c+2hvmodM9dg3gcJA4_jQ@mail.gmail.com>
2013-12-12 15:14 ` Fwd: " Ivo Raisr
2013-12-12 15:44 ` Ivo Raisr
2013-12-12 16:46 ` Pedro Alves
2013-12-11 11:43 ` Yao Qi
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=52AF0EB5.5030300@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=ivosh@ivosh.net \
/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