Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
smallbin double linked list corrupted #74
This is with the newest git
I'll send the save file to Yohann for looking at it.
ulimit -c unlimited
so if the Valyria executable is ValyriaTear and the core dump file is
gdb ValyriaTear core.1234
this wil load gdb up with the executable, its code trace and the backtrace
when gdb finishes loading, type:
this will give you the backtrace for the program. if you can copy and paste
let me know if you get stuck or need more help!
Now, make sure Valyria is built with no optimizations on, and the -g option (otherwise you get very little usefull data).
What I do is
~/games/valyriatear$ git pull origin master
and that's the end of that.
So should I be doing ?
Did that and it generated a core file which is of 63 MB .
~/games/valyriatear$ ls -lh core
Did the ulimit thing again just in case I need to it or something and tried to load it :-
~/games/valyriatear$ gdb ./src/valyriatear core
warning: Can't read pathname for load map: Input/output error.
As can be seen I had to quit it. Any ideas ?
did you actually have to type quit? if so , it was actually working just
Core was generated by `./src/valyriatear'.
these two lines are telling you where the core file was generated from, and
is actually from valyriatear, not from gdb. this is OK, and it means your
you reached the gdb command line, right? it looks like
and then nothing else happens? actually, everything happened correctly :)
just type "bt" like so:
and see what you get
I had to type quit. This is the out when I just write bt in it :-
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
And I get the gdb prompt back. I guess the above info. is the one which was wanted/needed ?
yes! thats it. that right there is the last 20+ function calls before the crash.
.. unfortunately, I don't see any valyriatear code in here...it looks like something going on between SDL and OGL....
the next thing you can try, if you're sure that you can reproduce ths bug, is to run the application right through gdb. This is straight forward. from your shell:
~/games/valyriatear$ gdb ./src/valyriatear
when gdb loads and you are at the gdb prompt, type "run"
this will start the game in debuging mode. keep in mind you may get some performance slowdown from this. if it becomes unplayable, well...we may be have to just keep hunting using core dumps.
and copy / paste this and the error message you get here