segmentation fault on Num.power_num #6164
Comments
|
Comment author: @lefessan Fixed in commit r14074. There is a buffer overflow in Nat.make_power_base when base=0 or 1. This case can only be triggered in Nat.power_base_int, so I added a test there for base=0 or 1. |
|
Comment author: kanig Thank you, that was quick! I have a couple of questions though ... :-) Can you tell me if the fix will be in 4.01? Is it possible to workaround this problem, e.g. by avoiding calls with certain arguments to Num.power_num? Thanks in advance. |
|
Comment author: @damiendoligez This fix will be in 4.01.0. |
|
Comment author: kanig That's great, thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original bug ID: 6164
Reporter: kanig
Assigned to: @lefessan
Status: closed (set by @xavierleroy on 2015-07-24T08:38:59Z)
Resolution: fixed
Priority: normal
Severity: minor
Platform: x86_64
OS: linux
OS Version: Debian 3.2.35-2
Version: 4.01.0+beta/+rc
Fixed in version: 4.00.1
Category: otherlibs
Monitored by: @gasche
Bug description
The attached file produces a segfault both in bytecode and native format. Note that the platform is important: it happens on x86_64, and I have only seen it on linux.
I have reproduced this in 3.12.1, 4.00.1 and 4.01.0rc.
Steps to reproduce
ocamlbuild -lib nums numbug.ml
./numbug.native
Additional information
gdb locates the crash in "bng_amd64_mult_add_digit".
File attachments
The text was updated successfully, but these errors were encountered: