Menu
▾
▴
[Cscope-devel] [ cscope-Bugs-1665751 ] cscope-15.5 aborts on startup on fc6
|
From: SourceForge.net <no...@so...> - 2007-02-22 19:44:33
|
Bugs item #1665751, was opened at 2007-02-22 02:40 Message generated for change (Comment added) made by broeker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104664&aid=1665751&group_id=4664 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: cscope-15.5 aborts on startup on fc6 Initial Comment: Hi, I have an FC6 machine on which I installed cscope-15.5 binary. Cscope aborts on startup with the following error: Find this C symbol: Find this global definition: Find functions called by this function: Find functions calling this function: Find this text string: Change this text string: Find this egrep pattern: Find this file: Find files #including this file: Find all function definitions: Find all symbol assignments: cscope: invlib.c:563: invopen: Assertion `invcntl->param.sizeblk == sizeof(t_logicalblk)' failed. Abort I download 15.6 and the result is same. I compiled 15.6 with the assert commented out. Things seem to work fine with the assert removed. Since I don't know the purpose of I the assert, thought I'd report it. Thanks. Bhasker. ---------------------------------------------------------------------- >Comment By: Hans-Bernhard Broeker (broeker) Date: 2007-02-22 20:44 Message: Logged In: YES user_id=27517 Originator: NO The most likely explanation for that assert() to fail is that your machine's compiler is using some struct layout that invlib didn't expect. That assert() is an important sanity check of the inverted index file format. Which means that, as a workaround, you could just leave out the -q option. All that set aside: we need more details. I'll venture a guess that your "FC6 machine" (no further specifications) actually runs the 64-bit edition of FC6. That still wouldn't explain why I don't remember anything like that happening on my own 64-bit Linux box, but it'd be a first hint. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=104664&aid=1665751&group_id=4664 |