From: Pedro Alves <palves@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 2/2] Test GDB connection to GDBserver with no symbol files
Date: Wed, 13 Apr 2016 17:38:00 -0000 [thread overview]
Message-ID: <570E8400.4020001@redhat.com> (raw)
In-Reply-To: <1460562803-10817-3-git-send-email-lgustavo@codesourcery.com>
On 04/13/2016 04:53 PM, Luis Machado wrote:
> This test exercises the scenarios where we attempt to connect GDB to GDBserver
> in standard remote mode, query the symbol file path, attempt to open said
> symbol file on GDB's end and fail, causing the connection to drop abruptly.
>
> Regression-tested on x86-64/Ubuntu.
>
> Does it look OK now?
Perfect.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-04-13 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 15:53 [PATCH v3 0/2] Debugging without a symbol file Luis Machado
2016-04-13 15:53 ` [PATCH v3 1/2] Debugging without a binary (regression) Luis Machado
2016-04-13 17:37 ` Pedro Alves
2016-04-13 15:53 ` [PATCH v3 2/2] Test GDB connection to GDBserver with no symbol files Luis Machado
2016-04-13 17:38 ` Pedro Alves [this message]
2016-04-13 20:25 ` Luis Machado
2016-04-15 14:06 ` Yao Qi
2016-04-15 14:19 ` Luis Machado
2016-04-15 14:36 ` Luis Machado
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=570E8400.4020001@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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