Segfault in v.6.1 Socket buffer overflow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cyphesis |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Program received signal SIGPIPE, Broken pipe.
0x00007ffff4bba282 in send () from /lib/x86_
(gdb) bt
#0 0x00007ffff4bba282 in send () from /lib/x86_
#1 0x00007ffff612b957 in stream_
at ../../skstream/
#2 0x00007ffff612b66f in socketbuf::sync (this=<optimized out>)
at ../../skstream/
#3 0x00007ffff536d32e in std::ostream:
from /usr/lib/
#4 0x000000000047d781 in CommClientFacto
at ../../server/
#5 0x000000000048a3ec in CommStreamListe
this=0x2dcc010, asockfd=18, address=<optimized out>)
at ../../server/
#6 0x000000000047ebe0 in CommTCPListener
at ../../server/
#7 0x000000000048a06a in CommStreamListe
this=<optimized out>) at ../../server/
#8 0x00000000004882ef in CommServer::poll (this=0xa38ed0,
busy=<optimized out>) at ../../server/
#9 0x0000000000413ced in main (argc=<optimized out>, argv=<optimized out>)
at ../../server/
This isn't a segfault, it's SEGPIPE, which just indicates that a socket has broken. This isn't fatal in any way, and more of a nuisance. Cyphesis will keep on running just fine (if you're in gdb just execute "continue").
You'll often get this when running a local server and starting up Ember, since Ember will just open up the socket to see if the server is alive, and then brusquely close it. Ember should behave in a better way, but since it doesn't cause any error I haven't put any effort into fixing it.