Quote:

Well, see that's the problem: Money is not a big deal for someone like me, rather it is the question if I'm able to actually do it at all. If I'm able to, I'll do it no matter if there is a bounty or not, but if it turns out I can't do it, well, money is not going to help a lot here...

@abalaban

Talking about feature requests, the amigabounty team
seems to be thinking about opening a bounty on a
source debugger with gui such as db101. I this becomes
a reality, I would like to ask people in here, what they
want/need from such a program so that the bounty can
be guided towards the people and not vice versa.

So... What do you all want??

EDIT: Passing of arguments will be added as soon as I get back home.

New version of DEbug 101 uploaded. See original post for details.

@abalaban

Thanks for the pointer, it has been solved (me thinks).

@kas1e

Nice screenshot

1) I have added path-memory to the asl-requester.

2) I totally agree with you, that it would be nice with more developers to contribute to the problem, after all, I'm just a lazy no-good amateur with a lot of spare time . Also, adding it to Codebench (once it is done) was one of my initial thoughts.

3) I might try and add a simple disassembler and breakpoints at absolute memory locations. For the rest of the parts, I'm pretty stuck at the moment not knowing how to read and interpret debug info from object files. I was hoping, that someone in here had some knowledge to share, but maybe that's not the case...

@tonyw

Doh! I need to start reading the docs properly... Thanks!

@kas1e

I can explain a little: It is just a very small app, that can load a module, set a breakpoint and run/pause the app. Ideally it should also be able to crash the app, so you can read the stacktrace etc in the grim reaper, but that part doesn't work for some reason.

I want to be able to single step through the code when it has paused, but for that I need to be able to read and understand debug info, and that's where I'm stuck for now.


EDIT: and yes, it has a gui!

Version 0.9 of Debug 101 is now available:

http://dl.dropbox.com/u/5482530/Code%20examples/db101.lha

Added since version 0.8:

- Arexx port
- Arexx console
- Bugfixes and more

Added features since version 0.7:

- Attach mode
- Breakpoint window doesn't block
- Lots of internal changes

Added features since version 0.6:

- Interpretation of typedefs (experimental)
- Correct type-relative printing of variables
- Reading of global variables
- Read fp regs

Added features since version 0.5:

- Complete restructure of breakpoint system
- Correct handling of loops (experimental)
- Asm step and asm skip
- Tonnes of bugfixes
- Several other small things


Problems:

There are some problems with elf.library.kmod in AmigaOS Update 1 and Update 2, so from this version it is only going to work with a pre-update 1 elf.library or with the latest beta version (53.13). Sorry for this, but there is no workaround .

There is also a problem with the msr register, which means, that if you by any chance place a breakpoint on top of a branch, things are going to mess up. Sorry, this is also not my fault!

There is a problem with the gnu linker, which means that reading of type definitions doesn't work properly for executables consisting of more than one source file.

@ssolie

I had managed to copy my example code from probably the only SDK example that doesn't define GA_RelVerify for a button...

@Rigo

Thanks!

I'm trying to get into reaction, and my first test
is this:

http://dl.dropbox.com/u/5482530/Code%20examples/reaction/test.c

I'm curious to know, what I am doing wrong here. The button never reacts to input, and printf("hello world\n"); is never called. What am I doing wrong???

@joerg

Quote:

First of all I wouldn't count on me getting QtWebKit to run properly. I'm a lazy no good amateur, and besides I'm starting in school again so my time is going to be limited from now on. (Working on Qt was never intended to be very serious, just for my own pleasure and curiosity.)

Second of all, OWB will always have advantages over QtWebKit: Fast startup time (Qt is a sloow starter because it needs so many shared libraries), size (libQtWekKit.so is over 70 mb), accessability (there is going to be no native qt from me, so we are stuck with amicygnix, which scares many people away) and probably lots of other things.

The Qt Browser at it's current state is just not good enough, and I think I have pretty much reached the level, where further improvement is going to be hard. Sorry.

@joerg

Thanks Joerg . I must be needing glasses...

@Slayer

Actually I'm not sure that I know what is going on with OWB. My own project is just to get the Qt WebKit module to work, and for that purpose I'm "stealing" small snips of code from OWB.

@joerg

Quote:

I have downloaded pukapuka, and I can find neither MarkStackAmigaos4.cpp nor MarkStackNone.cpp in the archive. How is it supposed to look?

Here's the link:
http://dl.dropbox.com/u/5482530/Qt/vacuum.lha

Requires the latest qt user package from os4depot:
http://os4depot.net/?function=showfil ... /qt-amicygnix-user.tar.gz

I have compiled vacuum, and it runs, but I have no idea how it is supposed to work... Is anyone up for a test run?
Anyways, it's going to take a few days before I can upload, since I messed up smth and has to recompile WebKit (it takes little more than 24 hours).

@thomas

UnitControl doesn't do anything (only grey lists and buttons except for "rescan", which doesn't seem to do anything). I've tried with a newer application called q-device, which probes the controller, but the units never show up. It works fine with a DVD-drive connected to the internal IDE port.

Of course I'm not just trying "random" jumper settings, I'm just testing fx. different ID settings and so. And just to be sure: The red line of the cable goes with pin 1 on the connector, right??

There is a jumper saying smth with "termination", and I keep this on. I'm guessing this is right? Anyways, I know I left the drive in a working state back when I lost the original cable, so I'm guessing that amigakit sent me a defective cable.

I'm only going to try flash update as a very last resort because of bad memories with it... Is there a way to check which update is already installed without actually installing a new one?

@Vulture

I've tried in the SCSI boot menu to manually mount the device (should be unit 0 from the jumpers), but it doesn't change anything. The drive doesn't react and on boot it says that it cannot open blizzppc.device unit 0. By the way I've tried every other unit from 0 to 7, but nothing changes.

As far as I recall - from about 10 years back - it was pretty much plug-and-go for the drive to work. It could be a defective cable, who knows.

I have a few options to try still before returning the cable:

a) update the firmware
This is not a very pleasant option, since that was exactly what trashed my board back then. Anyhow, I can't get any of my old floppies to work (the update needs to run from floppy),
or maybe my floppy drive is defect, so that's pretty much no go.

b) try updating my roms to 3.1 and see if that helps. I have my doubts...

c) try more jumper/cable combinations. I think I already tried them all so, hey....

d) dunno what else to do..........

So I just got a fresh new cable for the scsi connector
on my old blizzppc 603 board. Trying to connect 2 different
CD-rom drives to the connector has failed miserably, so I think I need some help...

The "SCSI" menu of the blizzppc boot menu (ESC while boot) doesn't seem to find any devices no matter how I connect them. The scsiconfig program doesn't pick up on either devices or the controller.

Is there anything I can do to test if the controller itself is actually working or not? Is it possible to find the original phase 5 software anywhere on the web? Help!