bugXlog - Bugs: bug #29122, Adif file gets truncated/corrupted...

 
 

bug #29122: Adif file gets truncated/corrupted if one record has non-ham frequency

Submitted by:  Pierfrancesco Caci <ik5pvx>
Submitted on:  Mon 08 Mar 2010 08:25:58 PM UTC  
 
Category: ADIFSeverity: 3 - Normal
Item Group: NoneStatus: Fixed
Privacy: PublicAssigned to: Joop Stakenborg <pa4tu>
Open/Closed: ClosedRelease: 2.0

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Tue 15 Feb 2011 09:00:10 PM UTC, comment #4:

Okay, I can reproduce it by selecting "convert frequency to band" for the EXPORT/ADIF options in the "dialogs and windows" dialog. I will add a fix in 2.0.5.

Thanks!

Joop Stakenborg <pa4tu>
Project AdministratorIn charge of this item.
Tue 15 Feb 2011 07:43:15 PM UTC, comment #3:

Thanks Pf!

I can't reproduce this, but will have a look at the ADIF functions and will get back to you.

Joop Stakenborg <pa4tu>
Project AdministratorIn charge of this item.
Tue 15 Feb 2011 07:35:31 PM UTC, comment #2:

Hello Joop,
I can still see this with 2.0.4.
When trying to export the example.xlog file to example.adif, I get an empty file.

ik5pvx@penny:~/.xlog $ ls -las example.*

  1. -rw-r--r-- 1 ik5pvx ik5pvx 0 Feb 15 20:31 example.adif

8 -rw-r--r-- 1 ik5pvx ik5pvx 4225 Feb 15 20:12 example.xlog
8 -rw-r--r-- 1 ik5pvx ik5pvx 4225 Feb 15 20:31 example.xlog.backup

Pf

Pierfrancesco Caci <ik5pvx>
Tue 15 Feb 2011 06:36:56 PM UTC, comment #1:

Hello Pf,

checked you report with xlog-2.0.4 and the provided example.xlog, I see no file corruption.

Do you still see this problem with the latest xlog?

Joop Stakenborg <pa4tu>
Project AdministratorIn charge of this item.
Mon 08 Mar 2010 08:25:58 PM UTC, original submission:

One user reported getting a truncated adif file while exporting his log. After a bit of cutting his log in smaller pieces, I was able to find that he mistyped a frequency in a QSO record, placing it outside the 2m ham band. This makes the adif export function return unexpectedly, leaving a corrupted or even an empty adif file. Xlog itself does not crash.

Attached, sample extract from his log with wrong record.

xlog 2.0.3

Pf

Pierfrancesco Caci <ik5pvx>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #19887:  example.xlog added by ik5pvx (4KiB - text/x-xlog - look for the W1ZSA record)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by pa4tu (Updated the item)
  • -unavailable- added by ik5pvx (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 7 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 23 Feb 2011 08:08:32 PM UTCpa4tuStatusConfirmed=>Fixed
      Open/ClosedOpen=>Closed
    Tue 15 Feb 2011 08:29:12 PM UTCpa4tuStatusNeed Info=>Confirmed
    Tue 15 Feb 2011 06:34:21 PM UTCpa4tuStatusNone=>Need Info
      Assigned toNone=>pa4tu
      ReleaseNone=>2.0
    Mon 08 Mar 2010 08:25:58 PM UTCik5pvxAttached File-=>Added example.xlog, #19887

    Back to the top


    Powered by Savane 3.1-cleanup1