Closed v6 closed 8 years ago
can you get a bt?
// , Whether or not I can get a "bt" depends on what a "bt" is, of course. I can try, though.
// ,
NVM, figured it out.
I'll run it similarly to this until I get another segfault: https://github.com/notsecure/uTox/issues/936#issuecomment-87349335
I'll run it similarly to this until I get another segfault: #936 (comment)
then please paste the output of bt
you get from gdb
.
if you could start it with gdb
and then make it crash, then type bt
into gdb, and post the output to a gist... that would be SUPER awesome...
The same here, I noticed it happens when I send big images, the select square also bug. I'm on OpenBSD, running on commit d16f53912b161893431fd16025af94d4d8a14f53 There is a bt: FileTransfer: Starting outgoing image to friend 1. FileTransfer: Friend (1) has resumed file (1) Friend Typing (1): 0 Friend Typing (1): 1
Program received signal SIGSEGV, Segmentation fault. [Switching to thread 1010942] 0x0000192ec4cbb73f in handle_packet_connection () from /usr/local/lib/libtoxcore.so.0.0 (gdb) bt
) at /usr/src/lib/librthread/rthread.c:145
maybe its not compiled with -debug
So it is a toxcore problem? Wondering if any of these lasts commits solves: https://github.com/irungentoo/toxcore/commits/master
Probably solved with last toxcore, @v6 test it
// , @henriqueleng, I just tested it. I can confirm that this bug was fixed with the latest toxcore. However, I'm curious what could have caused this bug.
// , I'm getting a segfault on some sort of resize panic or race condition when I send a screenshot over a certain size in uTox 0.3.2 on Linux.
$ uname -a
3.16.0-43-generic #58-Ubuntu SMP Fri Jun 19 11:04:02 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Full log of entire program run: