On Tue, 11 Jun 2013 17:28:28 +1200 David Frampton <[email protected]> wrote:
it looks strange. i can suggest to rebuild enet with -O0 -g and try to run your app with valgrind: it may trace the origins of this pointer. note that valgrind can 'hide' crash conditions (i.e. app can go past the 'crash point'), so be careful and watch valgrind logs (--log-file=xxx) btw: what version of enet are you using? is it stock 1.3.7 or 1.3.8? also, make sure you aren't accidentally free/reuse either ENetPacket or it's 'data' field after passing it to enet_peer_send.
signature.asc
Description: PGP signature
_______________________________________________ ENet-discuss mailing list [email protected] http://lists.cubik.org/mailman/listinfo/enet-discuss
