Worked started for the source tracing

[clinton/Virtual-Jaguar-Rx.git] / docs / vj_HistoryNotes.txt

diff --git a/docs/vj_HistoryNotes.txt b/docs/vj_HistoryNotes.txt
index 84e0b65..b39c710 100644 (file)
--- a/docs/vj_HistoryNotes.txt
+++ b/docs/vj_HistoryNotes.txt
@@ -1,6 +1,23 @@
-Release 4 (TBD)
+Release 5 (TBA)
 ---------------
-Git commit: TBD
+0) Added a date creation stamp in the application command line information
+- This date already appears in the Release 4 executable but was not referenced in his history note
+1) Added a specific breakpoint for the M68K illegal instruction exception
+-- Alert box will display a message and then the code will stop
+2) Added a specific breakpoint for the M68K address error exception
+-- Alert box will display a message and then the code will stop
+3) Added a HW registers browser window and set a tab for the Blitter
+4) Added a source tab in the main window for step into tracing
+
+Release 4a (15th August 2019)
+-----------------------------
+Git commit: f04df4f185ed4f3cfc805d0f61b3c019a108ae2c
+-
+0) Fix specific breakpoint for ROM cartridge or unknown memory location writing
+
+Release 4 (10th August 2019)
+----------------------------
+Git commit: 9b25d85d1ea4a9476b83476bcec65e05464f68da
 -
 0) The zoom value setting has been fixed in the registry
 1) Debugger mode now shares the same alpine rom path setting
@@ -89,6 +106,7 @@ Git commit: TBD
 51) Removed the sorting filter in the all watches window
 52) Fix the support of the DRAM size limit option in the heap allocation window
 53) Set cartridge view menu for debugger mode only
+54) Prevent crash in case of call stack is out of range
 
 Release 3 (13th November 2017)
 ------------------------------
@@ -210,8 +228,9 @@ Known issues
 15) After a new breakpoint set, the breakpoint list window is not refreshed
 -- User must perform an operation, such code tracing, to see the breakpoints list update
 16) Some ASCII characters may be not displayed correctly
--- It depend how the text is displayed, this is related to the QT/HTML encoding done when reading DWARF file
+-- Probably depend how the text is displayed, this is related to the QT/HTML encoding done when reading DWARF file
 17) Potential legacy crash when leaving emulator in pause mode for a long period of time
+-- Need much investigation
 
 Cosmetic / UX issues
 ====================