diff --git a/source/asserts/nucleistudio/advanceusage/disassembly-linkage.png b/source/asserts/nucleistudio/advanceusage/disassembly-linkage.png new file mode 100644 index 0000000..348302c Binary files /dev/null and b/source/asserts/nucleistudio/advanceusage/disassembly-linkage.png differ diff --git a/source/asserts/nucleistudio/advanceusage/register-filter.png b/source/asserts/nucleistudio/advanceusage/register-filter.png new file mode 100644 index 0000000..c67ca4e Binary files /dev/null and b/source/asserts/nucleistudio/advanceusage/register-filter.png differ diff --git a/source/asserts/nucleistudio/known/gprof-error-diagnostic.png b/source/asserts/nucleistudio/known/gprof-error-diagnostic.png new file mode 100644 index 0000000..78ad124 Binary files /dev/null and b/source/asserts/nucleistudio/known/gprof-error-diagnostic.png differ diff --git a/source/asserts/nucleistudio/known/ld-link-nonexistent.png b/source/asserts/nucleistudio/known/ld-link-nonexistent.png new file mode 100644 index 0000000..5115437 Binary files /dev/null and b/source/asserts/nucleistudio/known/ld-link-nonexistent.png differ diff --git a/source/ide/advanceusage.rst b/source/ide/advanceusage.rst index 5c931d6..42d7120 100644 --- a/source/ide/advanceusage.rst +++ b/source/ide/advanceusage.rst @@ -2443,6 +2443,26 @@ Nuclei Studio 2026.10 adds support for the RISC-V Big Endian toolchain, so that Then build the project; the generated code and ELF files are big-endian. +.. _ide_register_view_filter: + +Register View Filter +-------------------- + +A filter box has been added to the Registers view (and the Variables view). During debugging, enter a keyword in the filter box to narrow the register list down to the matching registers, so you can quickly locate the registers you want to view without scrolling through the full list. A counter is displayed next to the filter box while filtering (for example, ``1/9``), indicating how many registers match and which one is currently selected. + +|register-filter| + +.. _ide_disassembly_c_linkage: + +Disassembly View C Code Linkage +------------------------------- + +The Disassembly view is now linked with the C/C++ editor: + +- Clicking a line in the C source file makes the Disassembly view jump to the corresponding instructions and highlight them; +- When the editor navigates to another source file (for example, by following a function call), the Disassembly view follows and displays the disassembly of the corresponding content. + +|disassembly-linkage| .. |image1| image:: /asserts/nucleistudio/advanceusage/image2.png @@ -2827,3 +2847,7 @@ Then build the project; the generated code and ELF files are big-endian. .. |image-be-1| image:: /asserts/nucleistudio/advanceusage/big-endian-1.png .. |image-be-2| image:: /asserts/nucleistudio/advanceusage/big-endian-2.png + +.. |register-filter| image:: /asserts/nucleistudio/advanceusage/register-filter.png + +.. |disassembly-linkage| image:: /asserts/nucleistudio/advanceusage/disassembly-linkage.png diff --git a/source/ide/index.rst b/source/ide/index.rst index 8c007d0..6616312 100644 --- a/source/ide/index.rst +++ b/source/ide/index.rst @@ -17,3 +17,4 @@ Nuclei Studio IDE advanceusage.rst update.rst faq.rst + known.rst diff --git a/source/ide/intro.rst b/source/ide/intro.rst index bb76a99..deb0965 100644 --- a/source/ide/intro.rst +++ b/source/ide/intro.rst @@ -192,6 +192,16 @@ Nuclei Studio 2026.10 adds support for the RISC-V Big Endian toolchain (this fea For details, see :ref:`Big Endian Compiler Support `. +Added Register View Filter +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +A filter box has been added to the Registers view, so you can quickly locate the registers you want to inspect by entering a keyword during debugging. For details, see :ref:`Register View Filter `. + +Added Disassembly View C Code Linkage +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The Disassembly view is now linked with the C source editor: clicking a line in the C file makes the Disassembly view jump to the corresponding instructions and highlight them, and navigating to another source file makes the Disassembly view follow. For details, see :ref:`Disassembly View C Code Linkage `. + Fixed Known Bugs ~~~~~~~~~~~~~~~~~ @@ -205,6 +215,14 @@ Fixed Known Bugs - Fixed that running clean on large projects failed because the generated command line (such as ``rm`` or compile commands) was too long; +- Fixed the issue where modifying the Nuclei Settings page did not trigger automatic synchronization of the model; + +- Fixed the issue where QEMU could not run n100 programs properly on the IDE; + +- Fixed the incorrect and incomplete layout in the New Project Wizard; + +- Fixed the incorrect display of the Language standard option in the project Settings; + - Fixed other known bugs. diff --git a/source/ide/known.rst b/source/ide/known.rst new file mode 100644 index 0000000..0024a67 --- /dev/null +++ b/source/ide/known.rst @@ -0,0 +1,47 @@ +Known Issues +============ + +.. _ide_known_issues: + +This page records known defects and issues that are being tracked, grouped by release version. + +Known Issues in 2026.10 +----------------------- + +Generate gprof Tool Has No Response +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +When the **Generate gprof** tool appears to produce no response, the usual cause is insufficient heap memory on the target: ``-pg`` (gprof) and ``-coverage`` (gcov) both allocate memory at runtime, so enabling them together may exhaust the heap. In this case the target only prints errors such as ``monstartup: out of memory`` or ``gprof_collect: unable to malloc enough memory to store gprof data``, and ``gmon.out`` is never generated. + +Therefore, test gprof and gcov separately: build and run with ``-pg`` alone for gprof, and with ``-coverage`` alone for gcov, instead of enabling both at the same time. + +Nuclei Studio 2026.10 also improves the error feedback of profiling. Errors found in the analyzed output are captured and shown in a **Profiling Error Diagnostic** dialog together with suggestions. The dialog is titled ``Profiling Error Diagnostic``, and its body begins with ``Errors were found in the analyzed output, please check the suggestions below.`` (or ``...no files have been generated.`` when no output file was produced). + +The diagnostic recognizes the following errors (each is a concise, de-duplicated message): + +* **Heap memory insufficient (gmon.out)** — ``Failed to generate gmon.out, because the heap memory is insufficient.`` + Matched from ``monstartup: out of memory`` or ``gprof_collect: unable to malloc enough memory to store gprof data``. + +* **Heap memory insufficient (.gcda file)** — ``Failed to generate , because the heap memory is insufficient.`` + Matched from ``Can't allocate gcda buffer for ``. + +* **Call-arc table overflow** — ``gmon.out may be incomplete, because the call-arc table overflowed (tos overflow); some call relations were lost.`` + Matched from ``mcount: tos overflow`` or ``_mcleanup: tos overflow``. This message is shown only when no heap error is present; when a heap error occurs, the overflow is treated as a cascade of the heap error and is suppressed. + +* **File open failure** — ``Failed to generate , because the file could not be opened on the target (check semihosting / file system).`` + Matched from ``Unable to open ``. If the same file already reports a heap error, this message is suppressed to avoid contradictory prompts for that file. + +.. figure:: /asserts/nucleistudio/known/gprof-error-diagnostic.png + +Linker Script Selected via File System Displayed as Non-existent +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In Nuclei Studio 2026.10, an issue was fixed where a linker script (``.ld``) selected through **File System** was incorrectly displayed as ``non-existent`` in Nuclei Settings. + +The root cause is that Nuclei Settings resolves the selected ``.ld`` file as a regular file. If the selected file is a linked file, or the path contains linked folders, the file cannot be located and is therefore reported as ``non-existent``. The same applies to virtual files and folders. + +As shown in the figure below, the icon in Project Explorer indicates that ``gcc_evalsoc_ilm.ld`` is a linked file, yet the Linker Script field still reports it as non-existent. + +.. figure:: /asserts/nucleistudio/known/ld-link-nonexistent.png + +