Go Back   EQEmulator Home > EQEmulator Forums > Support > Support::Linux Servers

Support::Linux Servers Support forum for Linux EQEMu users.

Reply
 
Thread Tools Display Modes
  #1  
Old 07-07-2009, 02:07 PM
cubber
Discordant
 
Join Date: Apr 2006
Posts: 374
Default

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?
Reply With Quote
  #2  
Old 07-07-2009, 02:41 PM
gaeorn
Developer
 
Join Date: Apr 2009
Location: USA
Posts: 478
Default

You need the -g option in there to include debugging information.
Reply With Quote
  #3  
Old 07-07-2009, 02:50 PM
cubber
Discordant
 
Join Date: Apr 2006
Posts: 374
Default

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.
Reply With Quote
  #4  
Old 07-07-2009, 03:16 PM
cubber
Discordant
 
Join Date: Apr 2006
Posts: 374
Default

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.
Reply With Quote
  #5  
Old 07-07-2009, 03:23 PM
gaeorn
Developer
 
Join Date: Apr 2009
Location: USA
Posts: 478
Default

If I were to venture a guess, I would suspect the -O3 as the culprit.
Reply With Quote
  #6  
Old 07-07-2009, 03:25 PM
cubber
Discordant
 
Join Date: Apr 2006
Posts: 374
Default

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?
Reply With Quote
  #7  
Old 07-07-2009, 03:30 PM
gaeorn
Developer
 
Join Date: Apr 2009
Location: USA
Posts: 478
Default

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.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 06:27 AM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3