Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA] nameless LOAD_DLL_DEBUG_EVENT causes ntdll.dll to be missing
Date: Thu, 12 Dec 2013 18:51:00 -0000	[thread overview]
Message-ID: <83y53p6gz9.fsf@gnu.org> (raw)
In-Reply-To: <20131212181843.GB3528@adacore.com>

> Date: Thu, 12 Dec 2013 19:18:43 +0100
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> On top of that patch, I was able to implement the same post-init
> trick of looking for ntdll.dll, but not without a couple of surprises:
> we don't have FILENAME_CMP nor a "basename" function in gdbserver
> at the moment. I worked around the first issue by using strcasecmp,
> which is good enough for our purposes. But for the second issue,
> I only had a handful of bad options for our current situation:
>   1. Import the module from gnulib; but that's never an innocent
>      change, and also the documentation says that it does not work
>      for Windows paths;
>   2. Import the libiberty module by hand, which itself depends on
>      their safe-ctype.h module.
>   3. Write a quick ad hoc function that implements basename.
> 
> (1) is a non-starter, and I didn't like either of (2) or (3).
> In the end, I went for (2) as the quickest option towards testing
> the change and sending an RFC patch. Should we go with this approach,
> we'll probably want to add the libiberty dependencies through
> configure.srv instead of inside OBS. That addition should be
> temporary, as the minute we stop looking specifically for ntdll,
> and load all mapped dlls through that loop, we'll stop needing
> lbasename, and will be able to remove the dependency.

I don't understand why you didn't like (2), I think that's the obvious
choice here.


  reply	other threads:[~2013-12-12 18:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 11:31 Joel Brobecker
2013-12-03 19:51 ` Pedro Alves
2013-12-03 20:11   ` Eli Zaretskii
2013-12-05 10:54   ` Joel Brobecker
2013-12-05 12:38     ` Pedro Alves
2013-12-09 11:33       ` Joel Brobecker
2013-12-09 17:08         ` Pedro Alves
2013-12-10 10:06           ` pushed: " Joel Brobecker
2013-12-10 10:06             ` Joel Brobecker
2013-12-10 10:56         ` Joel Brobecker
2013-12-10 13:41           ` Pedro Alves
2013-12-10 13:58             ` Pedro Alves
2013-12-12 18:18               ` Joel Brobecker
2013-12-12 18:51                 ` Eli Zaretskii [this message]
2013-12-12 19:08                 ` Pedro Alves
2013-12-12 22:06                 ` Tom Tromey
2013-12-13 10:06                   ` Pedro Alves
2013-12-13 11:04                     ` Joel Brobecker
2013-12-13 11:21                       ` Pedro Alves
2013-12-13 19:38                     ` Tom Tromey
2013-12-13 14:17                 ` Joel Brobecker
2013-12-13 14:42                   ` Pedro Alves
2013-12-13 15:45                     ` Joel Brobecker

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=83y53p6gz9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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