Bug 11590 - Segmentation fault on second refresh of the archive list
: Segmentation fault on second refresh of the archive list
Status: RESOLVED FIXED
Product: Evopedia
General
: unspecified
: x86 Ubuntu
: Unspecified normal (vote)
: ---
Assigned To: christian
: general
:
:
:
:
  Show dependency tree
 
Reported: 2010-11-18 16:09 UTC by mossroy
Modified: 2010-11-21 18:13 UTC (History)
0 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description mossroy (reporter) 2010-11-18 16:09:05 UTC
SOFTWARE VERSION:
0.4.2 (from git, probably not the final one), compiled on 64-bit Ubuntu 10.04.1

EXACT STEPS LEADING TO PROBLEM: 
1. Open evopedia, and go to the Archives window. The current local archives are
listed (I currently have 3 of them : fr, en and small)
2. In the menu, choose to refresh the archive list : all the other
languages/versions appear
3. then do the refresh once again

EXPECTED OUTCOME:
It should just refresh the languages/version in the window

ACTUAL OUTCOME:
The application crashes with a segmentation fault

REPRODUCIBILITY:
always, at least with my configuration

EXTRA SOFTWARE INSTALLED:

OTHER COMMENTS:
All my dumps are in the same directory

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.2.12)
Gecko/20101027 Ubuntu/10.04 (lucid) Firefox/3.6.12
Comment 1 christian 2010-11-19 20:45:49 UTC
I cannot reproduce that bug, but I have seen it once, too. Could you build the
debug version from git and attach a strack trace?
Comment 2 mossroy (reporter) 2010-11-21 00:38:53 UTC
How should I build evopedia to have the debug ? I did not find the right option
in qmake, make or Makefile
Comment 3 christian 2010-11-21 14:50:08 UTC
(In reply to comment #2)
> How should I build evopedia to have the debug ? I did not find the right option
> in qmake, make or Makefile

It's

qmake -config debug evopedia.pro
Comment 4 mossroy (reporter) 2010-11-21 16:41:01 UTC
(In reply to comment #3)
> qmake -config debug evopedia.pro

OK I compiled evopedia with this command, but I don't see where to get the
stack trace when I reproduce the segmentation fault.
Should I run evopedia differently?