From: Pedro Alves <pedro@codesourcery.com>
To: danny.backx@scarlet.be
Cc: gdb-patches@sourceware.org
Subject: Re: Patch : gdbserver get_image_name on CE
Date: Wed, 01 Jul 2009 20:12:00 -0000 [thread overview]
Message-ID: <200907012113.06018.pedro@codesourcery.com> (raw)
In-Reply-To: <1246473648.15871.201.camel@pavilion>
On Wednesday 01 July 2009 19:40:48, Danny Backx wrote:
> > And you never did explain what was broken with get_image_name
> > that you had to fix, as I asked $n emails ago, right?
>
> Err. I am almost certain that the return value of GetProcessMemory isn't
> a reliable way to verify success.
Thanks! You know that I couldn't guess what you were thinking or were
almost certain, right?
> Its final parameter is. Or at least
> that is my experience. Of course, MSDN docs don't mention this.
I'm not convinced of this. I think you must stumbling on some other bug,
or a bug in the device. MSDN docs mention this:
http://msdn.microsoft.com/en-us/library/ms680553(VS.85).aspx
"Reads data from an area of memory in a specified process. The entire area to be read
must be accessible or the operation fails."
That's why we read data bytewise to know the length or the string first.
So what you're doing may work for you, but it may fail for someone
else (other device, binary, etc.).
It makes *no sense* to be able to read the data in one go,
but not be able to read it bytewise. This would mean that ReadProcessMemory
could fail in many other circumstances --- it is used when gdb wants to
read memory of off the inferior...
So, please, now that you have a gdbserver that works, debug gdbserver
with gdbserver, and step through that routine (the old implementation),
and see where/why it is failing. Posting a log of that debug session
showing the failure would do wonders in convincing me where is the bug.
Hey, you may even have a compiler bug, right?
> I tested this on ARM and on i386. Real devices, not emulators. The ARM
> implementation worked as it was, and continued to work after my fix. The
> i386 version didn't work before, does work after the fix.
>
> Is this sufficient explanation?
I'm not convinced yet. :-)
I'll see about cleaning up the bits of your patch that are OK and
apply them (you still aren't following the code conventions). Then
we can focus on just this bit.
--
Pedro Alves
next prev parent reply other threads:[~2009-07-01 20:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2009-06-13 6:28 ` Johnny Willemsen
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=200907012113.06018.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=danny.backx@scarlet.be \
--cc=gdb-patches@sourceware.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