From mgiuli@no@m@il @ending from gm@il@com  Fri Aug 31 16:50:56 2018
From: mgiuli@no@m@il @ending from gm@il@com (Marco Giuliano)
Date: Fri, 31 Aug 2018 16:50:56 +0200
Subject: [Rd] Segfault when performing match on POSIXlt object
In-Reply-To: <23433.19189.841070.766209@stat.math.ethz.ch>
References: <CAA9Rc3PFDr_Rn9toAcwpp5MOvcdEbGMgfDnc7n6PFK+cHxZYAw@mail.gmail.com>
 <23433.18919.859126.521094@stat.math.ethz.ch>
 <23433.19189.841070.766209@stat.math.ethz.ch>
Message-ID: <CAA9Rc3N=Lji03ozt0qC=CeOa589ckQc9=iuq3hAmJfDLhmnkWw@mail.gmail.com>

Hi Martin,
should I file a formal bug report somewhere or you've already done it ?

On Fri, Aug 31, 2018 at 4:04 PM Martin Maechler <maechler at stat.math.ethz.ch>
wrote:

> >>>>> Martin Maechler  on Fri, 31 Aug 2018 16:00:07 +0200 writes:
>
> >>>>> Marco Giuliano on Fri, 31 Aug 2018 08:53:02 +0200 writes:
>
>     >> Hi All, I found a possible unexpected behavior when
>     >> performing match/%in% on POSIXlt objects, e.g. :
>
>     >> d <- as.POSIXlt('2018-01-01')
>
>     >> # match(<anything>,<POSIXlt>) --> segfault match(0,d)
>
>     >> # consequently also this fails :
>
>     > 0 %in% d
>
>     >> REPORTED ERROR ON LINUX: *** caught segfault *** address
>     >> 0x16dc2, cause 'memory not mapped'
>
>     >> Verified on 3.5.0 on linux, 3.5.1 on Windows.
>
>     > Confirmed (Linux, I think all version >= 3.4.0, but not in
>     > R 3.3.3 (or earlier, presumably).
>
> ooops that was an offset error:
>
>       Bug in all versions >= 3.3.3,
>       but not in 3.2.5 (or earlier, presumably)
>
>

	[[alternative HTML version deleted]]



[Rd] Segfault when performing match on POSIXlt object
Marco Giuliano