JagChris Posted April 3, 2014 Share Posted April 3, 2014 ALN/SLN/RLN will all leave symbols in the output if you ask them too. GCC produces the same sort of binary files as MADMAC/ALN. Not quite sure if I have understood what you have asked me to elaborate on I think you got it. Thanks! Quote Link to comment Share on other sites More sharing options...
JagChris Posted April 3, 2014 Share Posted April 3, 2014 I see what appears to be debug flags in the smac manual. Very interesting. Quote Link to comment Share on other sites More sharing options...
JagChris Posted April 3, 2014 Share Posted April 3, 2014 (edited) Hi all, im trying to debug with skunkboard (jserve.exe and jcp) the jseve.exe looks good .. reseted skunboard, green screen, i open, and ... ---------------------- (waiting on localhost:4567) -> so far so good ---------------------- but the jcp -c stucks at: ---------------------- C:\>jcp -c jcp v02.03.01 built on Oct 14 2009 Skip 0 bytes, base addr is $4000, length is 0 bytes Finished in 0 millis, 0KB/second. Starting console... ---------------------- any ideas? did i started the tools in correct order? (remark: one time he "waited for 68k handshake" but after waiting long time i aborted) Are you sure that's updated? The latest one was built June 2013. Oh nevermind. This post is older than that. Edited April 3, 2014 by JagChris Quote Link to comment Share on other sites More sharing options...
LinkoVitch Posted April 3, 2014 Share Posted April 3, 2014 hi there, as i tested today the skunkboard console skunkWRITEFILE i noticed that it writes nothing into my dumpfile.txt and the console hangs :-( any idea? i am using windows (7) i did a very trivial test (nearly 1:1 as in the skunkboard PDF description) can someone test it with his dev env? would be helpfull so i can see if the problem is my PC http://www.hochrhein-it.de/tmp/jaguar/SkunkDebug.zip greetz to all jagcoders Otto fixed your problem It is due to the label 'testbytes' falling on an odd address. if you put .EVEN on the line before it, your code should work fine (Well it does for me ) Quote Link to comment Share on other sites More sharing options...
LinkoVitch Posted April 3, 2014 Share Posted April 3, 2014 One thing I have learnt is that a lot of weird errors are often just caused by alignment issues, be they OP, RISC, Blitter etc. The worst ones I had were writing the SoundEngine and I would add a line of code or two and the whole thing would die, even though the code I was modifying hadn't been called at that point.. then adding a NOP in an unused bit of code would fix it. Transpired that the alignment of some memory was out of alignment, but it took me a few hours to clock it! and then I had fun and games due to a bug in ALN that I had to work around So glad we now have RLN and someone actively fixing it (praise be to shamoo! ) 1 Quote Link to comment Share on other sites More sharing options...
Otto1980 Posted April 3, 2014 Author Share Posted April 3, 2014 wow.. thanks for this helpfull support the jag is 64 Bits of Power and a source for 10000000 misstakes and bugs i try it soon, but currently abroad @ work greetz 1 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.