From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Christian Franke <Christian.Franke@t-online.de>
Cc: cygwin-apps@cygwin.com
Subject: Re: [PATCH rebase] peflags: Fix ULONG range checks
Date: Tue, 8 Aug 2023 10:55:13 +0200 [thread overview]
Message-ID: <ZNIC8T/q4rIdiC3v@calimero.vinschen.de> (raw)
In-Reply-To: <b9d50afe-6308-205d-ce04-0731269ca8e5@t-online.de>
On Aug 8 10:40, Christian Franke via Cygwin-apps wrote:
> Corinna Vinschen wrote:
> > On Aug 8 10:06, Christian Franke via Cygwin-apps wrote:
> > > Corinna Vinschen via Cygwin-apps wrote:
> > > > Hi Christian,
> > > >
> > > > On Aug 7 16:07, Christian Franke via Cygwin-apps wrote:
> > > > > Minor issue found during tests of the upcoming 'peflags --timestamp' patch.
> > > > >
> > > > > --
> > > > > Regards,
> > > > > Christian
> > > > >
> > > > > ...
> > > > > diff --git a/peflags.c b/peflags.c
> > > > > index 93eaa0b..d98b121 100644
> > > > > --- a/peflags.c
> > > > > +++ b/peflags.c
> > > > > @@ -30,7 +30,6 @@
> > > > > #include <unistd.h>
> > > > > #include <getopt.h>
> > > > > #include <errno.h>
> > > > > -#include <limits.h>
> > > > > #if defined (__CYGWIN__) || defined (__MSYS__)
> > > > > #include <sys/mman.h>
> > > > > #endif
> > > > > @@ -598,7 +597,7 @@ handle_num_option (const char *option_name,
> > > > > || sizeof_vals[option_index].value > 0x0000ffffffffffffULL
> > > > > /* Just a ULONG value */
> > > > > || (sizeof_vals[option_index].is_ulong
> > > > > - && sizeof_vals[option_index].value > ULONG_MAX))
> > > > > + && sizeof_vals[option_index].value > 0x00000000ffffffffULL))
> > > > What about using MAXDWORD or MAXULONG32 instead?
> > > Of course :-)
> > >
> > > Christian
> > >
> > Pushed. I've started deploying a new release.
>
> I'm currently working on 'rebase -c, --checksum' and found one minor issue:
> pechecksum.* are missing in SRC_DISTFILES.
Ok, I stopped the deployment. Are you going to send fixes?
Corinna
prev parent reply other threads:[~2023-08-08 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 14:07 Christian Franke
2023-08-07 18:50 ` Corinna Vinschen
2023-08-08 8:06 ` Christian Franke
2023-08-08 8:37 ` Corinna Vinschen
2023-08-08 8:40 ` Christian Franke
2023-08-08 8:55 ` Corinna Vinschen [this message]
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=ZNIC8T/q4rIdiC3v@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=Christian.Franke@t-online.de \
--cc=cygwin-apps@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).