David N. Welton
davidw at linuxcare.com
Thu Nov 18 17:45:36 EST 1999
On Wed, Nov 17, 1999 at 11:26:39PM -0500, David Edelsohn wrote:
> You're just messing with something. Most likely you are
> disrupting the condition register bits being used by the "blt"
Hmm... well, the 'davidw_debug' is supposed to crap out. It's a
function that calls printk, which I have been told is not really
available at that point in the game. I have noticed that I get a nice
'default catch' when it hits the printk, whereas, if I move the
function further down the list of things that happens, it apparently
isn't reached (or at least nothing is printed), as nothing crashes.
Maybe I should use a function that is guaranteed to crash?
Anyway, by moving this 'bomb' function around and rebooting way too
much, I narrowed down a region of code that I don't get the crash
after (meaning it hasn't reached my crash function or that it is
suddently ok to call it). That's what I posted...
It's been quite time consuming, and not very elegant, but lacking
anything else, it's all I have really (supposedly, someone is getting
me a null modem cable tommorow so that I can try and connect to the
David N. Welton, Developer, Linuxcare, Inc.
415.354.4878 x241 tel, 415.701.7457 fax
davidw at linuxcare.com, http://www.linuxcare.com/
Linuxcare. At the center of Linux.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev