04 April 2018, 18:32 | #41 | |
Registered User
Join Date: Apr 2012
Location: germany
Posts: 139
|
Quote:
|
|
04 April 2018, 18:51 | #42 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,598
|
Quote:
EDIT: 3F1 error makes no sense because it is debug hunk and they are supported.. Quote:
Last edited by Toni Wilen; 04 April 2018 at 19:10. |
||
04 April 2018, 20:03 | #43 |
Registered User
Join Date: Aug 2004
Location:
Posts: 3,351
|
If pressing Shift-F12 in full-screen mode causes WinUAE to crash, I think it would be better to just disable/ignore that key combination when in full-screen mode.
|
04 April 2018, 20:06 | #44 |
Banned
Join Date: Aug 2005
Location: London / Sydney
Age: 47
Posts: 20,420
|
That's a good point mark_k.
...sometimes I accidently press <Shift> + <F12> when is fullscreen mode and then have to bring up Task Manager to kill WinUAE as I'm stuck |
05 April 2018, 10:16 | #45 |
Registered User
Join Date: Aug 2014
Location: Zagreb / Croatia
Posts: 302
|
If you accidentally press <Shift>+<F12> try to exit debugger with <Alt>+<F4>.
|
05 April 2018, 10:46 | #46 |
Banned
Join Date: Aug 2005
Location: London / Sydney
Age: 47
Posts: 20,420
|
Thanks man, no sure why I never tried that standard Windows key combination before
|
05 April 2018, 10:49 | #47 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,598
|
Ctrl+C should work. (when debugger window has focus)
|
06 April 2018, 14:15 | #48 | |
Registered User
Join Date: Aug 2014
Location: Zagreb / Croatia
Posts: 302
|
Quote:
Anyway, Alt+F4 works only with GUI debugger. x+<Enter> works for both Ctrl+C only work when you are in console debugger and (to me) it was by default in GUI debugger. Alt+F4 works only with GUI debugger. When I switched from GUI to console debugger (xx command) I saw just blank debugger window without text and without prompt. I could only use Ctrl+C to exit emulation. Next time when I used WinUAE it was console debugger as default. Now when emulation is in fullscreen and I press Shift+F12 it put down emulation screen and switch to console debugger. When you going to use debugger I think that is better when emulation is in window mode because you can see what is happening in both debugger and emulation. |
|
07 April 2018, 14:38 | #49 |
Registered User
Join Date: Apr 2012
Location: germany
Posts: 139
|
thanks for upload new version. lawbreaker work now and show symbol info
I use often t or z key. maybe it is possible when use t or z key that this can work so instead of 2 key presses need only one. this can do when press return to execute t or z, the t or z command is written again in input line. so when want do a step, need only press return. if want another command, then can del the z or t in the disasm output there can with cursor up down move a box. maybe it is easy possible that with the cursor keys the disasm address can change so can scroll thru disasm output and can see previous instructions or later instructions. older dissasemble adresses can keep in a line buffer, so it is possible to look to older adresses again. |
07 April 2018, 18:40 | #50 |
Registered User
Join Date: Apr 2012
Location: germany
Posts: 139
|
Is it possible that there can add an unused opcode in a program with(define with dc.w) that it jump to debugger when this opcode appear ?(when program is start with uaedbg) ?. it is also possible to use 68k illegal instruction to jump into debugger.
|
07 April 2018, 19:42 | #51 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,598
|
$4afc (official illegal instruction) probably is best option.
|
08 April 2018, 09:02 | #52 |
Registered User
Join Date: Jul 2005
Location: -
Posts: 1,703
|
Thanks for the explanation. Interesting to learn about the internals of the program.
|
19 April 2018, 16:00 | #53 |
Registered User
Join Date: Oct 2014
Location: Berlin
Posts: 131
|
Crash with uaedbg
Hello Guys,
i have problems with this new debug-feature. With latest v4.0.0 ß 3 (and ß 2, others not tested), i start with Quickstart A3000, 3.1 ROM w/ 2MB Chip+8MB Fast. The only addition is my normal hdf. Now i open a CLI/Shell und type "uaedbg c:LawBreaker". I immediately get a Crash wich produces a MiniDump-File. I tested with amiga.lib in plugins\debugger and without -same result. Is there something missing? Invoking the non-GUI-debugger with Shift-F12 works OK, with amiga.lib also. (Loaded 'amiga.lib', 78 libraries, 1342 LVOs.) Should i attach the Dump and/or logs? |
19 April 2018, 17:04 | #54 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,598
|
GUI debugger is not supported in this mode but it still shouldn't crash so attach dump, thanks.
|
20 April 2018, 13:26 | #55 |
Registered User
Join Date: Mar 2016
Location: Australia
Posts: 934
|
In a similar theme to invalid memory accesses causing a debugger break, would it be possible to break if I try and step a floppy drive out of range?
I’m sure this feature would be useful for the 2-3 people that mess around with track loader code each decade ;-) I’d also be interested if any old track loaders ever try to do this. |
20 April 2018, 16:41 | #56 | |
Registered User
Join Date: Oct 2014
Location: Berlin
Posts: 131
|
Quote:
i think you have mistaken me. I don't expected the GUI Debugger to start. I thought if i start "uaedbg c:LawBreaker" on amiga-side from Initial CLI would bring up the non-gui-debugger but i get an crash wich generates a minidump. Its included together with winuae[boot]log.txt Hope it helps |
|
20 April 2018, 17:09 | #57 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,598
|
Quote:
There is already log message, I'll add current PC to message, it should be enough information to find where and when it happens. I have seen that message ("program tried to step over track 80") few times, some loaders do extra useless step after last track has been read and causes this message if last track was 79. Quote:
Manually adding smaller debugmem space may help: debugmem_start=0x70000000 debugmem_size=0x08000000 (or 0x04000000 or even smaller, default is very large) If it does not work: sorry, XP is unsupported. This debug method by design requires lots of RAM. (hundreds of megabytes). 64-bit OS is recommended. |
||
21 April 2018, 00:39 | #58 | |
Registered User
Join Date: Mar 2016
Location: Australia
Posts: 934
|
Quote:
I noticed that the check for stepping out beyond zero is commented out: Code:
/* else write_log (_T("program tried to step beyond track zero\n")); "no-click" programs does that */ |
|
21 April 2018, 09:13 | #59 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,598
|
Quote:
|
|
21 April 2018, 09:16 | #60 |
Registered User
Join Date: Mar 2016
Location: Australia
Posts: 934
|
Yeah, I saw that, was just wondering what the actual deal is with this. HRM says to never do that as it might cause alignment issues, yet it then goes on to say that new drives should ignore this command.
I ran no-click for years on my original A500 and had no issues ;-) Guess this is getting a bit off topic... |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Debugger updates (was: WinUAE Debugger HH PC history) | selco | support.WinUAE | 8 | 14 March 2018 22:27 |
Hacking the fs-uae console debugger | alpine9000 | Coders. Asm / Hardware | 1 | 28 March 2016 16:45 |
Added SegTracker to FS-UAE's Debugger | lallafa | support.FS-UAE | 7 | 16 January 2016 11:03 |
Amiga Segment!!! :) :) | blade002 | Amiga scene | 8 | 08 October 2015 15:00 |
SAS/C: Undefined symbols | Yesideez | Coders. C/C++ | 14 | 13 February 2014 16:36 |
|
|