[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

More on oskit-mach and serial debugging

From: Igor Khavkine
Subject: More on oskit-mach and serial debugging
Date: Sun, 8 Jul 2001 22:25:45 -0400
User-agent: Mutt/1.3.18i

I've successfuly setup my second box with a serial line as a console
and debugging line. I tried booting oskit-mach (from cvs) on it
and it failed with a segfault in one of the oskit drivers.

I discovered that when I tried to boot oskit-mach linked with oskit
which were both compiled with debug symbols. The problem is the
tulip driver, it's strange because it works when I boot linux
with the same driver on the same box.

I'll try to investigate and see where exactly the problem lies. But I'd
like to know about the capabilities of serial debugging. For example
I wasn't able to step through the code line by line or instruction
by instruction. I always got the message "Skipping to the end
of function <blah>, since it contains no line number information".
This is strange because I did compile everything with -g. So is
it possible to step through the code line by line? Also is it
possible to examine the contents of local variables?

Also, pardon my ignorance :-) but what's the command to log a GDB
session to a file?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]