qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Fabien Chouteau <chouteau@adacore.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Add GDB qAttached support
Date: Mon, 11 Mar 2013 12:36:24 +0100	[thread overview]
Message-ID: <513DC1B8.5000801@web.de> (raw)
In-Reply-To: <513DBE81.2060001@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]

On 2013-03-11 12:22, Fabien Chouteau wrote:
> On 03/10/2013 09:06 AM, Jan Kiszka wrote:
>>> @@ -2491,6 +2493,10 @@ static int gdb_handle_packet(GDBState *s, const char *line_buf)
>>>              break;
>>>          }
>>>  #endif
>>> +        if (strncmp(p, "Attached", 8) == 0) {
>>> +            put_packet(s, gdb_attached ? "1" : "0");
>>> +            break;
>>> +        }
>>
>> This works as expected for system mode, but now inverts the behaviour
>> for user mode - that's unexpected and not ok.
>>
> 
> OK, I can change the default value for user mode.
> 
>>> diff --git a/qemu-options.hx b/qemu-options.hx
>>> index 6f9334a..026d3eb 100644
>>> --- a/qemu-options.hx
>>> +++ b/qemu-options.hx
>>> @@ -2988,6 +2988,13 @@ property must be set.  These objects are placed in the
>>>  '/objects' path.
>>>  ETEXI
>>>
>>> +DEF("gdb-not-attached", 0, QEMU_OPTION_gdb_not_attached,
>>> +    "-gdb-not-attached\n"
>>> +    "                Do not set Gdb remote server in attached mode.\n"
>>> +    "                When exiting debugging session, Gdb will send a 'kill'\n"
>>> +    "                command instead of a 'detach'.\n",
>>> +    QEMU_ARCH_ALL)
>>> +
>>
>> First of all, why do we need this configurable? In which use cases do
>> you want attached mode for user emulation or kill mode for system
>> emulation/virtualization?
>>
> 
> It's more convenient for us, we expect QEMU to terminate at the end of
> debugging session because we do not run big systems/kernels but short
> test programs. It used to be the default behavior of QEMU, and our
> test-suites, IDE, developers and users are expecting this.

And it's not possible to replace 'q' with 'k' in your gdb control
scripts? That gives you a well-defined behaviour, and we don't need to
tweak QEMU, specifically its command line, for this special case.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-03-11 11:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 16:03 [Qemu-devel] [PATCH 1/2] Add GDB qAttached support Fabien Chouteau
2013-03-05 16:03 ` [Qemu-devel] [PATCH 2/2] Revert "gdbstub: Do not kill target in system emulation mode" Fabien Chouteau
2013-03-05 16:07   ` Jan Kiszka
2013-03-05 16:30     ` Fabien Chouteau
2013-03-10  8:06 ` [Qemu-devel] [PATCH 1/2] Add GDB qAttached support Jan Kiszka
2013-03-11 11:22   ` Fabien Chouteau
2013-03-11 11:36     ` Jan Kiszka [this message]
2013-03-11 11:59       ` Fabien Chouteau
  -- strict thread matches above, loose matches on Subject: below --
2013-03-12 14:31 [Qemu-devel] [PATCH 0/2] " Fabien Chouteau
2013-03-12 14:31 ` [Qemu-devel] [PATCH 1/2] " Fabien Chouteau
2013-03-12 14:40   ` Jan Kiszka
2015-01-31  9:28 Jan Kiszka
2015-02-04 13:36 ` Pedro Alves
2015-02-04 14:06   ` Jan Kiszka
2015-02-04 14:30   ` Peter Maydell

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=513DC1B8.5000801@web.de \
    --to=jan.kiszka@web.de \
    --cc=chouteau@adacore.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).