
But, for the sake of completeness I've pasted a generated backtrace here. This a Mac OS X generated one, but it should be roughly equivalent to a gdb bt, I believe. If a more complete one (including *ALL* processes running on my machine at the time of the crash) is required, well, I can try and get one of those.
I've not seen this in the svn versions I've been running sporadically, but I've not been playing any significant amount of Nexuiz recently. So, according to the small amount of non-scientific general usage tests I've done, I'd be tempted to guess that this (the crashing bug; have no idea about the movement one touched on) will be fixed in 2.5.2 and is not a Mac OS X specific bug.
EDIT: I realise that the minimal back trace above doesn't give conclusive proof that this is the same bug, so I'm trying to get it to crash while gdb is attached to it. If it proves to be otherwise, or seems that way, I'll look into filing a new bug at that dev bug tracker if that's possible.