1.
[root@pbx sipXecs]# gdb sipxhomer
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-56.el6)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/libexec/sipXecs/sipxhomer...Reading symbols
from /usr/lib/debug/usr/libexec/sipXecs/sipxhomer.debug...done.
done.
2.
(gdb) run --log-file /var/log/sipxpbx/sipxhomer.log --config-file
/etc/sipxpbx/sipxhomer.ini --pid-file /var/run/sipxpbx/sipxhomer.pid
Starting program: /usr/libexec/sipXecs/sipxhomer --log-file
/var/log/sipxpbx/sipxhomer.log --config-file
/etc/sipxpbx/sipxhomer.ini --pid-file /var/run/sipxpbx/sipxhomer.pid
[Thread debugging using libthread_db enabled]
sipxhomer version 1.0 - All Rights Reserved.
[New Thread 0xb7fe4b70 (LWP 18509)]
[Thread 0xb7fe4b70 (LWP 18509) exited]
Program received signal SIGSEGV, Segmentation fault.
__strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:52
52 movdqu (%edi), %xmm1
Missing separate debuginfos, use: debuginfo-install
boost-date-time-1.41.0-11.el6_1.2.i686
boost-filesystem-1.41.0-11.el6_1.2.i686
boost-program-options-1.41.0-11.el6_1.2.i686
boost-regex-1.41.0-11.el6_1.2.i686 boost-system-1.41.0-11.el6_1.2.i686
boost-thread-1.41.0-11.el6_1.2.i686 keyutils-libs-1.4-4.el6.i686
krb5-libs-1.9-33.el6_3.2.i686 libcom_err-1.41.12-12.el6.i686
libgcc-4.4.6-4.el6.i686 libicu-4.2.1-9.1.el6_2.i686
libselinux-2.0.94-5.3.el6.i686 libstdc++-4.4.6-4.el6.i686
libtool-ltdl-2.2.6-15.5.el6.i686 libuuid-2.17.2-12.7.el6.i686
mongodb-2.0.2-99.el6.i686 mysql-connector-odbc-5.1.5r1144-7.el6.i686
mysql-libs-5.1.61-4.el6.i686 nss-softokn-freebl-3.12.9-11.el6.i686
openssl-1.0.0-25.el6_3.1.i686 pcre-7.8-4.el6.i686
resiprocate-1.8.4-1.i686 sipxcommserverlib-4.6.0-383.g86d67.i686
sipxportlib-4.6.0-383.g86d67.i686 sipxsqa-4.6.0-383.g86d67.i686
sipxtacklib-4.6.0-383.g86d67.i686 unixODBC-2.2.14-11.el6.i686
zeromq-2.1.9-1.el6.i686 zlib-1.2.3-27.el6.i686
3.
(gdb) bt
#0 __strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:52
#1 0x001e935b in SQLDriverConnect () from /usr/lib/libmyodbc5-5.1.5.so
#2 0x0809c129 in HEPDao::connect (this=0xbffff5b8, connection=
Traceback (most recent call last):
File "/usr/lib/../share/gdb/python/libstdcxx/v6/printers.py", line
558, in to_string
return self.val['_M_dataplus']['_M_p'].lazy_string (length = len)
RuntimeError: Cannot access memory at address 0xfff5
) at HEPDao.cpp:61
#3 0x0806d0ea in main (argc=7, argv=0xbffff724) at main.cpp:40
"That's all she wrote!"
On Thu, Sep 6, 2012 at 11:13 AM, Tony Graziano
<[email protected]> wrote:
> I did. That was the entire output.
>
> On Thu, Sep 6, 2012 at 11:10 AM, George Niculae <[email protected]> wrote:
>> On Thu, Sep 6, 2012 at 6:07 PM, Tony Graziano
>> <[email protected]> wrote:
>>> it is, must have been in the wrong directory after all. sipxhomer is there.
>>>
>>> [Thread debugging using libthread_db enabled]
>>>
>>> sipxhomer version 1.0 - All Rights Reserved.
>>>
>>> [New Thread 0xb7fe4b70 (LWP 17738)]
>>> [Thread 0xb7fe4b70 (LWP 17738) exited]
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> __strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:52
>>> 52 movdqu (%edi), %xmm1
>>> Missing separate debuginfos, use: debuginfo-install
>>> boost-date-time-1.41.0-11.el6_1.2.i686
>>> boost-filesystem-1.41.0-11.el6_1.2.i686
>>> boost-program-options-1.41.0-11.el6_1.2.i686
>>> boost-regex-1.41.0-11.el6_1.2.i686 boost-system-1.41.0-11.el6_1.2.i686
>>> boost-thread-1.41.0-11.el6_1.2.i686 keyutils-libs-1.4-4.el6.i686
>>> krb5-libs-1.9-33.el6_3.2.i686 libcom_err-1.41.12-12.el6.i686
>>> libgcc-4.4.6-4.el6.i686 libicu-4.2.1-9.1.el6_2.i686
>>> libselinux-2.0.94-5.3.el6.i686 libstdc++-4.4.6-4.el6.i686
>>> libtool-ltdl-2.2.6-15.5.el6.i686 libuuid-2.17.2-12.7.el6.i686
>>> mongodb-2.0.2-99.el6.i686 mysql-connector-odbc-5.1.5r1144-7.el6.i686
>>> mysql-libs-5.1.61-4.el6.i686 nss-softokn-freebl-3.12.9-11.el6.i686
>>> openssl-1.0.0-25.el6_3.1.i686 pcre-7.8-4.el6.i686
>>> resiprocate-1.8.4-1.i686 sipxcommserverlib-4.6.0-383.g86d67.i686
>>> sipxportlib-4.6.0-383.g86d67.i686 sipxsqa-4.6.0-383.g86d67.i686
>>> sipxtacklib-4.6.0-383.g86d67.i686 unixODBC-2.2.14-11.el6.i686
>>> zeromq-2.1.9-1.el6.i686 zlib-1.2.3-27.el6.i686
>>> (gdb) bt
>>> #0 __strlen_sse2_bsf () at
>>> ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:52
>>> #1 0x001e935b in SQLDriverConnect () from /usr/lib/libmyodbc5-5.1.5.so
>>> #2 0x0809c129 in HEPDao::connect (this=0xbffff5b8, connection=
>>> Traceback (most recent call last):
>>> File "/usr/lib/../share/gdb/python/libstdcxx/v6/printers.py", line
>>> 558, in to_string
>>> return self.val['_M_dataplus']['_M_p'].lazy_string (length = len)
>>> RuntimeError: Cannot access memory at address 0xfff5
>>> ) at HEPDao.cpp:61
>>> #3 0x0806d0ea in main (argc=7, argv=0xbffff724) at main.cpp:40
>>>
>>> There was no logging to a file, but the output was very short. Is this
>>> sufficient?
>>>
>>
>> After this steps where it exists, run
>>
>> bt
>>
>> and post back the output
>>
>> George
>> _______________________________________________
>> sipx-dev mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
>
>
> --
> ~~~~~~~~~~~~~~~~~~
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: [email protected]
> Fax: 434.465.6833
> ~~~~~~~~~~~~~~~~~~
> Linked-In Profile:
> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> Ask about our Internet Fax services!
> ~~~~~~~~~~~~~~~~~~
>
> Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013!
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~
Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013!
--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
