From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC 6/9] Unify windows specifics into common/windows-hdep files
Date: Thu, 31 Mar 2011 13:58:00 -0000 [thread overview]
Message-ID: <004501cbef22$04b728b0$0e257a10$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <83k4fgqtqp.fsf@gnu.org>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : mercredi 30 mars 2011 21:44
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC 6/9] Unify windows specifics into common/windows-hdep
files
>
> > From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> > Date: Wed, 30 Mar 2011 14:05:06 +0200
> >
> > - cygwin_conv_to_win32_path (program, real_path);
> > + windows_conv_path (WINDOWS_POSIX_TO_NATIVE_A, program, real_path,
> > + MAXPATHLEN);
> > program = real_path;
> > #endif
> >
> > @@ -924,11 +929,7 @@ win32_add_one_solib (const char *name, CORE_ADDR
> > load_addr)
> > }
> > #endif
> >
> > -#ifdef __CYGWIN__
> > - cygwin_conv_to_posix_path (buf, buf2);
> > -#else
> > - strcpy (buf2, buf);
> > -#endif
> > + windows_conv_path (WINDOWS_NATIVE_A_TO_POSIX, buf, buf2, MAX_PATH +
1);
> >
> > loaded_dll (buf2, load_addr);
>
> See my other mail: windows_conv_path can fail, but the code does not
> check for errors, and bravely used the possibly invalid results.
As said in other emails...
the existing code also didn't care to check for a possible error in
cygwin_conv_path.
But I agree with you that a check should be added,
I just don't really know what to do in case of failure...
Thanks again for the comments.
Pierre
next prev parent reply other threads:[~2011-03-30 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00b101cbeed2$b5aa4990$20fedcb0$%muller@ics-cnrs.unistra.fr>
2011-03-30 21:00 ` Eli Zaretskii
2011-03-31 13:58 ` Pierre Muller [this message]
2011-03-30 12:15 Pierre Muller
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='004501cbef22$04b728b0$0e257a10$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=eliz@gnu.org \
--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