14 Nov
2010
14 Nov
'10
9:53 p.m.
Hi Stuart,
On Sun, Nov 14, 2010 at 08:35:33PM +0000, Stuart Baggs wrote:
SET ATTR NACK CAUSE=Message cannot be performed
This should not happen. I would recommend recording a pcap file (with
wireshark) and looking at the exact OML message that has caused this problem.
*** stack smashing detected ***:
/usr/local/sbin/bsc_hack terminated
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0x2eaed8]
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0x2eae90]
/usr/local/sbin/bsc_hack[0x8060f43]
/usr/local/sbin/bsc_hack[0x805cca0]
/usr/local/sbin/bsc_hack[0x80663d9]
/usr/local/sbin/bsc_hack[0x80752a2]
/usr/local/lib/libosmocore.so.0(bsc_select_main+0x14b)[0x88e51b]
/usr/local/sbin/bsc_hack[0x804c0a6]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x220b56]
/usr/local/sbin/bsc_hack[0x804bbb1]
A backtrace without the symbol names is not particularly useful.
can you actually provide a gdb backtrace from this? As we don't have your
exact binaries for libosmocore + bsc_hack and your generated core file, we
cannot produce this ourselves.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)