Sent: Thursday, March 23, 2023 7:17 AM
To: Ivan Krylov
Cc: Kenny, Christopher ;
r-package-devel@r-project.org
Subject: Re: [R-pkg-devel] How to identify what flags "Additional Issues" for
UBSAN
In line
https://github.com/alarm-redist/redist/blob/f1ed042841469456c1d8c149092bc818e2
In line
https://github.com/alarm-redist/redist/blob/f1ed042841469456c1d8c149092bc818e2a5c1a5/src/wilson.cpp#L165
int max_try = 50 * remaining * ((int) std::log(remaining));
you need to ensure remaining > 0. At some point it became -1.
On Thu, 23 Mar 2023 at 22:07, Ivan Krylov wrote:
>
> В
On 3/22/23 16:51, Kenny, Christopher wrote:
Hi folks,
I'm the maintainer of the redist package
(https://cran.r-project.org/web/checks/check_results_redist.html) which was flagged for
additional issues with clang-UBSAN and gcc-UBSAN. Both of the 00check.log files say that
the status is "OK"
В Wed, 22 Mar 2023 15:51:54 +
"Kenny, Christopher" пишет:
> Is there an easy way to identify what is causing the flag?
Unfortunately, it's _all_ the sanitizer errors.
> wilson.cpp:165:34: runtime error: signed integer overflow:
> -2147483648 * -1 cannot be represented in type 'int'
>
Hi folks,
I'm the maintainer of the redist package
(https://cran.r-project.org/web/checks/check_results_redist.html) which was
flagged for additional issues with clang-UBSAN and gcc-UBSAN. Both of the
00check.log files say that the status is "OK" at the bottom.
Is there an easy way to
