nsw@cord.UUCP (Neil Weinstock) (02/06/89)
I was just wondering how people debugged programs that spawn off tasks. Manx SDB doesn't seem up to the task (sorry.) Does Lattice's new CodeProbe deal with it? I have had to go through some interesting contortions to figure out what was going in some of my subtasks, since I can't SDB and I can't printf. Anyone have any clever tricks (or tools) for this? /.- -- .. --. .- .-. ..- .-.. . ... .- -- .. --. .- .-. ..- .-.. . ...\ / Neil Weinstock | att!cord!nsw | "One man's garbage is another \ \ AT&T Bell Labs | nsw@cord.att.com | man's prune danish." - Harv Laser / \.- -- .. --. .- .-. ..- .-.. . ... .- -- .. --. .- .-. ..- .-.. . .../
jesup@cbmvax.UUCP (Randell Jesup) (02/07/89)
In article <686@cord.UUCP> nsw@cord.UUCP (Neil Weinstock) writes: >I was just wondering how people debugged programs that spawn off tasks. Manx >SDB doesn't seem up to the task (sorry.) Does Lattice's new CodeProbe >deal with it? I have had to go through some interesting contortions to figure >out what was going in some of my subtasks, since I can't SDB and I can't printf. Lattice 5.02 CPR can handle it. It can even catch system tasks (if it doesn't depend on them itself), like my handler, even after it's been running for a while, and bind symbols from the loadfile to the image in memory. It can catch by address or task name. -- Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup