[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Invalid memory access with Lua 5.1 lua_isnumber()
- From: "Timm S. Mueller" <tmueller@...>
- Date: Wed, 5 Mar 2014 18:03:17 +0100
On Wed, 5 Mar 2014 12:12:06 +0100
"Timm S. Mueller" <tmueller@schulze-mueller.de> wrote:
> I think I have stumbled across a problem in lua_isnumber(). Lua 5.1.5
> is affected, Lua 5.2.2 is not. The following is on Linux x86_64:
> [..]
> $ valgrind /usr/local/bin/lua -e 'require"test".test("none")' # =>
> ==9069== Memcheck, a memory error detector
> ==9069== [..]
> ==9069== Invalid read of size 8
> ==9069== at 0x5A5CE0F: __GI___strncasecmp_l (in /lib64/libc-2.15.so)
> ==9069== by 0x5A0F75C: ____strtod_l_internal (in /lib64/libc-2.15.so)
> ==9069== by 0x40AD99: luaO_str2d (in /usr/local/bin/lua)
I can't reproduce this on an otherwise identical setup when using a
newer version of Valgrind (3.8.1). So an issue with the debug tool, not
Lua.
- Timm
--
Timm S. Mueller <tmueller@schulze-mueller.de>
Schulze & Mueller GbR, Jungstr. 2, 10247 Berlin,
Gesellschafter: Franciska Schulze, Timm S. Mueller,
Tel. +49 30 85610000, http://www.schulze-mueller.de/
