Program crash - two Situations

3 posts / 0 new
Last post
DM5JH
Program crash - two Situations

Hello,

I've updated to version 1.3 (64bit) on Suse 11.3.

Currently I've two situations, where cqrlog crashes.

1. Normal program termination (clicking the 'Quit Program' btoon on the QSO-window), the programms seems to exit normally, but I#am always getting the following error messages (when I start it from a console):


Saving ini file to database
Closing BandMap window
Closing DXCluster window
Closing TRXControl window
Closing GrayLine window
Closing dDXCC
Closing dData
/home/cfjh/.config/cqrlog/database/bastau.pid
Command:
kill 9922
120212 22:22:33 [Note] /usr/sbin/mysqld: Normal shutdown

120212 22:22:33 InnoDB: Starting shutdown...
Closing ini file ...
An unhandled exception occurred at $000000000051C3C3 :
EAccessViolation :
$000000000051C3C3
$00000000006934D9

120212 22:22:37 InnoDB: Shutdown completed; log sequence number 0 44243
120212 22:22:37 [Note] /usr/sbin/mysqld: Shutdown complete

[2]+ Exit 217 cqrlog

2. After importing a QSO-list from adif format and editing a QSO (with invalid callsign, here "TEST"), cqrlog crashes immeaditly, when I click on the 'IOTA' combobox:


cfjh@bastau:~> cqrlog &
[1] 9718
cfjh@bastau:~> Loading libssl: /usr/lib64/libssl.so
Loading libcrypto: /usr/lib64/libcrypto.so
Loading libmysqlclient: /usr/lib64/libmysqlclient.so.16
Loaded 49721 LoTW users
Loaded 58346 eQSL users
/home/cfjh/.config/cqrlog/database/bastau.pid
Command:
kill 9668
120212 22:16:41 [Note] /usr/sbin/mysqld: Normal shutdown

120212 22:16:41 InnoDB: Starting shutdown...
120212 22:16:41 InnoDB: Shutdown completed; log sequence number 0 44243
120212 22:16:41 [Note] /usr/sbin/mysqld: Shutdown complete

*
User home directory: /home/cfjh/
Program home directory: /home/cfjh/.config/cqrlog/
Data directory: /home/cfjh/.config/cqrlog/database/
Memebers directory: /usr/share/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
*
/usr/sbin/mysqld --defaults-file=/home/cfjh/.config/cqrlog/database/my.cnf --default-storage-engine=MyISAM --datadir=/home/cfjh/.config/cqrlog/database/ --socket=/home/cfjh/.config/cqrlog/database/sock --skip-grant-tables --port=64000 --key_buffer_size=32M --key_buffer_size=4096K
120212 22:16:44 InnoDB: Initializing buffer pool, size = 8.0M
120212 22:16:44 InnoDB: Completed initialization of buffer pool
120212 22:16:44 InnoDB: Started; log sequence number 0 44243
120212 22:16:44 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
120212 22:16:44 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
120212 22:16:44 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.57' socket: '/home/cfjh/.config/cqrlog/database/sock' port: 64000 SUSE MySQL RPM
select * from tables where table_schema = 'cqrlog_common'

SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nr

use cqrlog003

use cqrlog003

SELECT * FROM cqrlog_config

select * from db_version

SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF

SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF

In inicializerig
Model:1
Port:/dev/ttyS0
Baudrate:9600
Databits:8
StopBits:1
Handshake:None
Parity:None
DTR:OFF
RTS:OFF
Poll:500
rig:rig_init called
rig: loading backend dummy
dummy: _init called
rig_register (1)
rig_register (2)
dummy_init called
in tRig.Close
rig:rig_close called
Loading window size a position (height|width|top|left):651|807|20|20
Section:frmQSODetails
Loading window size a position (frmQSODetails) (height|width|top|left):210|266|20|20
CW init
SunDelta: 1.000000000000000000E+00
SELECT * FROM profiles WHERE visible > 0 ORDER BY nr

SELECT * FROM profiles WHERE visible > 0 ORDER BY nr

2012-02-12 21:16:49
select * from view_cqrlog_main_by_qsodate LIMIT 500 OFFSET 0

LoadForm: frmMain
Column:QSODATE:TRUE
Column:TIME_ON:TRUE
Column:TIME_OFF:FALSE
Column:CALLSIGN:TRUE
Column:MODE:TRUE
Column:FREQ:TRUE
Column:RST_S:TRUE
Column:RST_R:TRUE
Column:NAME:TRUE
Column:QTH:TRUE
Column:QSL_S:TRUE
Column:QSL_R:TRUE
Column:QSL_VIA:FALSE
Column:LOC:FALSE
Column:MY_LOC:FALSE
Column:IOTA:FALSE
Column:AWARD:FALSE
Column:COUNTY:FALSE
Column:PWR:FALSE
Column:DXCC_REF:FALSE
Column:REMARKS:FALSE
Column:WAZ:FALSE
Column:ITU:FALSE
Column:STATE:FALSE
Column:LOTW_QSLSDATE:FALSE
Column:LOTW_QSLRDATE:FALSE
Column:LOTW_QSLS:FALSE
Column:LOTW_QSLR:FALSE
Column:CONT:FALSE
Column:QSLS_DATE:FALSE
Column:QSLR_DATE:FALSE
Column:EQSL_QSL_SENT:FALSE
Column:EQSL_QSLSDATE:FALSE
Column:EQSL_QSL_RCVD:FALSE
Column:EQSL_QSLRDATE:FALSE
Column:QSLR:FALSE
SELECT COUNT(*) FROM cqrlog_main

select count(*) from (select distinct adif from cqrlog_main where adif <> 0 and (adif not in (2,8,19,23,25,26,28,30,39,42,44,55,57,58,59,67,68,81,85,93,101,102,113,115,119,127,128,139,154,155,164,178,183,184,186,193,193,194,196,198,200,208,210,218,220,226,228,229,231,243,244,255,258,261,264,267,268,271,307,488,493))) as foo

select count(*) from (select distinct dxcc_id.dxcc_ref from dxcc_id left join cqrlog_main on dxcc_id.adif = cqrlog_main.adif WHERE cqrlog_main.adif<>0 and (dxcc_ref NOT LIKE '%*') AND (qsl_r = 'Q')) as foo

SELECT * FROM profiles WHERE visible > 0 ORDER BY nr

2012-02-12 21:16:55
SELECT * FROM profiles ORDER BY nr

NEnalezeno - U1RC
adif:0
SELECT * FROM view_cqrlog_main_by_qsodate WHERE callsign = 'TEST' ORDER BY qsodate,time_on

LoadForm: frmNewQSO
select * from cqrlog_common.qslmgr where (callsign = 'TEST') and (fromDate <= '2012-02-12') order by fromDate

GetIOTAForDXCC
The program 'cqrlog' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 128705 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

[1]+ Exit 1 cqrlog
cfjh@bastau:~>

Jürgen
www.wetterstation-porta.info

ok2cqr
ok2cqr's picture
Re: Program crash - two Situations

Hello Jürgen,

I know about the first crash but not sure where is the problem. It is somewhere in releasing objects from memory but not sure where.

The second crash is interesting. Could you please send me adif file you imported and callsign which caused the problem? Thank you!

73 Petr, OK2CQR

DM5JH
Hello, here is the exported

Hello,

here is the exported data (one qso). But the crach can be caused easylier:
- enter a new qso
- enter an invalid call sign (for example "TEST")
- click on the 'IOTA'-combo box
I think the problem occours, when the IOTA list is empty.

Jürgen
www.wetterstation-porta.info

------------->8=================
2.2.1
ADIF export from CQRLOG for Linux version 1.3.0
Copyright (C) 2012 by Petr, OK2CQR and Martin, OK1RR

Internet: http://www.cqrlog.com

201202252209TESTCW7.02540M599599TestTesthausenNN