Public bug reported:
* Description:Ubuntu 14.10
Release: 14.10
* 0.5.7-3ubuntu1
* I expected that application linked with msgpack3 passed all valgrind memory
checks
* undefined behaviour in msgpack::unpacker::next - malloc/delete
===
In 0.5
Hello! here you are: https://github.com/shilkin/msgpack_0.5.7-bug-1469090
Step-by-step instructions to reproduce this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469090
Title:
undefined
Knock-knock! Please, give me any feedback?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469090
Title:
undefined behaviour in msgpack::unpacker::next - malloc/delete
To manage notifications about
+
+ ===
+
+ https://github.com/shilkin/msgpack_0.5.7-bug-1469090
+ Step-by-step instructions to reproduce this bug.
===
In 0.5.7 version msgpack::unpacker holds zone in std::aut_ptr.
In msgpack::unpacker::next on line 234 we can see
