The_Piper Report post Posted April 11, 2008 (edited) My CVS client (from March, 27th) crashes from time to time, its not reproduceable. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1222764848 (LWP 5236)] 0x0811fb2d in ec_recall_effect () (gdb) where #0 0x0811fb2d in ec_recall_effect () #1 0x080e9833 in filter_or_ignore_text () #2 0x000000ff in ?? () Ah.. additional info.. It just crashed again, and the 2 last crashes happened when you stop harvesting. First time, the char was overloaded, 2nd time i stopped harvesting by eating. Piper Edit: eye candy and harvesting effect are both enabled. Edited April 11, 2008 by The_Piper Share this post Link to post Share on other sites
Vegar Report post Posted April 11, 2008 Can you try reproducing it with a more recent checkout? Preferably compiled with debugging symbols (-ggdb if you're using gcc). Share this post Link to post Share on other sites
The_Piper Report post Posted April 11, 2008 (edited) This client was compiled with -ggdb according to the Makefile.linux i used # basic compiling and linking - rarely changed OPTIONS = -DLINUX -DELC $(foreach FEATURE, $(FEATURES), -D$(FEATURE)) CFLAGS=$(PLATFORM) $(CWARN) -O0 -ggdb -pipe $(OPTIONS) $(shell sdl-config --cflags) $(shell xml2-config --cflags) -fno-strict-aliasing $(EXTRA_INCLUDES) _CFLAGS=$(PLATFORM) -O2 -fomit-frame-pointer -ffast-math -pipe $(OPTIONS) $(shell sdl-config --cflags) $(shell xml2-config --cflags) -fno-strict-aliasing $(EXTRA_INCLUDES) Thats the Makefile.linux i got from CVS, and i was a little bit astonished that "where" and "bt full" commands didnt gave me more informations, like the expected line of source, variables and such. I tried to reproduce it right now with my current client, by starting/stopping harvesting veggies 30-40 times, but no success. Ill try to get the actual source from CVS later and try that one. Piper Edited April 11, 2008 by The_Piper Share this post Link to post Share on other sites
Entropy Report post Posted April 12, 2008 AFAIK, the stop harvesting bug has been fixed a while ago, so get the latest CVS. Share this post Link to post Share on other sites
The_Piper Report post Posted April 12, 2008 I run an actual CVS client now, lets see what happens. Piper Share this post Link to post Share on other sites
The_Piper Report post Posted April 16, 2008 And a few days later, the bug is gone obviously. No crashes anymore. So the latest CVS client fixed it, i guess. Piper Share this post Link to post Share on other sites