[comp.unix.i386] Kernel debugger

emmanuel@hpgnd.HP.COM (Emmanuel GAYET) (12/20/89)

 I am looking for a kernel debugger for Unix System V/386 . I have heard that
a Californian company named TRONIX INTERNATIONAL DATA CORP sales such a 
product but I cannot find the address or Tel number of that company.
Has anybody heard of them ? What other tools do you use when debugging code
in the Unix 386 kernel?
 
 Emmanuel GAYET

gerry@zds-ux.UUCP (Gerry Gleason) (12/22/89)

In article <2640001@hpgnd.HP.COM> emmanuel@hpgnd.HP.COM (Emmanuel GAYET) writes:

> I am looking for a kernel debugger for Unix System V/386 . I have heard that

ISC's 386/ix has one that comes with their OS.  We use it quite a bit, and
find it useful.  It's pretty basic, but has most of the features you really
need.  Of course, if you already have another OS, and are looking for an
add on package, this won't be much help.

Gerry Gleason

izen@amelia.nas.nasa.gov (Steven H. Izen) (12/22/89)

In article <64@zds-ux.UUCP> gerry@zds-ux.UUCP (Gerry Gleason) writes:
>In article <2640001@hpgnd.HP.COM> emmanuel@hpgnd.HP.COM (Emmanuel GAYET) writes:

>> I am looking for a kernel debugger for Unix System V/386 . I have heard that

>ISC's 386/ix has one that comes with their OS.  We use it quite a bit, and
>find it useful.  It's pretty basic, but has most of the features you really
>need.  Of course, if you already have another OS, and are looking for an
>add on package, this won't be much help.

Maybe you can answer a question for me.  I've RTFMd and not been able to
figure this one out.  TFM mentions setting breakpoints, but NOWHERE does it
say how to start the kernel executingg again!  Every time I've entered
the debugger, either due to a panic, or by hitting ctrl-alt-d, the only way out
seemed to be the power switch.  Am I missing something?


-- 
Steve Izen: {sun,uunet}!cwjcc!skybridge!izen386!steve  / Quote corner:
or steve%izen386.uucp@skybridge.scl.cwru.edu          / 
or izen@cwru.cwru.edu	   /-------------------------/ My second bike is a car.
                           | The problem is that I *was* paying attention.

emmanuel@hpgnd.HP.COM (Emmanuel GAYET) (12/22/89)

 I should have been more precise in my question: actually it is with the
 SCO Unix I am working with. It seems there are native debuggers with
 ISC or ATT Unix but it is not the case with SCO.

stevea@i88.isc.com (Steve Alexander) (12/22/89)

In article <4333@amelia.nas.nasa.gov> izen@cwru.cwru.edu (Steven H. Izen) wrote:
>Every time I've entered the debugger, either due to a panic, or by 
>hitting ctrl-alt-d, the only way out seemed to be the power switch.

Typing <CTRL>-D should exit the debugger.  In a panic situation you probably
just want to reboot, after optionally taking a system dump.

--
Steve Alexander, Software Technologies Group    | stevea@i88.isc.com
INTERACTIVE Systems Corporation, Naperville, IL | ...!{sun,ico}!laidbak!stevea

daveb@i88.isc.com (Dave Burton) (12/23/89)

In article <4333@amelia.nas.nasa.gov> izen@cwru.cwru.edu (Steven H. Izen) writes:
>[regarding kdb]
>Maybe you can answer a question for me.  I've RTFMd and not been able to
>figure this one out.  TFM mentions setting breakpoints, but NOWHERE does it
>say how to start the kernel executingg again!  Every time I've entered
>the debugger, either due to a panic, or by hitting ctrl-alt-d, the only way out
>seemed to be the power switch.  Am I missing something?

Try <ctrl-d>.
--
Dave Burton
uunet!ism780c!laidbak!daveb

johnl@esegue.segue.boston.ma.us (John R. Levine) (12/23/89)

In article <4333@amelia.nas.nasa.gov> izen@cwru.cwru.edu (Steven H. Izen) writes:
>Maybe you can answer a question for me.  I've RTFMd and not been able to
>figure this one out.  TFM mentions setting breakpoints, but NOWHERE does it
>say how to start the kernel executingg again!

The trick here is reasoning by analogy:  What is the regular unix program the
most similar to the kernel debugger?  dc, of course.  How do you get out of
dc?  By typing ctrl/D.  (Only wimps type q.)  Case solved.  The manual could
be more helpful, although typing "help" to the debugger does tell you this.
-- 
John R. Levine, Segue Software, POB 349, Cambridge MA 02238, +1 617 864 9650
johnl@esegue.segue.boston.ma.us, {ima|lotus|spdcc}!esegue!johnl
"Now, we are all jelly doughnuts."

Lance_C_Norskog@cup.portal.com (12/28/89)

Depending on what you're debugging, we may be able to help you.

Streamlined Networks has a special debugging system for UNIX Streams modules.
Called The Modulator (for Module Simulator), it allows you to put a
Streams device driver into a user program.

Since almost all communication with a Streams device driver is done
via messages, a trapdoor module in the kernel stands in for the module
that you're debugging, and all messages passed to the trapdoor are sent
up to your test module.  When your module emits a message, it goes back
down into the kernel and pops out of the trapdoor.  The result: your
applications use the module as if it were in the kernel.  You can get a 
module up to (almost) full functionality without ever crashing the kernel. 

If you'd like sales literature, please send your postal address.

Lance Norskog
Sales Engineer
Streamlined Networks
1-415-659-1450
thinman@cup.portal.com

john@touch.UUCP (John Weald) (01/03/90)

In article <2640001@hpgnd.HP.COM> emmanuel@hpgnd.HP.COM (Emmanuel GAYET) writes:
>
> I am looking for a kernel debugger for Unix System V/386 . I have heard that
>a Californian company named TRONIX INTERNATIONAL DATA CORP sales such a 
>product but I cannot find the address or Tel number of that company.
>Has anybody heard of them ? What other tools do you use when debugging code
>in the Unix 386 kernel?
> 
> Emmanuel GAYET

We had an evaluation copy of this debugger. Functionally is a little richer
than the 386/ix debugger and the user interface is a better. 
Additional functionality includes; skipping over function calls, call
functions within the kernel and display certain kernel data structures
in a formatted way.

It runs on SCO Xenix 386, ISC 386/ix, Everex Enix and AT&T's SVR3.2.

We were quoted a price of $475.00

Tronix can be reached at 408-973-8559.

------
Cheers!

John Weald, Touch Commincations, Campbell, CA

uunet!touch!jweald

brian@apt.UUCP (Brian Litzinger) (01/03/90)

From article <105@touch.UUCP>, by john@touch.UUCP (John Weald):
> In article <2640001@hpgnd.HP.COM> emmanuel@hpgnd.HP.COM (Emmanuel GAYET) writes:
>>
>> I am looking for a kernel debugger for Unix System V/386 . I have heard that
>>a Californian company named TRONIX INTERNATIONAL DATA CORP sales such a 
>>product but I cannot find the address or Tel number of that company.
>>Has anybody heard of them ? What other tools do you use when debugging code
>>in the Unix 386 kernel?
>> 
>> Emmanuel GAYET
> 
> It runs on SCO Xenix 386, ISC 386/ix, Everex Enix and AT&T's SVR3.2.
> We were quoted a price of $475.00
> Tronix can be reached at 408-973-8559.

I have the Tronix debugger, and I like it except that you can't break
on IO port accesses.  Something I was hoping to do.

The MSDOS 386 debugger I have can break on IO port accesses so obviously
it can be done.

<>  Brian Litzinger @ APT Technology Inc., San Jose, CA
<>  UUCP:  {apple,sun,pyramid}!daver!apt!brian    brian@apt.UUCP
<>  VOICE: 408 370 9077      FAX: 408 370 9291