> This happenned to me the other day when I did a simple "where" in the
> gdb console window (note: not using the backtrace dialog). DDD/gdb
> messes with my system big time...
> Just so you know you're not on crack...
Not that I ever do crack, I stick to the green stuff.. but, damn. I was
doing exactly that in DDD. I moved my mouse pointer over DDD's gdb window
and tried to type in something; BOOM, kernel went into orbit. Looks like
there's a nasty interaction between DDD/gdb and the kernel itself
(2.2.0-final) that sends it bye-bye. :o(
Note that gdb on its own works perfectly well. The problem's getting it to
log what's going on in the kernel's brains when it does that. Maybe Tux's
been at the crack again... ;o)
Which system library are you using? glibc-2.0.111? Or libc5? It might help
to narrow it down a bit futher so we can kill this bastard of a bug.
-- /\_/\ Legalise cannabis now! ( o.o ) Grow some cannabis today! > ^ < Peace, Love, Unity and Respect to all.
http://www.tahallah.demon.co.uk - *new* - rewritten for text browser users!
Linux tahallah 2.2.0-final #74 SMP Thu Jan 21 20:35:00 EST 1999 Two Intel Pentium Pro 166MHz processors, 331.78 total bogomips, 48M RAM System library 2.0.111
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com Please read the FAQ at http://www.tux.org/lkml/