Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Sun, 14 Jun 2009 14:05:00 -0000	[thread overview]
Message-ID: <200906141504.53294.pedro@codesourcery.com> (raw)
In-Reply-To: <1244969225.20290.59.camel@pavilion>

On Sunday 14 June 2009 09:47:05, Danny Backx wrote:
> > IIRC, psapi.dll does exist on WinCE, but it is
> > not bundled with the OS usually.  If I'm not confusing
> > it with some other dll, I think I have it for ARM, gotten
> > from some MSFT redistributable, and it does work.
> 
> It isn't on the Windows Embedded for x86 that I'm using. But the
> gdbserver code appears to be well written : it silently falls back to
> something that does work.
> 
> I've not messed with that code because "if it ain't broke, don't fix
> it". I could have surrounded it with #ifndef _WIN32_WCE but I didn't see
> the point.

I've no idea what you're talking about here, or even why
we talking about psapi.dll anyway.  The only hunks in your
patches touching psapi related things are:


-  if (!load_psapi ())
+  if (!load_psapi ()) {
     goto failed;
+  }

and...

+  /* Note : no psapi.dll on CE, fall back to get_image_name below. */
   if (!psapi_get_dll_name ((DWORD) event->lpBaseOfDll, dll_buf))


The fact that psapi is dynamicaly loaded with LoadLibrary
was exactly so that gdbserver falls back to other mechanisms.
Even on desktop Windows it isn't garanteed that psapi.dll will be
around.  Please drop these spurious hunks from the patch.

BTW, 

-  if (!load_psapi ())
+  if (!load_psapi ()) {
     goto failed;
+  }

The coding conventions states to not surround a single statement
with curly braces, so that original version would be the correct
form --- your patch would make it wrong.


+  /* Note : no psapi.dll on CE, fall back to get_image_name below. */

Double spaces after period, no space before ':'.  This would be:

  /* Note: no psapi.dll on CE, fall back to get_image_name below.  */

But as I said, this hunk is unnecessary.

-- 
Pedro Alves


  parent reply	other threads:[~2009-06-14 14:05 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
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 [this message]
  -- 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=200906141504.53294.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