Debugging/Testing Methods and Suggestions

Forum thread started by onepremise on Wed, 2004-06-30 20:47

Ok, so I am just getting started and I was wondering if I could get some input from any of the guys that are currently working on the kernel. I am in the process of downloading source modules from cvs, reading the source, and getting accustom to how things are done around here. I have also looked over and read some of the resources on the website. I see most of the work is compile and built with the GNU compiler and JAM. I was wondering what environment you guys use to work in. Ex: OS ( BeOS MAX, Linux, Unix, XP) and Debugging "IDE" (DD, GNU Debbugger, etc...). Is any remote debugging ever done via serial port? Any input will help. Thanks

Comments

Re: Debugging/Testing Methods and Suggestions

by myob - 2004-06-30 21:50

onepremise wrote:

Ok, so I am just getting started and I was wondering if I could get some input from any of the guys that are currently working on the kernel. I am in the process of downloading source modules from cvs, reading the source, and getting accustom to how things are done around here. I have also looked over and read some of the resources on the website. I see most of the work is compile and built with the GNU compiler and JAM. I was wondering what environment you guys use to work in. Ex: OS ( BeOS MAX, Linux, Unix, XP) and Debugging "IDE" (DD, GNU Debbugger, etc...). Is any remote debugging ever done via serial port? Any input will help. Thanks

As far as I know, all development for the kernel on x86 is done under BeOS (don't use Max, is painful), and on PowerPC under Debian Linux. GCC is used, obviously. Currently I think the x86 progress is testing in the Bochs x86 emulator, and PowerPC on the real hardware

However, this is just based off what I've seen on the lists/IRC and not nessacerily 100% what happens

Re: Debugging/Testing Methods and Suggestions

by Jack Burton - 2004-07-02 10:44

Quote:

As far as I know, all development for the kernel on x86 is done under BeOS (don't use Max, is painful),

Actually, you can build the kernel also under linux (any gcc version should do).

Re: Debugging/Testing Methods and Suggestions

by euan - 2004-07-02 17:44

Jack Burton wrote:

Quote:

As far as I know, all development for the kernel on x86 is done under BeOS (don't use Max, is painful),

Actually, you can build the kernel also under linux (any gcc version should do).

Doesn't it need to be 2.x something to retain binary compatibility?

Re: Debugging/Testing Methods and Suggestions

by myob - 2004-07-02 23:20

Jack Burton wrote:

Quote:

As far as I know, all development for the kernel on x86 is done under BeOS (don't use Max, is painful),

Actually, you can build the kernel also under linux (any gcc version should do).

I did mention that it done under Linux for PowerPC, its just that Axel develops under BeOS on x86....

The Linux kernel can also be built under BeOS :D :D :D

Re: Debugging/Testing Methods and Suggestions

by Jack Burton - 2004-07-04 09:38

euan wrote:

Doesn't it need to be 2.x something to retain binary compatibility?

Shouldn't matter for the kernel. The kernel API is C, so shouldn't be an issue to compile it with the latest GCC.

Debugging/Testing Methods and Suggestions

by onepremise - 2004-07-09 20:24

I am having a difficult time trying to sort through some binaries required for building. It seems some precompiled files are required for the build. These files look like they are native to BeOS R5 PE. Im not sure where to get them or what version I need. When I compile I get this:

dhp1171:~/BEOS/current root# jam
don't know how to make boot_arch_stage2.o
...patience...
don't know how to make /boot/develop/lib/x86/_KERNEL_
...patience...
...patience...
...patience...
...patience...
...patience...
don't know how to make /system/servers/input_server
...patience...
don't know how to make ./objects/ppc.R1/kernel/kernel.so
...patience...
don't know how to make /boot/develop/lib/x86/libpdf.a
...patience...

Where can I find these dependencies? You guys mention building under Linux, but it seems this project is setup to build under the BeOS only. What is required to get this to build under linux outside of the development tools mentioned on this site?