-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault #28
Comments
FYI, same bug, also on Ubuntu 14.04 (which we just upgraded to one one of our cluster servers). Identical script / different binary works on 12.04. Had to recompile with newer opal (3.10.10) line 13: 28400 Segmentation fault /usr/bin/timeout 40 /usr/local/bin/sipcmd -u 1980 -c XXXX -P sip -w 10.99.0.54 -x "w13000;c7071;w250;d#;w250;v$SONG;h;" -o sip.log
|
After digging through a core dump, the issue seems to be in channels.cpp:460, with a bug likely in libopal's CollectAverage. Commenting out that line seems to have solved the immediate segfault issue, and that's the end of the problem for me. I haven't dug into the internals enough to know what the long term effects of this change are, but since our use of sipcmd is relatively simple and straightforward, I'm stopping there. FYI for others. |
as per discussion here tmakkonen#28
I am not sure if commenting out CollectAverage() is the correct thing to do. After all, it probably was there for a reason. But admittedly, the code that invokes CollectAverage() looks extremely strange. I would suggest the following patch. At least intuitively, that looks more reasonable. But somebody more familiar with Opal and with sipcmd should probably double-check:
|
Running this command will more likely crash with a segfault.
$ ./sipcmd -P sip -u 1183 -c ***** -w 192.168.20.240 -x "c1234;ws2000;d9876;w1000;h" -o ./opal.log
The opal.log has no hints for me, and the segfault will happen about 80% of the time.
Using Ubuntu 14.04 x86_64
The text was updated successfully, but these errors were encountered: