| 
 Code: file core | 
| 
 Ok gdb finished compiling here is the output: Code: gdb ./world core | 
| 
 Your world executable appears to be stripped. That removes a lot of debugging information. I would suggest you rebuild it and not strip it. Then get the backtrace from a fresh core dump. | 
| 
 From what I'm hearing, gentoo strips the executable by default. I don't know how to change that behavior. You should do some google searches or ask a gentoo expert to find out how to disable stripping the executable. | 
| 
 here is what I change in my makefiles DFLAGS=-DDEBUG=5 -DEQDEBUG=2 -DSHAREMEM -DCATCH_CRASH -DNO_PIDLOG -DFIELD_ITEMS -DIRC -Di386 -DAPP_OPCODE_SIZE=2 -DEQBOTS COPTS=$(WFLAGS) -march=native -O3 -pthread -pipe I also remove the -g and -pg flags if they are there. I take it you want me to change the DEQDEBUG=2 to something like DEQDEBUG=5? | 
| 
 You need the -g option in there to include debugging information. | 
| 
 Ok I will try recompiling with -g, then I will reproduce the crash and hit the new core file with gdb and post the results. | 
| 
 Very Interesting... I wacked my svn source folder and just pulled down new sources. Ended up being rev752. I then only changed the -march=i686 option in each makefile to -march=native and left everything else at default. I also did NOT enable bots. I did not change any -O options or remove the -g flags like I normally do nor did I change -DEQDEBUG=5 to -DEQDEBUG=2. When I went to log in and create a character the character created fine but I got an error saying that the zone was not available yet. It then just stuck the character in my list and I was then able to choose the character and login to Gloomingdeep. So something in the compile options was screwing me up. Though I have used those settings for quite a while now without an issue. The only change now is that I am running gcc4.3.2 instead of gcc3.2.6 and using -march=native instead of -march=cpufamily_name. I will have to try recompiling with bots and see if it still works. | 
| 
 If I were to venture a guess, I would suspect the -O3 as the culprit. | 
| 
 yah gonna leave them alone, and just keep everything default with the -march=native and try enabling bots. does removing -g and changing -DEQDEBUG=2 give that much more of a performance boost over running the server with it enabled? | 
| 
 As far as the DEBUG=2, I would doubt it would have much effect since most of the debugging is configured at runtime now. As to the -g, I'm not the right person to ask. My guess would be that it doesn't slow it down much. | 
| 
 Compiled with bots and all seems fine.  Thanks for the assistance! | 
| All times are GMT -4. The time now is 06:47 PM. | 
	Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.