aboutsummaryrefslogtreecommitdiff
path: root/zlib/example.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2023-01-06 10:37:10 -0500
committerSimon Marchi <simon.marchi@efficios.com>2023-01-26 14:31:33 -0500
commit4cdda229da53bde30b2a22155ee7ceb025cebc49 (patch)
treef6c8cd0c07dd21957bd70fc6f14dd4c8f151586d /zlib/example.c
parent48680a5f9d8ec2fcfa349ff2006a21b3b788b959 (diff)
downloadgdb-4cdda229da53bde30b2a22155ee7ceb025cebc49.zip
gdb-4cdda229da53bde30b2a22155ee7ceb025cebc49.tar.gz
gdb-4cdda229da53bde30b2a22155ee7ceb025cebc49.tar.bz2
gdb/testsuite/dap: write requests to gdb.log
This helps following what happens when reading gdb.log. The downside is that it becomes harder to tell what text is from GDB and what text is going to GDB, but I think that seeing responses without seeing requests is even more confusing. At least, the lines are prefix with >>>, so when you see this, you know that until the end of the line, it's something that was sent to GDB, and not GDB output. Change-Id: I1ba1acd8b16f4e64686c5ad268cc41082951c874
Diffstat (limited to 'zlib/example.c')
0 files changed, 0 insertions, 0 deletions