Wyk3d

But you did freeze it ? This second log ended with a freeze detector crash. It may have been due to the high lag though.

Rational Purify can I think. It has free trial versions for both windows and linux available for download from IBM (as part of PurifyPlus).

Not natively, but we got it to use revision numbers and oddly enough it does that much better than things that were designed for it. The number is in revision_nr.h if you want to read it with external tools. It's shown in the client, server startup, wheaty crash log etc. All of those work even if you downloaded a snapshot of the sources instead of the git repo. It's shown in the commit log at the start of the commit message. You can even use the revision number instead of the SHA with existing git commands e.g: git reset --hard [6910]

Been a long time since anyone made a valgrind log of the server .. looks like there's lots of info to go over .

Offtopic: So what if you break something ? That's one of the great things about git, once you've committed something you're free to experiment with all sorts commands because even if you break something, you can always get it back with either reflog or branches. Only git gc and related plumbing commands can actually delete commits.

Are you sure that instability is not related to your patches ? Many of the crashes you are reporting I've never seen before.

What do you mean "fine", which version do you have ? Something is definitely not "fine", be it your git version or something with your installation because that command works "fine" otherwise.

Update your git versions ?

One very easy way to reset to revision 7042 for example is: git reset --hard [7042] Basically for every commit-ish command parameter you can use the [rev] syntax if you know the revision number.

Videos containing an overview of all the really important stuff that you should know: http://excess.org/article/2008/07/ogre-git-tutorial/

Interesting claim .. one would figure that handling creatures should take more time than players since there may be a thousand players but tens of thousands of creatures ..

Reset your branch.

If you don't want to switch the remote tracking branch (like from origin/master to origin/mangos-0.12) but just ditch what you have now and go back a couple of revs till you find something that works, resetting your current branch is better that creating a new one I guess. If you want to reset to the commit before the current: git reset --hard HEAD^ If you want to reset to 5 commits before the current: git reset --hard HEAD~5 Note that not all commits have rev numbers and it's generally recommended not to use commits which don't.

What you probably didn't find out from your discussion is that as soon as you've cloned you already have your own completely custom branch . By default that custom local branch is called "master", not to be confused with "origin/master" (which is by default the remote branch which your local master branch points to, but you can change that if you want with git reset). With git checkout -b X Y (shortcut to git branch X Y + git checkout X) you make additional local branches, but you don't really need that unless you want to be able switch between that and master quickly. For example if you create two databases, one for 303 and one for 242, you make two branches named A and B, one pointing to origin/master and one to origin/mangos-0.12, you add and commit the configuration files (with the matching database specified), you can switch between the two setups with a simple "git checkout A" or "git checkout B". That stuff is only made complicated by the database stuff, and it's the same for switching to older version. When database changes are not involved multiple branches become more useful. For example you could switch between a branch which contains only "vanilla" mangos and one which has your local changes, or you could have one branch which contains patches X,Y and one which contains Z,T. So if at any time you say "oops that patch totally messed something up", you just git checkout <the-previous-local-branch-that-worked>. You could also achieve similar things with revert. You apply a patch, commit it, and then you can pass that SHA of that commit to git revert to record another commit which reverts it. Maybe you have a branch which contains patches X,Y,Z but none with just Y,Z. Instead of removing all patches and applying Y,Z again you can just run revert on the commit where you added X.

Haven't checked the code but in general that construct is used when the array is static. The sizeof operator gets the size in bytes of whatever is passed to it. For a static array (and only for a static array) this is always equal to the number of elements times the size of one element, which is known at compile time, as well as the total size of the array, so the computation of the number of rows will result in a hardcoded constant number in the compiled code.

Found another good book http://www-cs-students.stanford.edu/~blynn/gitmagic/index.html .. that one doesn't have videos though.

Hmm, how disappointing, i thought "grammer" might actually be a word i haven't heard yet since you linked to it .. and then i got "a common misspelling." .

class Year { public: Year(int) {} } * happy = new Year(2009);

PQuery after a PExecute that it depends on -> FAIL (PQuery is executed immediately while PExecute is put on another thread and only executed later).. You need to use either DirectPExecute + PQuery or if you care about performance, PExecute + AsyncPQuery.

Have you read the FAQ? You need to commit the changes that you apply to your working copy, otherwise most operations will fail.

This look like a hack, but pet loyalty was completely removed in 3.0.3. Added to the mangos-0.12 branch.

Only few people can push to origin, the reason you see many authors is because the author of the commit is shown instead of the person who pushed the commit. So for example you make a commit on your own fork, you give me a link to it, and if it's something that's good to be added, I can cherry-pick it from your fork and push it, your name will be shown as the author even though you were not the one who pushed it to origin.

1. update to the latest git version 2. you don't have rights to push to origin, only to your own fork if you make one 3. you must use the private git url to push, not the public one (should look like [email protected]:Wyk3d/mangos.git) 4. make sure your private key is in a place where ssh can find it, usually in ~ (home)

http://code.google.com/p/msysgit/downloads/detail?name=Git-1.6.1-preview20081227.exe&can=2&q= Version 1.6.1 of mysgit was just released, some of the changes are immediately noticeable, especially in the gui/gitk .

That's the specific one that I fixed, there could be others I don't know of.