Re: [Xlog-discussion] Problem using the remote logging capabilities with KPSK

[Joop Stakenborg]

Op donderdag 26-06-2008 om 18:36 uur [tijdzone -0500], schreef Joshua
Wood:
> Hi,
> I've built xlog 1.7 on Slamd64 -current (call it 12.1 if you'd like.)
> I'm wanting to use it this weekend for Field Day.  The problem I'm
> running into is, xlog segfaults when I send it a qso from KPSK.  I've
> included a backtrace on the segfault below:
> 
> (gdb) backtrace
> #0  0x000000000043f7d5 in addtolog_or_qsoframe ()
> #1  0x0000000000440ef9 in remote_entry ()
> #2  0x00002abe9fda802b in ?? () from /usr/lib64/libglib-2.0.so.0
> #3  0x00002abe9fda78d4 in g_main_context_dispatch ()
> from /usr/lib64/libglib-2.0.so.0
> #4  0x00002abe9fdaabbd in ?? () from /usr/lib64/libglib-2.0.so.0
> #5  0x00002abe9fdaaeb7 in g_main_loop_run ()
> from /usr/lib64/libglib-2.0.so.0
> #6  0x00002abe9e52b853 in gtk_main ()
> from /usr/lib64/libgtk-x11-2.0.so.0
> #7  0x000000000040e159 in main ()
> 
> 
> Any ideas on what could be causing this? 
> 

Hi Joshua,

I have downloaded kpsk-1.2rc2, but it won't compile on my system. I have
checked the kpsk mailing lists to see if there is any activity, but they
only seem to contain spam.

I would like to suggest that you use gmfsk (works fine with xlog) or any
of the other digital modem programs. Since my development time is
limited I am ruluctant in supporting dead projects like kpsk.

Also, backtraces don't help me much without line numbers. After
compilation, start xlog from the xlog source tree when using gdb. 'gdb
src/xlog'. It would be nice to seen that the content of the message
buffer is in addtolog_or_qsoframe()... After the crash type: 'p entry'.

> Thanks,
> JK

Joop PG4I