Menu

#77 seg fault exporting with mdb-export

open
nobody
libmdb (15)
5
2005-03-22
2005-03-22
Anonymous
No

Exporting a table from a JET4 mdb with the latest CVS
as of 2005-03-21:

Program received signal SIGSEGV, Segmentation fault.
0x00eca271 in mdb_crack_row (table=0x9422ef8,
row_start=2399, row_end=-1074284864, fields=0xbff7b6c0)
at write.c:226
226 fields[i].is_null =
nullmask[byte_num] & (1 << bit_num) ? 0 : 1;
(gdb) backtrace
#0 0x00eca271 in mdb_crack_row (table=0x9422ef8,
row_start=2399, row_end=-1074284864, fields=0xbff7b6c0)
at write.c:226
#1 0x00ec7653 in mdb_read_row (table=0x9422ef8,
row=15) at data.c:263
#2 0x00ec78a7 in mdb_fetch_row (table=0x9422ef8) at
data.c:397
#3 0x08048e9e in main (argc=155336168,
argv=0xbff7cfe4) at mdb-export.c:186

I rebuilt setting MDB_DEBUG to 1 in mdbtools.h and set
MDBOPTS to debug_all
Row 12 bytes 2615 to -46538 [lookup] [delflag]
Row 13 bytes 2615 to -46538 [lookup] [delflag]
Row 14 bytes 2516 to 2614
sarg test passed row 14
bitmask_sz 2
row_var_cols 6
row_fixed_cols 4

Row 15 bytes 2399 to -30253 [lookup]
bitmask_sz 2
row_var_cols -1
row_fixed_cols 11

the only pattern I see is that [delflag] is not set for
Row 15

Note: the seg fault didn't occur using the 2004-06-18
version (although text was truncated in memo fields)

Discussion


Log in to post a comment.