[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
According to the following url (beware, long lines follow):
http://groups.google.com/groups?q=debug&start=20&group=comp.programming.threads&rnum=27&selm=3BB21269.74AF563E%40webmaster.com
...when you recieve a sigsegv you could fork and call abort, which
aparently leaves a core, maybe because the forked process doesn't suffer
from the thread environment or behaves like an independend process :-?
Another way is running your program directly from the debugger, whenever
you get an error the program will stop and gdb will gain control. I've
tried to do this before with Allegro programs under X, trying to reach a
break condition and stepping through the code. However, from the first
break gdb starts to behave weird, recieving signals which disturb it
and make debugging a pain. At least that's what happened some months ago.
Aparently there are patches/versions of gdb which turn it able to debug
multithreaded applications depending on your thread library and how you
compiled it. Some other debuggers/libs known to work with threads:
http://groups.google.com/groups?q=debug+thread&group=comp.unix.programmer&rnum=6&selm=85703CDB221DD511AA200060089CD8B12FBA1D%40hydmail01.hyd.wilco-int.com
http://groups.google.com/groups?q=debug+thread&group=comp.unix.programmer&rnum=3&selm=3mmab1%24ab0%40agate.berkeley.edu
--
Grzegorz Adam Hankiewicz gradha@xxxxxxxxxx http://gradha.infierno.org/