(Oh! For some reason I am not getting all of the bug mail from Launchpad. At least: I missed notifications about this bug.)
Hm... It seems that free() on Ubuntu checks that nothing was written outside of the allocated space? Does malloc() put a "canary" at the tail? Anyway, I am pretty sure that the patch attached to bug #1641592 will fix this crash. It is same patch as the second one attached to https://lists.gnu.org/archive/html/nano-devel/2016-04/msg00075.html, which was applied upstream nearly a year ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1572807 Title: /bin/nano:*** Error in `nano': double free or corruption (!prev): ADDR *** Status in nano package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nano. This problem was most recently seen with version 2.5.3-2, the problem page at https://errors.ubuntu.com/problem/7dd7f74a72fca06513544d8af66b623efa15b26c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1572807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
