There's a tool named Valgrind, http://valgrind.org, which can help to find
memory leaks and mysterious bugs in code.

On Fri, Apr 2, 2010 at 1:59 PM, Patrick Baggett
<[email protected]>wrote:

> It would be helpful to know if you are getting a SIGSEGV or SIGILL, or
> what. From the backtrace, it looks like it made it into VM_Call() where it
> can branch to a DLL function if executing native code, VM_CallInterpreted()
> if interpreting a QVM, or VM_CallCompiled() if executing complied QVM code.
> The address it is branching to looks very high in memory compared the other
> ones (Virtual Address in the 806MB range)  -- suspect, even. I wouldn't be
> surprised if that is just an invalid address.
>
> You might check vm->entryPoint (DLL function) to make sure it was
> initialized correctly, or use just the QVMs to see if that resolved the
> issue. If it does, then your DLLs might be bad or there is some other rogue
> heap corruption that is overwriting the QVM structure.
>
> Patrick
>
> On Fri, Apr 2, 2010 at 2:02 AM, Michael Menegakis <[email protected]>wrote:
>
>> By running a [black box] command in urban terror, without the
>> arguments it usually requires, it crashes the client with
>>
>> #0  0x32643db5 in ?? ()
>> #1  0x0046aa00 in VM_Call (vm=0x1ef1d10, callnum=2) at
>> code/qcommon/vm.c:771
>> #2  0x0040a1a0 in CL_GameCommand () at code/client/cl_cgame.c:791
>> #3  0x00431831 in Cmd_ExecuteString (text=0x28f484 "ut_weaptoggle") at
>> code/qcommon/cmd.c:
>>
>> However, that doesn't appear on the vanilla client, but only mine,
>> which has been modified over the time.
>>
>> I had increases cvar limit, console history limit, console length
>> limit and config limit, but returning them to same values it didn't
>> return to normal.
>> _______________________________________________
>> ioquake3 mailing list
>> [email protected]
>> http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
>> By sending this message I agree to love ioquake3 and libsdl.
>>
>
>
> _______________________________________________
> ioquake3 mailing list
> [email protected]
> http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
> By sending this message I agree to love ioquake3 and libsdl.
>
_______________________________________________
ioquake3 mailing list
[email protected]
http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
By sending this message I agree to love ioquake3 and libsdl.

Reply via email to