[Xapian-tickets] [Xapian] #592: (crash) ChertTable::add_item_to_block on a seemingly corrupted block

[Xapian]

#592: (crash) ChertTable::add_item_to_block on a seemingly corrupted block
---------------------------+------------------------------------------------
 Reporter:  static-void    |       Owner:  olly 
     Type:  defect         |      Status:  new  
 Priority:  normal         |   Milestone:       
Component:  Backend-Chert  |     Version:  1.2.5
 Severity:  normal         |    Keywords:       
Blockedby:                 |    Platform:  Linux
 Blocking:                 |  
---------------------------+------------------------------------------------

Comment(by static-void):

 Although I haven't seen the inside of Xapian before starting this diag, I
 guess DIR_END(p) should not ever be zero. Could it be database file
 corruption?

 I've got an idea how I can find the primary reason for this:
  * compile libxapian with the usual debug options and -fno-inline (to stop
 setint2 being inline)
  * breakpoint setint2(unsigned char *p, int c, int x) with condition c=9
 and x=0 (if that's possible)

 Is it worth it, i.e. can it be caught like this? Or should I just not
 waste time and delete the index file?

-- 
Ticket URL: <http://trac.xapian.org/ticket/592#comment:1>
Xapian <http://xapian.org/>
Xapian