aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base/macro-source-path.c
AgeCommit message (Collapse)AuthorFilesLines
2025-04-08Update copyright dates to include 2025Tom Tromey1-1/+1
This updates the copyright headers to include 2025. I did this by running gdb/copyright.py and then manually modifying a few files as noted by the script. Approved-By: Eli Zaretskii <eliz@gnu.org>
2024-01-12Update copyright year range in header of all files managed by GDBAndrew Burgess1-1/+1
This commit is the result of the following actions: - Running gdb/copyright.py to update all of the copyright headers to include 2024, - Manually updating a few files the copyright.py script told me to update, these files had copyright headers embedded within the file, - Regenerating gdbsupport/Makefile.in to refresh it's copyright date, - Using grep to find other files that still mentioned 2023. If these files were updated last year from 2022 to 2023 then I've updated them this year to 2024. I'm sure I've probably missed some dates. Feel free to fix them up as you spot them.
2023-01-01Update copyright year range in header of all files managed by GDBJoel Brobecker1-1/+1
This commit is the result of running the gdb/copyright.py script, which automated the update of the copyright year range for all source files managed by the GDB project to be updated to include year 2023.
2022-07-29gdb/testsuite: add macros test for source files compiled in various waysSimon Marchi1-0/+22
Using different ways of passing source file paths to compilers results n different file and directory paths in the line header. For example: - gcc foo.c - gcc ./foo.c - gcc ../cwd/foo.c - gcc $PWD/foo.c Because of this, GDB sometimes failed to look up macros. The previous patch fixed that as much as possible. This patch adds the corresponding tests. Add both a DWARF assembler-based test and a regular test. The DWARF assembled-based one tests some hard-coded debug info based on what I have observed some specific versions of gcc and clang generate. We want to make sure that GDB keeps handling all these cases correctly, even if it's not always clear whether they are really valid DWARF. Also, they will be tested no matter what the current target compiler is for a given test run. The regular test is compiled using the target compiler, so it may help find bugs when testing against some other toolchains than what was used to generate the DWARF assembler-based test. For the DWARF assembler-based test, add to testsuite/lib/dwarf.exp the necessary code to generate a DWARF5 .debug_macro section. The design of the new procs is based on what was done for rnglists and loclists. To test against a specific compiler one can use this command, for example: $ make check TESTS="gdb.base/macro-source-path.exp" RUNTESTFLAGS="CC_FOR_TARGET=clang --target_board unix/gdb:debug_flags=-gdwarf-5" Change-Id: Iab8da498e57d10cc2a3d09ea136685d9278cfcf6