Jump to content

Lamarr

Members
  • Posts

    5
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Lamarr's Achievements

Newbie

Newbie (1/3)

0

Reputation

  1. Wow. You guys just keep getting faster, seriously. The patch hasn't even been out for two weeks yet! I remember when it used to be that you actually had to downgrade your client to work with MaNGOS. This has really come a long way since then.
  2. Manually applied on 9632 as per the first post in the thread, works perfectly fine. Should work for any version, really, as long as the aura behavior doesn't change fundamentally.
  3. I'm using Linux too, but I still get segfaults, so it doesn't seem to be purely a Windows issue. Also, a clean Core + ScriptDev2 compile hasn't ever crashed for me at all, so I'm pretty positive it has to be an ahbot thing.
  4. I think I'm merging merging the right repository (git://github.com/Naicisum/mangos.git ahbot), but maybe there are errors I don't know about. Git says everything is fine, but I'll try running git mergetool and see if anything turns up. I'll gladly provide a dump if you tell me how to get one. As I said, I don't know squat about C++ coding, so I've got no idea where to find it.
  5. I can confirm that ahbot causes segmentation faults with Mangos rev9609. I've tried compiling with and without ahbot multiple times, and every time I compile the git pull from Naicisum's repository, Mangos will crash with a segfault after a few seconds of running. Compiling as such works fine though, no errors at all after merging the mangos.conf.dist.in manually. It used to work fine the last time, when I used the ahbot.patch you posted here in the thread, so I have no idea what could be wrong. GDB says that some thread related to the player.cpp is crashing, but I'm not familiar with debugging C++ and have no idea what this could mean.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use