[gcompris-devel] Segmentation fault CVS

Ralf Jardon ralf.jardon at uni-koeln.de
Sun Jan 25 04:37:01 UTC 2004


Am So, den 25.01.2004 schrieb Olivier Samyn um 12:52:
> Ralf Jardon wrote:
> 
> >Am Sa, den 24.01.2004 schrieb Bruno Coudoin um 14:45:
> >  
> >
> >>Just commited some changes but nothing related to your bug.
> >>Could you send me the output trace when running gcompris in a console.
> >>    
> >>
> >
> >I´ve grabbed the current CVS-Code today (Sunday 11 o'clock)
> >With python compiled in the following error occured:
> >
> >[...] all plugins loaded
> >---
> >** Message:     plugin /usr/local/lib/gcompris/libread_colors.so loaded
> >/usr/local/lib/gcompris/libpython.so: undefined symbol:
> >gcompris_log_set_reason
> >Segmentation fault
> >---
> >
> >After compiling with "--without-python":
> >  
> >
>  ?!?? Seems strange, are you sure you made a cvs update this morning ?

Some minutes ago i've purged my source-tree and made a completely new
cvs update. After compiling the python bug is removed but the segfault
as described in my previous mail is still there :(
The gdb trace is still the same...

Regards
Ralf

> 
> I commited yesterday the changes that removes this error with the python 
> plugin...
> (and I just took a look at cvs.gnome.org and it seems correct)
> 
> Olivier Samyn
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> gcompris-devel mailing list
> gcompris-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gcompris-devel






More information about the Gcompris-devel mailing list