From: Lerele <lerele@champenstudios.com>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb-patches@sourceware.org
Subject: Re: [gdbserver/win32] (4/11) New interrupting method
Date: Sun, 25 Nov 2007 20:39:00 -0000 [thread overview]
Message-ID: <4749DD6E.5090407@champenstudios.com> (raw)
In-Reply-To: <4749C306.7050003@portugalmail.pt>
My mistake, I did not read the entire patch chain.
Pedro Alves escribió:
> Lerele wrote:
>> I think this patch breaks interrupt functionality.
>> The function suspend_one_thread in the new patch does not seem to
>> retreive the thread context and sets the thread suspend count to 1,
>> so the next call to thread_rec that should happen in gdbserver will
>> get incorrect thread context.
>>
>> My interrupt patch I sent initially used thread_rec to pause the
>> child threads, so get context should work here.
>> I think it's more correct anyway to use thread_rec everywhere so that
>> SuspendThread is centralized in one unique function.
>>
>> Is this correct, or is there something I may have slipped reading
>> your patch?
>>
>
> You slipped reading the previous patch in the series :-)
>
> The previous patch in the series [1] has this hunk:
>
> @@ -105,10 +105,19 @@ thread_rec (DWORD id, int get_context)
> return NULL;
>
> th = inferior_target_data (thread);
> - if (!th->suspend_count && get_context)
> + if (get_context && th->context.ContextFlags == 0)
> {
> - if (id != current_event.dwThreadId)
> - th->suspend_count = SuspendThread (th->h) + 1;
> + if (!th->suspended)
> + {
> + if (SuspendThread (th->h) == (DWORD) -1)
> + {
> + DWORD err = GetLastError ();
> + OUTMSG (("warning: SuspendThread failed in thread_rec, "
> + "(error %d): %s\n", (int) err, strwinerror
> (err)));
> + }
> + else
> + th->suspended = 1;
> + }
>
> (*the_low_target.get_thread_context) (th, ¤t_event);
> }
>
> Which means that thread_rec will fetch the register context
> if it hasn't already (th->context.ContextFlags == 0),
> not if the thread wasn't suspended, which makes more sense:
> "If you want the registers, and you don't have them already",
> as opposed to:
> "If you want the registers and the thread is not suspended".
>
> [1] - [gdbserver/win32] (3/11) Fix suspend count handling
> http://sourceware.org/ml/gdb-patches/2007-11/msg00216.html
>
next prev parent reply other threads:[~2007-11-25 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 2:07 Pedro Alves
2007-11-25 15:00 ` Lerele
2007-11-25 18:47 ` Pedro Alves
2007-11-25 20:39 ` Lerele [this message]
2007-12-01 18:56 ` Daniel Jacobowitz
2007-12-03 3:53 ` Pedro Alves
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=4749DD6E.5090407@champenstudios.com \
--to=lerele@champenstudios.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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