From: sven schnelle <schnelle@kabelleipzig.de>
To: Patrick Caulfield <patrick@tykepenguin.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] kdb include files
Date: Mon, 08 Jul 2002 09:03:45 +0200 [thread overview]
Message-ID: <3D293951.6060702@kabelleipzig.de> (raw)
In-Reply-To: 20020708064246.GC815@tykepenguin.com
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Patrick Caulfield wrote:
>On Sun, Jul 07, 2002 at 08:11:47PM -0400, Carlos O'Donell wrote:
>
>
>>>hello,
>>>
>>>Im writing on a floppy driver for my 712 and want to use kdb,
>>>
>>>but when i try to compile the kernel with it, i get errors:
>>>
>>>kdb/break.h: No such file or directory
>>>kdb/kgdb_types.h: No such file or directory
>>>kdb/kgdb_machine.h: No such file or directory
>>>kdb/trap.h: No such file or directory
>>>
>>>does anybody know where i can get this files ?.
>>>
>>>bye
>>> sven
>>>
>>>
>>If you haven't already done so, I would recommend getting
>>a kdb patched source tree from cvs.parisc-linux.org
>>
>>There is a 'kdb_v21' branch for the 'linux' tree.
>>
>>cvs co -rkdb_v21 linux
>>
>>Please take a look at:
>>http://cvs.parisc-linux.org
>>
>>Note: That I'm currently working on kdb's stability...
>>so you might not get something that is as happy as you
>>expect from other platofrms.
>>
>>
>
>It's a little confusing that there's mention of KDB in the
>non-KDB enabled kernel. Under General Options it says
>"Kernel Debugger support" which seems (to me) to have the
>sole function of generating the above messages :)
>
>patrick
>
>
that's right. If I disable it under general options and patch
the kernel as written above kdb works.
thanks,
sven
[-- Attachment #2: Type: text/html, Size: 1701 bytes --]
prev parent reply other threads:[~2002-07-08 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 6:02 [parisc-linux] kdb include files sven schnelle
2002-07-08 0:11 ` Carlos O'Donell
2002-07-08 6:42 ` Patrick Caulfield
2002-07-08 7:03 ` sven schnelle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D293951.6060702@kabelleipzig.de \
--to=schnelle@kabelleipzig.de \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=patrick@tykepenguin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox