Skip to contentSkip to conversation

Novell Linux Kernel Debugger (NLKD)

DISCUSSION Clyde Griffin 12 participants 20 messages Jun 23, 2005 – Jun 27, 2005

lore
Share & tools
lore
#0 lore raw

Novell engineering is introducing the Novell Linux Kernel Debugger (NLKD) as an open source project intended to provide an enhanced and robust debugging experience for Linux kernel developers.

The project (nlkd) at http://forge.novell.com/modules/xfmod/project/?nlkd currently has code patches to SUSE Linux Enterprise Server v9 SP1 and SP2, which when applied allow kernel developers to recompile the Linux kernel exposing the functionality provided by NLKD.

Patches against the mainline will be forthcoming after community feedback.

At this point the intent of this project is to gather comments and suggestions on how to improve NLKD and make it possible for NLKD to be included as a native (mainline) kernel debugger for Linux. Novell engineering will be actively involved in reviewing comments regarding NLKD and submitting and receiving patches for the support of NLKD.

NLKD provides an architecture for supporting a stable debugging experience as well as debug agents supporting local and remote debugging. NLKD's Console Debug Agent (CDA) supports on-box kernel debugging and is extremely rich in functionality and easy to use. The Remote Debug Agent (RDA) supports remote source level debugging via gdbtransport to your favorite gdb based client. Both agents benefit from the Core Debug Engine (CDE), which provides the state machine logic supporting the debug agents.

A detailed description of the architecture will be presented in a paper titled "The Novell Linux Kernel Debugger, NLKD" at the Ottawa Linux Symposium July 20-23, 2005.

NLKD provides debugging capabilities that will be a benefit to the whole development community and we invite developers interested in using NLKD to download the patches, provide feedback, and benefit from the use of this great tool.

Developers interested in commenting on, contributing to, testing, documenting, and improving NLKD should subscribe to the nlkd-dev mailing list at http://forge.novell.com/modules/xfmod/project/?nlkd and post to [email protected].

#1 lore raw
Quoted 5 lines · Clyde Griffin

At this point the intent of this project is to gather comments and suggestions on how to improve NLKD and make it possible for NLKD to be included as a native (mainline) kernel debugger for Linux.  Novell engineering will be actively involved in reviewing comments regarding NLKD and submitting and receiving patches for the support of NLKD.

Does / Will it support remote debugging over firewire ports? I think this would be a great opportunity to get rid of the serial port requirement for debugging.

Parag

#2 lore raw
In reply to Clyde Griffin
Quoted 2 lines · Clyde Griffin

Patches against the mainline will be forthcoming after community feedback.

Please provide patches against a mainline kernel, otherwise it's pretty much impossible to review.

And try to reduce the ammount of #ifdev CONFIG_CDE you have placed in your patch, it's quite excessive and against the kernel coding style rules.

thanks,

greg k-h

#3 lore raw
In reply to Clyde Griffin
Quoted 3 lines · Clyde Griffin

Novell engineering is introducing the Novell Linux Kernel Debugger (NLKD) as an open source project intended to provide an enhanced and robust debugging experience for Linux kernel developers.

Umm... How does this differ from KDB?

#4 lore raw
Quoted 7 lines · Christoph Lameter
Quoted 3 lines · Clyde Griffin

Novell engineering is introducing the Novell Linux Kernel Debugger (NLKD) as an open source project intended to provide an enhanced and robust debugging experience for Linux kernel developers.

Umm... How does this differ from KDB?

Sounds like it overlaps w/ both KDB and KGDB...still, the question stands...

John

Signature · 2 lines
John W. Linville
[email protected]
#5 lore raw
Quoted 11 lines · John W. Linville
Quoted 7 lines · Christoph Lameter
Quoted 3 lines · Clyde Griffin

Novell engineering is introducing the Novell Linux Kernel Debugger (NLKD) as an open source project intended to provide an enhanced and robust debugging experience for Linux kernel developers.

Umm... How does this differ from KDB?

Sounds like it overlaps w/ both KDB and KGDB...still, the question stands...

I would appreciate efforts to consolidate all of these and finally get one into the kernel.

#6 lore raw
In reply to John W. Linville

I have downloaded and reviewed the code. It's a GBD replacement and is not fully open source. KDB is at present more capable. It has a lot of promise, but it does not have the all the architectural features necessary to replace either KDB or GDB at present.

Jeff

Quoted 20 lines · Christoph Lameter
Quoted 12 lines · Clyde Griffin
Quoted 6 lines

Novell engineering is introducing the Novell Linux Kernel Debugger (NLKD) as an open source project intended to provide an enhanced and robust debugging experience for Linux kernel developers.

Umm... How does this differ from KDB?

Sounds like it overlaps w/ both KDB and KGDB...still, the question stands...

John

#7 lore raw
Quoted 2 lines · jmerkey

I have downloaded and reviewed the code. It's a GBD replacement and is not fully open source.

Thanks for that info. Guess I really won't have to bother looking at it any more now ;)

I'll go back to waiting for systemtap...

Signature · 3 lines
The Theory of Escalating Commitment: "The cost of continuing mistakes is
borne by others, while the cost of admitting mistakes is borne by yourself."
  -- Joseph Stiglitz, Nobel Laureate in Economics
#8 lore raw
Quoted 4 lines · Rik Van Riel

On Thu, 23 Jun 2005, jmerkey wrote:

Quoted 11 lines
Quoted 3 lines

I have downloaded and reviewed the code. It's a GBD replacement and is not fully open source.

Thanks for that info. Guess I really won't have to bother looking at it any more now ;)

I'll go back to waiting for systemtap...

Rik,

You are most welcome. You should encourage Clyde though to keep working to convince Novell to release all of it open source. Clyde is a really good guy, and he knows what he's doing.

:-)

Jeff

#9 lore raw
In reply to jmerkey
Quoted 1 line

It's a GBD replacement and is not fully open source.

What is not open source in it ()?

Quoted 3 lines

KDB is at present more capable. It has a lot of promise, but it does not have the all the architectural
features necessary to replace either KDB or GDB at present.

While I never used or saw kdb, I'd be curious about what you immediately saw missing...

Jan

#10 lore raw
Quoted 8 lines · Jan Beulich
Quoted 3 lines

It's a GBD replacement and is not fully open source.

What is not open source in it ()?

Quoted 8 lines
Quoted 4 lines

KDB is at present more capable. It has a lot of promise, but it does not have the all the architectural features necessary to replace either KDB or GDB at present.

While I never used or saw kdb, I'd be curious about what you immediately saw missing...

1. No back trace
2. Doesn't run standalone fully embeded in the kernel
3. Not fully open source (since it's not embeded in the kernel)
4. IA64 doesn't really matter, since IA64 is basically dead anyway
5. No advanced recursive descent parser for conditional breakpoints

Jeff

Quoted 5 lines

Jan

#11 lore raw
Quoted 9 lines · jmerkey
Quoted 8 lines · Jan Beulich
Quoted 1 line

It's a GBD replacement and is not fully open source.

What is not open source in it ()?

Quoted 3 lines

KDB is at present more capable. It has a lot of promise, but it does not have the all the architectural
features necessary to replace either KDB or GDB at present.

Quoted 8 lines
Quoted 2 lines

While I never used or saw kdb, I'd be curious about what you immediately saw missing...

1. No back trace
2. Doesn't run standalone fully embeded in the kernel
3. Not fully open source (since it's not embeded in the kernel)
4. IA64 doesn't really matter, since IA64 is basically dead anyway
5. No advanced recursive descent parser for conditional breakpoints

This is more or less completely inaccurate.

-chris

#12 lore raw
Quoted 30 lines · Chris Mason
Quoted 19 lines · jmerkey
Quoted 7 lines · Jan Beulich
Quoted 3 lines

It's a GBD replacement and is not fully open source.

What is not open source in it ()?

Quoted 9 lines
Quoted 5 lines

KDB is at present more capable. It has a lot of promise, but it does not have the all the architectural
features necessary to replace either KDB or GDB at present.

While I never used or saw kdb, I'd be curious about what you immediately saw missing...

Quoted 7 lines

1. No back trace
2. Doesn't run standalone fully embeded in the kernel
3. Not fully open source (since it's not embeded in the kernel)
4. IA64 doesn't really matter, since IA64 is basically dead anyway
5. No advanced recursive descent parser for conditional breakpoints

Quoted 4 lines

This is more or less completely inaccurate.

Which one -- more ? or less ?

Jeff

Quoted 6 lines

-chris

#13 lore raw
Quoted 9 lines · jmerkey
Quoted 7 lines
Quoted 5 lines

1. No back trace
2. Doesn't run standalone fully embeded in the kernel
3. Not fully open source (since it's not embeded in the kernel)
4. IA64 doesn't really matter, since IA64 is basically dead anyway
5. No advanced recursive descent parser for conditional breakpoints

This is more or less completely inaccurate.

Which one -- more ? or less ?

I think Jan answered this in detail later in the thread.

-chirs

#14 lore raw
Quoted 11 lines · Chris Mason
Quoted 7 lines · jmerkey
Quoted 7 lines
Quoted 7 lines

1. No back trace
2. Doesn't run standalone fully embeded in the kernel
3. Not fully open source (since it's not embeded in the kernel)
4. IA64 doesn't really matter, since IA64 is basically dead anyway
5. No advanced recursive descent parser for conditional breakpoints

Quoted 11 lines
Quoted 6 lines
Quoted 3 lines

This is more or less completely inaccurate.

Which one -- more ? or less ?

I think Jan answered this in detail later in the thread.

Jan was very professional and interested and solicited suggestions, and got them. :-)

Jeff

Quoted 4 lines

-chirs

#15 lore raw
In reply to Jan Beulich
Quoted 1 line · Jan Beulich

While I never used or saw kdb, I'd be curious about what you immediately saw missing...

Um, you guys developed your own kernel debugger without looking at KDB first? How would you know you're not just reinventing the wheel?

Lee

#16 lore raw
Quoted 5 lines · Lee Revell
Quoted 1 line · Jan Beulich

While I never used or saw kdb, I'd be curious about what you immediately saw missing...

Um, you guys developed your own kernel debugger without looking at KDB first? How would you know you're not just reinventing the wheel?

Isnt the name "Novell ..." already a giveway? This is some kind of corporate management artifact. Someone wants to do something good for the poor Linux community that has no debuggers available and they just got something from somewhere that is going nowhere (merger?). They are in the period clueing in to opensource. Just give them some time .....

Hint to Novell Management : You own SuSE who has provided KDB with their kernel for quite some time.

#17 lore raw
In reply to Clyde Griffin
Quoted 1 line · Clyde Griffin

Patches against the mainline will be forthcoming after community feedback.

I see that the tar ball is 2.7MB in size. This is too big to effectively give any feedback on. When you create patches against the mainline kernel, please split them up into logical pieces that are each small enough to properly review.

Signature · 3 lines
The Theory of Escalating Commitment: "The cost of continuing mistakes is
borne by others, while the cost of admitting mistakes is borne by yourself."
  -- Joseph Stiglitz, Nobel Laureate in Economics
#18 lore raw
In reply to Clyde Griffin
Quoted 4 lines · Clyde Griffin

Novell engineering is introducing the Novell Linux Kernel Debugger (NLKD) as an open source project intended to provide an enhanced and robust debugging experience for Linux kernel developers.

Hmm, no backtrace, turns off kprobes, does not handle ia64 MCA/INIT. And don't get me started about the trailing white space in the patch. I'll stick with KDB for now.

#19 lore raw
In reply to Clyde Griffin

Hi!

(please wrap your lines after 72 characters or so)

Quoted 6 lines

Novell engineering is introducing the Novell Linux Kernel Debugger (NLKD) as an open source project intended to provide an enhanced and robust debugging experience for Linux kernel developers.

The project (nlkd) at http://forge.novell.com/modules/xfmod/project/?nlkd currently has code patches to SUSE Linux Enterprise Server v9 SP1 and SP2, which when applied allow kernel developers to recompile the Linux kernel exposing the functionality provided by NLKD.

Patches against the mainline will be forthcoming after community feedback.

gettingRidOfFunkyCapitalisation and rid of hungarian notation_t would be a good start. (I only seen the docs, but it has some code snippets that look very ugly).
Pavel

Signature · 1 line
teflon -- maybe it is a trademark, but it should not be.