basicScandal / raft

Automatically exported from code.google.com/p/raft

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Segfault while attempting to view

GoogleCodeExporter opened this issue · comments

What steps will reproduce the problem?

See attached.

Console output:

$ python2.6  raft.pyw 
('CONSOLE--->', '[object Object]')
('DEBUG', 'SiteMapThread started...')
('DEBUG', 'ResponsesThread started...')
('DEBUG', 'AnalyzerThread started...')
('DEBUG', 'DomFuzzerThread started...')
('DEBUG', 'SpiderThread started...')
QPainter::end: Painter ended with 2 saved states
('DEBUG', 'Database temp.raftdb attached')
starting populating responses
finished populating responses
QTreeView::rowsInserted internal representation of the model has been 
corrupted, resetting. 
OpenOffice path before fixup is '/usr/lib/ooo'
OpenOffice path is '/usr/lib/ooo'
OpenOffice path before fixup is '/usr/lib/ooo'
OpenOffice path is '/usr/lib/ooo'

(process:7915): GLib-GObject-CRITICAL **: gtype.c:2706: You forgot to call 
g_type_init()

(process:7915): GLib-CRITICAL **: g_once_init_leave: assertion 
`initialization_value != 0' failed

(process:7915): GLib-GObject-CRITICAL **: g_object_new: assertion 
`G_TYPE_IS_OBJECT (object_type)' failed
Segmentation fault


Using raft just checked out from svn, revision: 39

Running:

Linux localhost 2.6.33.7-desktop586-2mnb #1 SMP Mon Sep 20 18:19:58 UTC 2010 
i686 i686 i386 GNU/Linux

Mandriva 2010.2

Original issue reported on code.google.com by justin.s...@gmail.com on 8 Aug 2011 at 5:53

Attachments:

I cannot reproduce your crash.

Could you send a copy of either the results you imported, or the raft save file 
(.raftdb)?  I expect that there's some special character or encoding in the 
things you analyzed that we didn't account for and this is what caused the 
error.

If narrowing it down to a single result still causes the crash, that would also 
be helpful to me.  

Thanks!

Original comment by justinen...@gmail.com on 8 Aug 2011 at 8:11

Unfortunately, it looks like it is not a single result. In the main "Responses" 
view, nearly any response I clicked on to view would cause a crash.

Original comment by justin.s...@gmail.com on 8 Aug 2011 at 10:44

Attachments: