From: Danny Backx <danny.backx@scarlet.be>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch : gdbserver get_image_name on CE
Date: Fri, 12 Jun 2009 22:18:00 -0000 [thread overview]
Message-ID: <1244845085.11918.283.camel@pavilion> (raw)
In-Reply-To: <200906071916.03048.pedro@codesourcery.com>
On Sun, 2009-06-07 at 19:16 +0100, Pedro Alves wrote:
> On Sunday 07 June 2009 19:01:39, Danny Backx wrote:
>
> > Feel free to ignore these patches until they're complete, if that is a
> > better idea.
>
> It's fine to send unfinished patches for comments, if you'd like, but
> please say so explicitly, so I don't waste time trying to understand
> what they're for, for nothing.
>
> > I sent this one separately because it looked contained.
>
> Thanks for doing that. Splitting self contained patches is
> always good.
Excellent news : I just figured out why gdbserver was failing on CE/x86
where the same code worked for ARM.
The GetThreadContext call looked different between win32-i386-low.c and
its ARM equivalent :
th->context.ContextFlags =
CONTEXT_FULL |
CONTEXT_FLOATING_POINT |
CONTEXT_EXTENDED_REGISTERS |
CONTEXT_DEBUG_REGISTERS;
GetThreadContext (th->h, &th->context);
On ARM, only CONTEXT_FULL and CONTEXT_FLOATING_POINT were used. The call
on x86 returned error 87 (ERROR_INVALID_PARAMETER) but MSDN doesn't
contain clues as to what that means.
I'll try to figure out whether this breaks anything, but at first sight
this small change (and a couple of others I have yet to submit) makes
gdbserver work.
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
next prev parent reply other threads:[~2009-06-12 22:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 9:18 Danny Backx
2009-06-07 17:03 ` Pedro Alves
2009-06-07 18:02 ` Danny Backx
2009-06-07 18:15 ` Pedro Alves
2009-06-07 19:13 ` Danny Backx
2009-06-07 19:28 ` Pedro Alves
2009-06-08 18:13 ` Danny Backx
2009-06-12 22:18 ` Danny Backx [this message]
2009-06-13 6:28 ` Johnny Willemsen
2009-06-13 14:29 Danny Backx
2009-06-13 18:05 ` Pedro Alves
2009-06-13 18:08 ` Pedro Alves
2009-06-14 8:35 ` Danny Backx
2009-06-14 13:56 ` Pedro Alves
2009-06-14 8:47 ` Danny Backx
2009-06-14 9:48 ` Danny Backx
2009-06-14 14:23 ` Pedro Alves
2009-06-21 9:50 ` Danny Backx
2009-06-30 21:07 ` Danny Backx
2009-06-30 21:56 ` Pedro Alves
2009-07-01 18:41 ` Danny Backx
2009-07-01 18:52 ` Pedro Alves
2009-07-01 19:12 ` Danny Backx
2009-07-01 20:12 ` Pedro Alves
2009-07-04 18:14 ` Pedro Alves
2009-07-08 9:55 ` Danny Backx
2009-07-08 11:34 ` Danny Backx
2009-07-27 20:40 ` Danny Backx
2009-07-01 19:31 ` Danny Backx
2009-06-14 14:34 ` Pedro Alves
2009-06-14 14:05 ` 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=1244845085.11918.283.camel@pavilion \
--to=danny.backx@scarlet.be \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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