Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#46458 - [lua-socket] client:receive() segfaults with buffer > ~4100
Attached to Project:
Community Packages
Opened by Nimrod Maclomhair (nimrod_mack) - Monday, 28 September 2015, 12:54 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 01 October 2015, 19:20 GMT
Opened by Nimrod Maclomhair (nimrod_mack) - Monday, 28 September 2015, 12:54 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 01 October 2015, 19:20 GMT
|
DetailsDescription:
With lua-socket 3.0rc1-7 and lua 5.3.1-1 When trying to read a buffer larger than ca. 4096 bytes (haven't found the exact limit) the program segfaults, leaving something like that in the journal: segfault at 666c347a (mostly random number to me, changes from call to call) ip 0804ce04 (usually the same) sp bfd5f03c (the first two letters stay like that) error 4 in lua[8048000+3e000] (that number and the error code don't change as well) I have tried compiling lua-spcket from scratch (using the attached PKGBUILD, modified from the official version) and the error didn't persist. I do not know wether the error also applies to the x86_64 platform. Steps to reproduce: I have attached a test script, that will start a server on port 8080. Using something like the following line should kill it: $ dd if=/dev/urandom | nc 127.0.0.1 8080 |
This task depends upon
PKGBUILD