At least! nice one!

SOunds like it could be very useful. A screenshot would be nice! (I see there is an ancient one on OS4Depot - perhaps a newer one could be added?)

@ChrisH
I upload new one yesterday to os4depot, but it still not in. If you in interest, there is: db101_v1_screen

db101 in general can be improved more of course (gui and some stuff for core itself), but that new version are pretty stable and helpfull: You can set breakpoints in easy "gui" way (see those labels on screen, in the source window), you can do different kind of steps: step to fucntion, step out, step over, asm steps (per instructions), can continue till next bp or to end, can send signals, have command line (currently simply, but still) mode by which you can set breaks on addresse and co, can even attach to avail processes (currently not very helpfull anyway).

Alfkil also spend plenty of time to make entering to new areas (like kernel ones, newlib ones and co), painfull free : nice window with warnings, remembering of states, ability to see local/global/and all kind of the variables, registers and co. Loading of binary with or without command line arguments, and so on.

My wish list for the next versions is:

-- impove gui a bit and add RMB support (prefs and stuff)
-- add support of relocation symbols (latest GDB can do it, but our one are not, and need to use objdump for).
-- maybe rework hexdump and breakpoint windowses, to make it more easy to navigate.
-- make a stack trace working
-- cosmetic stuff: make a text propotional (you can see in screenshot, that hex-dump are non proportional)
-- and some others which i do not remember for now

But even current version are cool. Now, need ppls who will test it in real lifes, and bring all bug report to Alfkil, so he can fix/improve stuff. And autor of CodeBench to try to add it and ask for imporvements for.

HUGE!!!

This is so great that I'll try it myself, even if I'm not a developer

Thanks Alfkil. It was really needed to help in debugging.

Massive news for developers but also for final user at the end = potentially better and stable apps for all

Yes, congrats and thanks, Alfkil!

Looking forward to checking this version out - sorry I had too little time lately to test the previous betas.

Keep up the good work!

Best regards,

Niels

@samo79

Quote:

It also means faster debugging, which could potentially speed up development a fair bit.

Hans

I had very high hopes for this when I saw the news item appear, and couldn't wait to try it out. Unfortunately, I don't seem to be able to get it to stop at a breakpoint here. I start db101 and load my stabs enabled executable. I select the source file I want, then struggle to find the function I want to stop at. Once I eventually found it, I click the checkbox, then hit "Start". The program starts, and eveything is good, but the function with the breakpoint is executaed and the debugger fails to notice, and it doesn't stop.

Also the "Breaks" window could do with sorting in alphabetical order to make it eaier to find the function the user is looking for.

On that note, a separate window showing the functions in the current source file would be a great help too, and would make it much easier to set breakpoints in a function. Most coders know which source a function is in, but code can be long sometimes, so listing the functions would be much better than scrolling through the source to find it.

It looks great so far though.

Simon

Is this one usable for stupid programmers like myself?
One who doesn't know what he is doing

@Rigo

I tested it only on peg2, and as far as i know alfkil have Sam. If you have any kind of A1 or x1000, then maybe there need to do something about as well .. Or maybe something related to many sources in one binary (i tested it on peg2 only with 1 binary = 1 source).

Write plz mail to Alfkil, he 100% in interest to fix it. Will be nice to have CodeBench with integrated db101.

@Antique

Knowing of basics is necessary with debugger: a bit of assembler, C, a bit of HW details (like what is registers and so on). And more you know about, the easy to use debuggers.

Quote:
I'm just sorry I don't have much time to get more done on the kernel API side of things. As Trevor would say, "Stay tuned."

Rigo, does the helloworld example behave the same?
I tried with it and it stops at breakpoints (on Sam460).

@Elwood
Alfkil says that its all can be because he forget to add x1000-related breakpoint code. I.e. it's because the X1000 is a 64-bit, and the breakpoints code
he is using uses a 32-bit instruction to set the msr register.

Thats all of course, if Rigo tryed it on x1000

Yes, I've recently moved my development environment over to X1000, which is where I tested db101. If alfkill needs an X1000 tester, tell him to mail me (although time is very limited right now).

Simon

@Simon
Quote:
Done