[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 olly):

 We shouldn't really end up actually calling memmove with a bad size in
 this case.  I'll add a sanity check.

 Does xapian-check report the database as corrupt?

 If so, the more interesting question is how it got that way, rather than
 how we end up getting to where the crash is in the code.  That's likely to
 be much easy to understand if you can see it happening, rather than just
 the aftermath.

 If xapian-check is happy, it's definitely worth investigating.

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