#7033: install anything from terminal results in gdb, BT included ------------------------------------+-------------------------- Reporter: stargatefan | Owner: jackburton Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/Terminal | Version: R1/alpha2 Resolution: | Keywords: Blocked By: | Has a Patch: 0 Platform: All | Blocking: ------------------------------------+-------------------------- Comment (by bonefish): Replying to [comment:7 luroh]: > Replying to [comment:5 stargatefan]: > > It also sent my CPU temps skyward so I am lucky it didn't kill my cpu, power supply or motherboard. Thankfully I have thermal limiting in place on my motherboard. > > If I were you, I'd run a stress test (perhaps grab a live CD like [http://www.inquisitor.ru/ Inquisitor]) to verify the general stability of your hardware. installoptionalpackage is pretty CPU intensive - that in combination with e.g. a CPU fan starting to cave in could possibly be the cause. In principle it is possible that a kernel bug can cause such a behavior (random application crashes) -- most likely in the VM subsystem -- but there haven't been any significant changes for quite a while, and this is the only report of such problems I know of. So to me this also sounds very much like a hardware issue, particularly since you mention very high CPU temperatures. The OS is not responsible for keeping the CPU temperature in some range (I haven't read anything in this regard in the IA-32 specification yet at least), even if other OSs try to do that (and we should eventually implement that in Haiku, too). Torturing the CPUs a bit, like luroh suggests, is certainly not a bad idea. If you have a Unixish system, a `while true; do true; done` per hardware thread should do the trick. If nothing else critical CPU temperatures should at least be logged somewhere (syslog/system messages). -- Ticket URL: <http://dev.haiku-os.org/ticket/7033#comment:8> Haiku <http://dev.haiku-os.org> Haiku - the operating system.