send_packets: Avoid crashing on errors in sendto call. #74
Conversation
If sendto() returned an error, pthread_cleanup_pop() was not called before return, resulting in a segfault on my CentOS 5.x platform. Next, I need to look into why sendto is failing on CentOS 5.x but not on other platforms.
|
I also now see that this change wouldn't be necessary if Pull Request #57 is merged since it drops the use of the pthread_cleanup_push/pop calls. |
|
Yes. I had the same problem with the pthread_cleanup stuff (on Ubuntu), so I had to hack it out too. |
|
You wouldn't know what the issue with sendto/raw sockets is would you? I think there must be some difference in glib on the platforms since just changing the kernel out on Centos 5.x to 3.2.x from the stock 2.6.18 didn't fix the "invalid arguement" error. But running under CentOS 6.x and Debian 6.0 did not have a problem. I have the same failure running ossobv:wjd-no_root_for_pcap. |
|
No, that I don't. The sendto issues I had were my own doing when I was hacking on the non-root play. |
wdoekes
force-pushed
the
master
branch
2 times, most recently
from
bebdf78
to
8923379
Compare
vodik
force-pushed
the
master
branch
3 times, most recently
from
231edd4
to
341fb97
Compare
|
I was seeing the same segfault issue, randomly after 30-70 calls. I'm running in two dockers communicating to each other over a bridged network. dmesg shows: And the error I see in sipp is: Sipp was exiting status code 139. I can reproduce with great regularity, let me know if I can provide any more debugging output. I created a patch for 2.5.1 since this branch has merge conflicts, patch attached. |
|
Fixed in recent commits |
If sendto() returned an error, pthread_cleanup_pop() was not called before
return, resulting in a segfault on my CentOS 5.x platform.
Next, I need to look into why sendto is failing on CentOS 5.x but not on other
platforms.