mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-07-30 12:25:35 +02:00
6cd2e97470
The parser for dprintf parameters was much too simplistic and prevents real uses cases from operating. It is not necessary to remove the , between the arguments to dprintf, so don't try to split on that anymore. That also means we can't check for and error on mismatch between format specifiers and number of arguments. e.g. "===> XML_EVENT_TEXT(%s)\n", (char *)strtok(Text,"\n") should be permitted. The alternative would be to write a more complete parser for both the printf specification and the arguments. Well out of scope and unnecessary. Some inputs may now be accepted by the GUI and then when inserted with GDB fail. These errors are displayed in the GUI already anyway. |
||
|---|---|---|
| .. | ||
| CDT-10.0-CTAD.jpg | ||
| CDT-10.0-new_terminal_colors.png | ||
| CDT-10.0-new_terminal_colors_pref.png | ||
| CDT-10.1-Console_actions.png | ||
| CDT-10.2-Rename.png | ||
| CDT-10.2-Terminal-invert-colours.png | ||
| CDT-10.3-GDB_process_properties.png | ||
| CDT-10.3-Jump_to_memory.png | ||
| CDT-10.3-make_args.png | ||
| CDT-10.3-Opcode_as_byte_sequence.png | ||
| CDT-10.3-Terminal-hover-selection.png | ||
| CDT-10.3-working_sets.png | ||
| CDT-10.3-Wsl.png | ||
| CDT-10.4-outline.png | ||
| CDT-10.5-GdbPreferences.png | ||
| CDT-10.5-Smart_import_dialog.png | ||
| CDT-10.7-Gdb-extended-remote.png | ||
| CDT-11.0-dprintf-gui.png | ||
