aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2005-01-23document -qrsc1-0/+4
2005-01-23document core and stackrsc2-13/+31
2005-01-23sort cores; print stack as commandrsc1-7/+16
2005-01-23changes mainly for threading supportrsc1-0/+72
2005-01-23less verbosersc1-1/+2
2005-01-23change to use attach functions.rsc5-97/+35
$a means switch thread in core dumps. (maybe that should be $A now?).
2005-01-23Working on better handling of multithreading in generalrsc10-174/+526
and core dumps in particular. See notes: new types: register is something that when dereferenced gives you the registers. the Ureg is no longer mapped at 0. refconst is something that gives a constant when dereferenced. new builtin register("AX") creates register values new builtin refconst(0x123) creates refconst values new builtin var("foo") is equivalent to the variable foo (it returns foo but can also be used as the lhs of an assignment). new acid function getregs() returns a list of the current values of registers. new acid function setregs() sets the current registers to those values. note that getregs and setregs operate on register locations, not the register values themselves. new acid function resetregs() sets registers to register("AX"), etc. new acid function clearregs() sets all registers to constant -1. the default register settings are as in resetregs(), not small numbers. new acid variables coretext, pids, systype, corefile, cmdline. new behavior: local variable lookup, stk, etc., use the acid values of registers (*PC, *SP, and so on), so the thread support code can change the context completely. unary + is applicable to more data types and prints more often.
2005-01-23document searchpath(3)rsc1-0/+61
2005-01-23Add searchpath().rsc3-0/+64
2005-01-23Extract more data from core dumps.rsc1-4/+11
2005-01-23Start working through proper handling of pthreads whenrsc14-415/+528
debugging Linux core dumps. Pthreads for active processes is still not supported, nor are other systems.
2005-01-23Apparently SuSE 9.1's X distribution uses even biggerrsc4-4/+5
buffers than the standard ones. 64kB appears to be enough for a stack in that case, but let's just go nuts and make the stacks enormous, so that it takes a few more doublings of X's stack needs before we run into this problem again. The VM system should take care of not actually using most of the memory anyway.
2005-01-23redirect debugging output of isnptlrsc1-1/+1
2005-01-21arg countrsc1-1/+1
2005-01-21use better versionsrsc3-3/+4
2005-01-21replace mdir with mkdir; oopsrsc1-1/+1
2005-01-20ignore host read eof while exitingrsc3-0/+9
2005-01-20todorsc1-0/+6
2005-01-20core has been writtenrsc1-3/+9
2005-01-19use correct yaccrsc1-1/+0
2005-01-19more ignoresrsc1-1/+1
2005-01-19add errnorsc2-1/+1
2005-01-19fixesrsc1-1/+1
2005-01-19show only interesting log entriesrsc1-0/+3
2005-01-19do not use shutdown on macrsc1-4/+6
2005-01-19avoid c99rsc1-15/+22
2005-01-19avoid c99 extensionsrsc1-4/+15
2005-01-19bad $variable namesrsc1-2/+2
2005-01-19try againrsc1-4/+4
2005-01-19try again at x86-64rsc1-1/+3
2005-01-19continue x86-64rsc3-1/+10
2005-01-19do not close -1rsc1-1/+2
2005-01-19updatersc1-0/+12
2005-01-19do not translate man pagesrsc1-1/+1
2005-01-19do not use rpath on Darwinrsc1-2/+6
2005-01-18proccreate racersc1-1/+3
2005-01-18free hdr->cmdrsc1-0/+1
2005-01-18extract cmd in right placersc3-6/+6
2005-01-18addrsc1-0/+102
2005-01-18add core cmdrsc4-0/+65
2005-01-18print core cmdrsc1-0/+1
2005-01-18run LOCAL.INSTALLrsc1-1/+4
2005-01-18check for lack of registersrsc1-4/+4
2005-01-18bigger chunkingrsc1-1/+1
2005-01-18add threadgetnamersc1-0/+6
2005-01-18bug fixesrsc5-11/+16
2005-01-18update 9menu urlrsc1-1/+1
2005-01-18gonersc1-17/+0
2005-01-18updatersc3-10/+29
2005-01-18add threadspawnlrsc1-0/+1