R devel - Aug 2018 - Segfault when performing match on POSIXlt object

>>>>> 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)

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]]

>>>>> Marco Giuliano 
>>>>>     on Fri, 31 Aug 2018 16:50:56 +0200 writes:
    > Hi Martin, should I file a formal bug report somewhere or
    > you've already done it ?

No, I haven't, 
and as I may not address this bug further myself (in the near
future), it may be best if you file a formal report.

I will create an account for you on R's bugzilla - you will be
notified and can update your initial pseudo-random password.

Best,
Martin