search for: saha048

Hi All, I'm facing a problem in icecast relay machines. I'm seeing frequently that some of the relay machines are crashing and generates core dump but the reason for the crash is not clear from the trace of the core. Here is how the gdb trace looks like: (gdb) bt #0 0xffffe435 in __kernel_vsyscall () #1 0xf742c607 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0xf742fa33 in

Hi, I am new to Icecast open source project and I would like to contribute into this open source project. Looking for some kind of guidelines how to get started and where to browse for the open issues or features to look into. Any kind of help would be much appreciated. - Sourav Saha -------------- next part -------------- An HTML attachment was scrubbed... URL:

Thanks Philipp. I agree with you, this looks like some buffer overrun issue. I know I'm using a very old version of icecast software but still I am asking is there any kind of workaround to this problem apart from upgrading the icecast version (which is the last option). Running Valgrind may help to capture the root cause, any thoughts? BTW what's the latest stable version of icecast?

Hi All, I'm facing a problem in icecast relay machines. I'm seeing frequently that some of the relay machines are crashing and generates core dump but the reason for the crash is not clear from the trace of the core. Here is how the gdb trace looks like: (gdb) bt #0 0xffffe435 in __kernel_vsyscall () #1 0xf742c607 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0xf742fa33 in

Hi All, I'm facing a problem in icecast relay machines. I'm seeing frequently that some of the relay machines are crashing and generates core dump but the reason for the crash is not clear from the trace of the core. Here is how the gdb trace looks like: (gdb) bt #0 0xffffe435 in __kernel_vsyscall () #1 0xf742c607 in raise () from /lib/i386-linux-gnu/libc.so.6 #2 0xf742fa33 in

Hi, I am using icecast 2.3.2 and I'm not in position to upgrade the version right away since this version is already in use. Please let me know if you need any additional details for this issue. Nevertheless if there is any potential fix has gone towards this part of code in later versions, I can just use that patch in my current code base. Also I'll try to catch up on Freenode but