> I think you misunderstood my question. I'm sure you know that
> gdb will display the source code of your program while you
> step through it. I am debugging the oskit-mach kernel, and
> I can follow the kernel source except when it calls an oskit
> function, I just wondered where the oskit source
Title: 이메일문서
기적의 영어 7English 샘플 샘플을
보시려면 <한글97>이 설치되어 있어야 합니다. 다음은 영어교육개혁 협회의 발표문을 인용한
것입니다.
《1》 폐지되는 영문법 80% 25개항 - 상세히 보기-클릭학계와 교육계의 98%의 지지로 결정된 사항입니다. 《2》 기적의
단어숙어, 문법의 혁명 - 원소이론-클릭
I think you misunderstood my question. I'm sure you know that
gdb will display the source code of your program while you
step through it. I am debugging the oskit-mach kernel, and
I can follow the kernel source except when it calls an oskit
function, I just wondered where the oskit source should be
"B. Douglas Hilton" <[EMAIL PROTECTED]> writes:
> I noticed my gdb isn't properly finding the oskit sources when I am
> stepping through the kernel. How should the source tree be arranged
> so that it works as expected?
Uhm, I don't know what's the cause of your problem, but did you have a
look a
I just did a "cp -a" of my /gnu partition onto oskit-mach's
new home on the IDE drive. I was able to boot my
"kernel-ide" with no problems. It happily fired up
and gave me a Bourne shell with TERM=dumb and
some error about "/dev/console is not a console".
I assume this is normal for oskit-mach. For
I noticed my gdb isn't properly finding the oskit sources
when I am stepping through the kernel. How should the
source tree be arranged so that it works as expected?
BTW: I allocated my 640MB IDE drive to oskit-mach
since the problem with aic78xx seems formidable right
now. That should enable me to
6 matches
Mail list logo
