Lines Matching +refs:po +refs:show +refs:source +refs:path
400 source or destination registers and their respective qualifiers.
459 Add generated source files and fix thinko in aarch64-asm.c
788 number of source operands and one destination operand at this time.
1570 path that was just completed is a directory. However, if I instead
1602 path starting with a tilde character.
1615 allows me to give a unique test name, that doesn't include the path
1772 consequently the backtrace show foobar instead foo.
2058 compiler (equivalent to hard-coding the library path into the name
2612 vfork+exec code path.
2960 Avoid language-based lookups in startup path
3013 many cases, the prompt can show up early, making gdb feel more
3800 4) Check out */po/*.pot which we don't update frequently.
4049 line of source code, GDB stops in the middle of the line. Thus requiring
4060 The source line looks like:
4223 The two distinct ranges are generated because GCC started outputting source
5752 Even though it has an "else" path that calls this error function.
6109 so people can understand the original source file.
6117 pragmas, we can point people to the original source files.
6140 The TUI status window is called the "locator" in the source, but
6147 documentation, but not in the source. There, the relevant files are
6617 without this fix, but that's just a concidence, there's a code path
7317 always show the initial value (here 0), while the user would
7456 * Some of the dmulh insns were multiplying one of the source regs
7457 against itself instead of against the other source reg.
7674 When generating semantics.c from .igen source files, indenting the code
7980 exercise the code path.
9317 - the source for the current frame,
9318 - the source for main, or
9615 source charset don't affect the DWARF index.
9835 gdb/testsuite: Update worker thread show assertion
9989 path but costing less elsewhere.
10014 determine whether the current source tree is a dev build (e.g.
10094 If the GDBINIT or GDBINIT_DIR path during configuration
10096 as it interpreted the '@' in the path as a start of a command
10097 when expanding the path in the docs.
10099 This patch simply escapes any '@' characters in the path,
10104 an '@' in the workspace path.
10280 core. "maint show worker-threads" correctly reported eight and one
10288 The next commit wants to use a 'show' command within an early
10296 uiout (e.g. 'show' commands) will end up dereferencing a nullptr, and
10318 'source' commands are acceptable. But now, if a user does try a
10319 'show' command, then instead of crashing, GDB will do something
10651 is the new failure path in proc test_gdb_complete_tab_unique, which
11291 I noticed in gdb/tui/tui-stack.c a source-level micro-optimization where
11485 ideally like to have reproducible builds: for the same source,
13275 The problem is that for the source window:
13350 cannot increase the source window height to the point that the command window
13374 source py-missing-debug.py^M
13386 (gdb) FAIL: $exp: source python script
13983 comparing the results will always show the file having changed.
14021 and so show no change as having happened.
14220 * testsuite/gas/bpf/asm-extra-sym-1.s: New test source.
14316 Hannes' patch to show local variables in the TUI pointed out that
14449 (The mnemonic suffix describes the source operand, not the destination
14765 Remove path name from test case
14766 'runtest' complains about a path in a test name, from the new test
14812 also show the variables from outer frames. DAP doesn't directly
15169 For the elfread.c path there should be no user visible changes after
15172 For the coffread.c path GDB will now attempt to perform a debuginfod
15431 - the associated "set/show remote thread-events-packet" command,
15838 exited" path.
15926 The null_ptid check fails however when this path is taken:
16820 source instead of branch target) when optimizing away BTI stubs in
17266 * po/bfd.pot: Regenerate.
17281 * po/bfd.pot: Regenerate.
17295 * po/bfd.pot: Regenerate.
17710 * testsuite/ld-scripts/fill2.t: New test source.
18036 * testsuite/ld-scripts/sort-file-reversed-1.t: New test source.
18037 * testsuite/ld-scripts/sort-file-reversed-2.t: New test source.
18040 * testsuite/ld-scripts/sort-sections-reversed-1.t: New test source.
18041 * testsuite/ld-scripts/sort-sections-reversed-2.t: New test source.
18044 * testsuite/ld-scripts/sort-sections-reversed-3.t: New test source.
18080 The problem is the filename_for_id which is the source file prefixed with the
18081 compilation dir rather than the source dir.
18881 bfd to show programming errors in bfd.
18893 [gdb/cli] Add gnu-source-highlight selftest
18894 Add a selftest gnu-source-highlight:
18896 $ gdb -q -batch -ex "maint selftest gnu-source-highlight"
18897 Running selftest gnu-source-highlight.
19128 [gdb/cli] Allow source-highlight to autodetect language
19129 Currently when gdb asks the source-highlight library to highlight a file, it
19137 python pygments, and in absence of that, unhighlighted source text.
19142 Add the same capability when using the source-highlight library.
19148 - checking that source-highlight still manages to highlight a hello world.
19438 the source of the move was.
19841 source-highlight library.
21076 - Stopped passing 'nowarnings' flag when building the source file.
21077 I see no reason why this source should issue a warning,
21163 gdb -ex 'set sysroot' --args /tmp/show-args
21164 Reading symbols from /tmp/show-args...
21165 (gdb) target extended-remote | gdbserver --once --multi - /tmp/show-args
21166 Remote debugging using | gdbserver --once --multi - /tmp/show-args
21168 Process /tmp/show-args created; pid = 176054
21177 Starting program: /tmp/show-args \'
21179 Process /tmp/show-args created; pid = 176088
21181 /tmp/show-args
21188 Starting program: /tmp/show-args \'
21190 /tmp/show-args
21242 gdb -ex 'set sysroot' --args /tmp/show-args
21243 Reading symbols from /tmp/show-args...
21244 (gdb) target extended-remote | gdbserver --once --multi - /tmp/show-args
21245 Remote debugging using | gdbserver --once --multi - /tmp/show-args
21247 Process /tmp/show-args created; pid = 176054
21256 Starting program: /tmp/show-args \'
21258 Process /tmp/show-args created; pid = 176088
21260 /tmp/show-args
21267 Starting program: /tmp/show-args \'
21269 /tmp/show-args
21281 used with the "set args" command is just to show GDB that the single
21656 delete_inferior -> ~program_space path, we see that the current
22841 gdb: Add command 'maint set/show debuginfod download-sections'
23198 If you provided some relative path to the shared library, such as
23220 'thread_local' could be used in place of '__thread' in the C source
23228 the source file, so I moved this linker option to 'ldflags='.
23262 Updated show usage for MicroBlaze specific assembler options
23522 whole new path, or if GDB just spotted that the executable changed on
23648 path to the executable for this program space, or None if no
23651 The path within this attribute will be set by the "exec-file" and/or
23801 other test-cases that source unwind-on-each-insn.exp.tcl and use a .s file.
24746 ld: write resolved path to included file to dependency-file
24749 This is before include-path processing so the tracked dependency
24752 Instead track the opened file at the point where the resolved path is
24781 gdb/dap: only include sourceReference if file path does not exist
24783 included in a Source object, then the DAP client _must_ make a "source"
24785 object also includes path information.
24787 If the Source's path field is a valid path that the DAP client is able
24791 display those contents as a file with the name in "source.path", but
24792 this will conflict with the _acutal_ existing file at "source.path").
24794 Instead, only set "sourceReference" if the source file path does not
24801 gdb/dap: use breakpoint fullname to resolve source
24802 If the breakpoint has a fullname, use that as the source path when
24803 resolving the breakpoint source information. This is consistent with
24820 gdb/dap: check for breakpoint source before unpacking
24821 Not all breakpoints have a source location. For example, a breakpoint
24823 "source" will be None, which leads to a RuntimeError when attempting to
24827 breakpoint, ensure that the source information is not None. Also
24828 populate the source and line information separately from the
25807 A user pointed out that if a DAP setBreakpoints request has a 'source'
25811 While SourceBreakpoint does not allow 'source' in the spec, it seems
25813 "Postel's Law" path -- after all, we have the type-checker -- but at
26192 than the test's source file, changes to the C++ runtime could cause
26271 were written in the source code of tests. These were usually dummy
26710 error path.
27364 x86: correct source used for two non-AVX512 VEXWIG tests
27760 vms-alpha: Free memory on failure path
27769 or some obstack so that it doesn't show as a memory leak on exit.
27781 --input_line_pointer might have caused the following source line to be
28045 using "maint print symbols -source $srcfile", but dwz has moved the typedef to
28046 a PU, so it's shown by "maint print symbols -source <unknown>" instead.
28048 Fix this by dropping the "-source $srcfile" bit.
28120 objdump: Free sorted_syms on error path
29406 padding is added before pi to show that the actual address of pi and
29590 …(display_debug_ranges): Only show debug ranges whose version is suitable for the secction being di…
30441 source bit, despite operating on registers. If BPF_SRC_X (=1) is set,
30481 and writing core files. This also enables readelf/objdump to show the
30678 different directory by default than opcodes, and I had my source
30682 sources in the build dir rather than the source dir. Fix that by
30695 * cris/local.mk: Add $(srcdir) to paths for regenerated source.
30879 the source for debugging, but don't want it for comments in bfd.pot
30880 (because then bfd.pot will likely reference Nick's source tree).
30891 (po/SRC-POTFILES.in): uniq SRC_POTFILES.
30892 (po/BLD-POTFILES.in): uniq BFD_POTFILES.
30894 * po/Make-in (bfd.pot): Edit out source dir from comments.
30895 * po/SRC-POTFILES.in: Regenerate.
30899 * po/POTFILES.in: Regenerate.
31255 The reason that these failures don't show up when run on the standard
31410 path, this should still address the issue seen in b1e0126ec56e,
31489 source.
31937 mt print symbols [-objfile OBJFILE] [-source SOURCE] [--] [OUTFILE]
31949 mt print psymbols [-objfile OBJFILE] [-source SOURCE] [--] [OUTFILE]
32158 the "next" commands. I've had some test runs which don't show the bug
32215 to show up. Anyone wishing to investigate those other failures should
32402 Fix hppa64-hpux11 build to remove source paths from embedded path.
32404 paths that were specified with the -L option from the embedded path.
32753 c++: source position of lambda captures [PR84471]
32875 binary shrinks by almost a third (the generated source code shrinks by
33197 Fix this by replacing "-objfile enqueued-cu-base-addr" with "-source cu2".
33253 The 32-bit non-fetching atomic instructions treat the source register as
33264 * testsuite/gas/bpf/atomic-be-pseudoc.d: Use "w" for source reg
33275 show debug breakpoint
33818 The test-case gdb.base/index-cache.exp uses only one source file, which
33831 - adding another source file containing function foo, and
34203 (gdb) show index-cache enabled
34984 Implement DAP "source" request
34985 This implements the DAP "source" request. I renamed the
35006 Don't supply DAP 'path' for non-file shared libraries
35007 The DAP 'module' event may include a 'path' component. I noticed that
35104 would include a relative path name for the "path" component.
35114 have a separate method to return the full path to the source file.
35178 Add note to check that all changes have been pushed before creating the source tarballs
35604 * testsuite/gas/bpf/jump-relax-ja.s: And corresponding source.
35607 * testsuite/gas/bpf/jump-relax-jump.s: And corresponding source.
35997 `.module mips4' pseudo-op within the source itself so as to avoid
36271 * testsuite/ld-mips-elf/sections.s: New test source.
36873 instructions to not use their source registers.
38205 can show that these are required, it will be easy to revert this one
38227 dependent, as such, they don't always show up. I've had more success
38229 copies of the test in parallel, then the bugs would normally show up
40147 use the 'lseek + read|write' path if the offset would be negative.
40326 The alternative is 1 byte shorter when the source is %xmm0-7, as a
40392 block, and then a message to show how many more were elided (if any).
40412 The new use is still not on a hot path -- it's going to be a Python
40689 source of a recent kernel. The code mentioned in the lkml.org posting
41796 objdump/readelf will show the following message to the user if .sframe
42643 other one to match the source code line number that is shown by GDB right
42808 DAP allows a source breakpoint to specify a log message. When this is
43016 - in order for tuiterm to show something, its input processing procs need to
43095 success path.
43780 (do_s_func): Likewise on error path. strdup label.
44168 Note that the copyright dates on the new test source file are not
44326 won't necessarily show up in other distributions or even past or
44343 No source file named src/util.c.
45121 on set_group_contents failure return path.
45581 plugin claimfile lost symbol with source
45582 plugin claimfile replace symbol with source
45583 plugin claimfile resolve symbol with source
45584 plugin 2 with source lib
45585 load plugin 2 with source
45586 plugin 3 with source lib
45587 load plugin 3 with source
45820 [gdb/tui] Fix help text of show tui tab-width
45823 (gdb) help show tui tab-width
46100 failure path. Move declaration to..
46263 I got a source window with only one line in it, and the cmd window taking most
47816 If a header file defining a static function is included in multiple source
48302 I started down the path of attempting to fix
48409 Porting the fix to the mi-mode code path resolved the issue.
48479 file, which was then injected into another source file within a .asm
48501 for one of the functions in the source file, and as a consequence GDB
49071 [gdb/tui] Don't show line number for lines not in source file
49072 Currently, for a source file containing only 5 lines, we also show line
49073 numbers 6 and 7 if they're in scope of the source window:
49075 0 +-compact-source.c----------------+
49084 Fix this by not showing line numbers not in a source file, such that we have instead:
49086 0 +-compact-source.c----------------+
49633 First argument of $_gdb_maint_setting must be a valid setting of the 'show' command.
49635 Notice that GDB claims I need to use a setting from the 'show'
49637 need to use a setting from 'maintenance show'.
49722 (gdb) show width
49729 (gdb) show width
50029 [gdb/tui] Fix tui compact-source a bit more
50030 Andrew pointed out that the behaviour as tested in gdb.tui/compact-source.exp
50033 0 +-compact-source.c--------------------------------------------------------+
50044 The last line number in the source file is 5, and there are 7 lines to display
50045 source lines, so if we'd scroll all the way down, the first line number in the
50046 source window would be 5, and the last one would be 11.
50143 [gdb/tui] Fix tui compact-source
50151 With compact-source off:
50156 -ex "set tui compact-source off" \
50170 but with compact-source on:
50182 There are a couple of problems with compact-source.
50187 source text at the next tab stop; the compact display uses only as
50189 only a single space to separate the line numbers from the source.
50193 source doesn't start at a tab stop, instead it uses a single space to separate
50194 the line numbers from the source.
50202 The abbreviation is due to allocating space for <lines in source>, which is
50205 max (<lines in source>, <last line in window>), which in this example takes 2
50215 It could be the trailing space that's mentioned in tui-source.h:
50247 With the fixes, we get for compact-source on:
50260 compact-source.
51147 bfd/doc/chew.c extracts documentation from source code comments
51150 adding things like CODE_FRAGMENT to the source to put code into bfd.h
51321 I guess, as the source file has the '.cc' extension, all the compilers
51322 are doing the right thing anyway -- the source file uses templates, so
51445 $ TERM=xterm gdb -ex "show width" -ex q
51447 $ TERM=ansi gdb -ex "show width" -ex q
51729 gdb: make set/show inferior-tty work with $_gdb_setting_str
51730 Like the previous two commits, this commit fixes set/show inferior-tty
51744 gdb: make set/show cwd work with $_gdb_setting_str
51745 The previous commit fixed set/show args when used with
51746 $_gdb_setting_str, this commit fixes set/show cwd.
51757 gdb: make set/show args work with $_gdb_setting_str
51762 (gdb) show args
51781 Luckily, the fix is pretty easy, set/show variables have an
51786 While working on set/show args I also rewrote show_args_command to
51799 cmd_list_element object when the set/show command is created, and we
52432 place. The user created breakpoints include the path to the source
52566 for both syntaxes in the same source.
52601 syntax. Instruction formats can be mixed in the source program: the
53003 PASS: gdb.tui/main.exp: show main after file
53505 setting. The source of truth is really current_language and
53788 path.
54255 to generate the man pages from the source.
54479 which is the path that handles the "restore PC after a displaced step in
54824 source window.
54914 The commit 1b6d4bb2232 ("Redraw both spaces between line numbers and source
54979 commit 9e820dec13e ("Use a curses pad for source and disassembly windows"),
54982 This also changes the source window from:
54999 [gdb/tui] Add maint set/show tui-left-margin-verbose
55001 - tui_source_window (the source window), and
55006 With a hello world a.out, we can see the source window:
55033 giving us this for the source window:
55064 between line numbers and source code"), we have:
55580 Type "show copying" and "show warranty" for details.
55582 Type "show configuration" for configuration details.
55743 change to the generated source files after this commit.
56115 gdb/testsuite: Default to assembler's preferred debug format in asm-source.exp
56118 format wasn't set in asm-source.exp then leave it to the assembler to
56127 aarch64-linux started failing gdb.asm/asm-source.exp:
56129 Running /home/thiago.bauermann/src/binutils-gdb/gdb/testsuite/gdb.asm/asm-source.exp ...
56130 PASS: gdb.asm/asm-source.exp: f at main
56131 PASS: gdb.asm/asm-source.exp: n at main
56132 PASS: gdb.asm/asm-source.exp: next over macro
56133 FAIL: gdb.asm/asm-source.exp: step into foo2
56134 PASS: gdb.asm/asm-source.exp: info target
56135 PASS: gdb.asm/asm-source.exp: info symbol
56136 PASS: gdb.asm/asm-source.exp: list
56137 PASS: gdb.asm/asm-source.exp: search
56138 FAIL: gdb.asm/asm-source.exp: f in foo2
56139 FAIL: gdb.asm/asm-source.exp: n in foo2 (the program exited)
56140 FAIL: gdb.asm/asm-source.exp: bt ALL in foo2
56141 FAIL: gdb.asm/asm-source.exp: bt 2 in foo2
56142 PASS: gdb.asm/asm-source.exp: s 2
56143 PASS: gdb.asm/asm-source.exp: n 2
56144 FAIL: gdb.asm/asm-source.exp: bt 3 in foo3
56145 PASS: gdb.asm/asm-source.exp: info source asmsrc1.s
56146 FAIL: gdb.asm/asm-source.exp: finish from foo3 (the program is no longer running)
56147 FAIL: gdb.asm/asm-source.exp: info source asmsrc2.s
56148 PASS: gdb.asm/asm-source.exp: info sources
56149 FAIL: gdb.asm/asm-source.exp: info line
56150 FAIL: gdb.asm/asm-source.exp: next over foo3 (the program is no longer running)
56151 FAIL: gdb.asm/asm-source.exp: return from foo2
56152 PASS: gdb.asm/asm-source.exp: look at global variable
56153 PASS: gdb.asm/asm-source.exp: x/i &globalvar
56154 PASS: gdb.asm/asm-source.exp: disassem &globalvar, (int *) &globalvar+1
56155 PASS: gdb.asm/asm-source.exp: look at static variable
56156 PASS: gdb.asm/asm-source.exp: x/i &staticvar
56157 PASS: gdb.asm/asm-source.exp: disassem &staticvar, (int *) &staticvar+1
56158 PASS: gdb.asm/asm-source.exp: look at static function
56190 The 'info threads' command does not show the '-gid' option
56234 under bfd/po/, i.e. in maintainer mode.
56245 whether translatable strings in the source files were actually marked as
56869 set/show debug riscv breakpoints
56870 set/show debug riscv gdbarch
56871 set/show debug riscv infcall
56872 set/show debug riscv unwinder
58528 two code paths. One path calls value_as_address, while the other
59728 [gdb/testsuite] Fix gdb.asm/asm-source.exp for remote host
59729 Fix test-case gdb.asm/asm-source.exp for remote host using
59738 downloaded source file.
59862 Also add a "show language" to check that we automatically set the language
60191 that show:
60648 Commit 904d9b02a185 ("gdb: make "maintenance info line-table" show
60690 gdb: make "maintenance info line-table" show relocated addresses again
60768 It's an odd thing to have objdump -x show a different section table
61228 depends on symbols from within the C++ source code.
61353 C++-specific path in strncmp_iw_with_mode, which ultimately causes the
61463 Regen ld/po/BLD-POTFILES.in
61897 due to trying to match libinproctrace.so using the target path, while the
61898 command lists it using the host path.
61919 set solib-search-path can take effect.
61948 to target the result $target_obj may be a relative file path, which may give
61964 In proc have_avx we compile some source into an exec, resulting in a file $obj
62045 * scripttempl/z80.sc: Use source_sh to source elf.sc.
62376 * scripttempl/arclinux.sc: Use source_sh to source DWARF.sc
62553 But that's not the case for the .c file, which is needed by gdb to show a
62554 source line:
62724 This fixes a bug in .include and .incbin where given an absolute path
62725 the -I dirs would be searched for the path.
62737 use notes for include path.
62956 In gdbarch_types.py, I've updated the type annotations to show that
63080 "main.rs" -- i.e., the bug is specific to the source file name. The
63217 Also remove hard-coding of a source line number.
63426 system include path such as /usr/local/include is added before local
63744 the testcase to actually use distinguishable source and destination
63805 on target using remote_download, and using the resulting path.
63933 [gdb/testsuite] Fix gdbserver path in remote-stdio-gdbserver.exp
64035 assumed to be a target path, but it's actually a build path.
64047 is assumed to be a host path, but it's actually a build path. This happens to
64430 a host path.
64441 Fix this by using an absolute path name for the exec on the target board.
64613 BSD's use SYS_exit rather than SYS_exit_group. Update the C source
65164 [gdb/symtab] Add set/show always-read-ctf on/off
65185 Add a new command "set/show always-read-ctf on/off", that when on forces
65360 * read.c (do_repeat): Free sb on error path.
65519 The breakpoint will not show in 'info breakpoints' as its number is
65520 zero, but it will show in 'maint info breakpoints'.
65600 This means that GDB is in a position where the breakpoint doesn't show
65703 &"No source file named mi-pendshr.c.\n"
65732 'maint show target-non-stop' command, and then switch based on the
65953 Static analysis found this call path from the destructor to
66024 path to maybe_quit():
66031 Since there is a path to maybe_quit(), we must ensure that the
66045 a call path to maybe_quit():
66127 1) There is no call path to maybe_quit() in the try block. I used a
66130 call path can result in maybe_quit() being called", I reviewed it
66643 show:
67350 failed because the check comes after the PASS path. For tab completion,
67502 before the first ":" as it has to be the file path.
67971 Since b5075fb68d4 (Rename to allow_tui_tests, 2023-01-08) it does show
68301 The regexp in "noinit sections (ld -r)" is skipping the file path before
68302 the first ":". However, on Windows, a path can start with "C:". Adjust
68312 ld/testsuite: adjust to Windows path separator.
68313 In some tests, the path reported on Windows will have a \ instead of a
68314 /. This occurs when a file is concatened with the search path in
68319 * testsuite/ld-elf/retain5.map: Allow \ path separator.
69009 * testsuite/ld-scripts/ascii.s: New test assembler source.
69029 I don't see much point in cluttering the source with the PROGRESS
69388 currently print the double <>s because we take this path in
69395 c_print_type (type, "", stream, show, level, language_ada, flags);
69811 order in the output of "show convenience". And the order changes when
69814 I think that a nice way to fix it is to make the output of "show
69817 GDB_REVERSE_INIT_FUNCTIONS. Plus, it makes the output of "show
69843 "condition" command, but I never managed to get in the right code path.
70037 delete the directory from their source tree but... it doesn't make
70637 (gdb) source tui.py
70898 gdb: 'show config' shows --with[out]-amd-dbgapi
70899 Ensure that the "show configuration" command and the "--configuration"
70951 gdb: show task number in describe_other_breakpoints
71186 gdb: show task number in describe_other_breakpoints
71187 I noticed that describe_other_breakpoints doesn't show the task
71188 number, but does show the thread-id. I can't see any reason why we'd
71189 want to not show the task number in this situation, so this commit
71305 While debugging GDB I used 'show directories' and spotted lots of
71340 can still see the GDB source code just fine; which is because the
71358 debug information should allow us to correctly find all of the source
71488 gdb/source: Fix open_source_file error handling
71490 source file.
71497 a missing source file. The following error message should instead be
71502 Downloading source file /usr/src/debug/glibc-2.36-8.fc37.x86_64/elf/<built-in>
71506 to open a source file. Use this value to generate the error message
71776 "current source file".
71779 of debug info, the "current source file" becomes glibc's ./setjmp/longjmp.c.
71786 glibc-32bit-debuginfo package. This allowed me to confirm the "current source
71791 info source^M
71792 Current source file is ../setjmp/longjmp.c^M
71888 (mmo_scan): Free fname on another error path.
72430 and return it via the normal return path. That's normally needed when
72850 enabled by the user. Also show the bss-plt warning when
72967 bug didn't show.) Now I don't really care too much what happens with
73367 talk to the library, as show on the following diagram:
73741 code path.
73778 gdb/linespec.c: Fix missing source file during breakpoint re-set
74175 The display of address maps above could probably be improved, to show it
74340 adapted. The show command will display the current remote target's
74456 The show command displays the current remote target's configuration. If no
74477 The show command 'show remote multiprocess-feature-packet' will display
74484 To inform the gdb user about the new behaviour of the 'show remote
74488 test using the set/show remote 'PACKET-NAME' commands.
74626 that happens is the source window displays no content.
74801 path (e.g. when an assert triggers). With this done then we don't
75724 this code path we assert that the currently focused window is
75841 gdb/testsuite: rename test source file to match test script
75842 The previous commit touched the source file for the test script
75843 gdb.cp/cpcompletion.exp. This source file is called pr9594.cc. The
75844 source file is only used by the one test script.
75846 This commit renames the source file to cpcompletion.cc to match the
75847 test script, this is more inline with how we name source files these
76171 Remove path name from test
76172 The test suite reports several path names in tests. I couldn't find
76174 to locate one. This one is probably harmless, as I think the path
76299 source language c.
76351 shown above, is a bug. I would expect that command to show the
76851 This commit splits the `set/show print elements' option into two. We
76852 retain `set/show print elements' for controlling how many elements of an
76853 array we print, but a new `set/show print characters' setting is added
76862 For compatibility reasons by default the `set/show print characters'
76864 follow the setting of the `set/show print elements' option, as it used
76866 independent from the `set/show print elements' setting, however it can
76874 `set/show print elements' setting, for characters as well regardless of
76875 the current setting of the `set/show print characters' option.
76885 To make people's life easier the message shown by `show print elements'
76889 (gdb) show print elements
76892 (gdb) show print elements
76908 and `show print characters', copied from the corresponding checks for
76909 `set print elements' and `show print elements' respectively.
76922 `var_zuinteger_unlimited' `set'/`show' command variable types redefining
77081 binutils-gdb source tries to link against it.
77249 the wrong names for some source files. Finally, a couple of obsolete
77326 reach previous source line
77348 execution in the caller at the first instruction of the source code line.
77362 reach previous source line
77366 caller. GDB stops on the last instruction in the source code line where
77367 the call was made. When stopped at the last instruction of the source code
77369 of the same source code line thus requiring two step/next commands to
77370 reach the previous source code line. It should only require one step/next
77371 command to reach the previous source code line.
77374 function stops at the first instruction in the source code line where the
77378 instruction of the source line where the function call was made. The
77702 sim: common: move modules.c to source tracking
79197 up, we can switch this to the source files directly. It's a bit hacky
79203 gdb/linespec.c: Fix missing source file during breakpoint re-set
79210 symtab's fullname (the path where GDB found the source file) when the
79212 fullname differ and there is no substitute-path rule that converts the
79298 * po/SRC-POTFILES.in: Regenerate.
79838 sim: mips: add multi source to built sources
79841 In the multirun mode, be lazy and declare all of these generated source
80013 execinfo path (when libbacktrace is available). But I figure its
80297 sim: sh: move some generated source files to built sources
80552 source files managed by the GDB project to be updated to include
80569 of New Year procedure. The corresponding source files' copyright
80721 that this message doesn't show up, in other words, the out_of_scope callback
80729 Note that the message does show up later, at thread exit:
81235 source buffer for the memcpy needs to point to the uint8_t/uint16_t sized
81351 dynamic-linker was installed, in this case, the list of source files
81416 FAIL: gdb.base/float128.exp: show configuration
81418 The test fails to find --with-mpfr or --without-mpfr in the "show
81670 sim: endian: move bfd.h from header to source
81820 the full path.
81918 avoid producing a listing line for (non-existing) line 0 when the source
81997 been a permanent source of mistakes. Reduce what needs specifying
82115 With only MPFR in the toplevel (GMP distro library used and MPFR built from source)
82188 Clang) do not show such a bug, so the test includes an XFAIL for gcc
82377 The spreg.[ch] files live in the source tree now and are created
82382 sim: ppc: move spreg.[ch] files to the source tree
82445 Regen opcodes/po/POTFILES.in
82632 ld bootstrap test in build dir with path containing symlinks
82634 in the build path directory. $ld depends on $base_dir which is set
82916 When the source program contains a goto label, it turns out it's
84436 x86: revert disassembler parts of "x86: Allow 16-bit register source for LAR and LSL"
84438 register source for LAR and LSL"), adjusting testcases as necessary.
85650 x86: Allow 16-bit register source for LAR and LSL
85651 Since LAR and LSL only access 16 bits of the source operand, regardless
85652 of operand size, allow 16-bit register source for LAR and LSL, and always
85653 disassemble LAR and LSL with 16-bit source operand.
85676 * i386-opc.tbl: Allow 16-bit register source for LAR and LSL.
85702 gdb: merge solib-frv aix-solib debug options into "set/show debug solib"
85708 "set/show debug solib", with the solib_debug_printf macro.
85772 Currently finish-reverse-bkpt.exp uses source file finish-reverse.c and
85773 next-reverse-bpkt-over-sr.exp uses source file step-reverse.c A new
85774 source file was created for tests finish-reverse-bkpt.exp and
85780 The expect files were changed to use the new source files and to set the
85930 * po/POTFILES.in: Likewise.
86125 show disassembler-options esa
86308 Also move the respective conditional out of the code path taken by all
86327 src-release.sh: Fix gdb source tarball build failure due to libsframe
86337 Since then, the gdb source tarball has been failing with the error
87196 sorting and have a fast path for insertion at end (aka rightmost tree
87538 path, the stack looks like:
87545 Along this path there is no scoped_disable_commit_resumed created.
87986 e.g. gdb.base/macro-source-path.exp (see details below).
87990 Tested on amd64/debian11 and re-running gdb.base/macro-source-path.exp
89081 source looks like this:
89107 output (the top line of the source file is no longer included in the
89109 is checking that GDB managed to find the source file, it doesn't
89110 matter which source line we list, as long as we can list something.
89114 gdb/testsuite: rename source file gdb.debuginfod/main.c
89115 The test gdb.debuginfod/fetch_src_and_symbols.exp uses a source file
89119 Usually test source files are named after the test script.
89121 This commit just renames the source file inline with the test script,
89126 file named main.c made me thing that the source file must be shared
89198 One consequence of this change is that we need to compile the source
89208 deleted these two lines from the source file:
89398 the source files. The use of NULL in the comments was not changed.
89744 PASS: gdb.asm/asm-source.exp: info source asmsrc1.s
89746 UNRESOLVED: gdb.asm/asm-source.exp: finish from foo3
89751 $ gdb -q -batch -x outputs/gdb.asm/asm-source/gdb.in.1
89790 this patch disables source and assembly code highlighting for the
90431 [gdb/testsuite] Normalize gdbserver path name
90944 I realized that the more irregular output of show arch:
90946 (gdb) show arch^M
91471 in a source file would better not result in an internal error. Give use
91893 source language c.
92224 includes the relevant source files directly and runs the code that
92824 update the readline library path to be relative to the top dir.
93098 Further, some of the source file generation (e.g. .c files, or igen,
93313 running gdb.base/macro-source-path when using clang.
93955 4 next execute source code: buf[0] = 3;
93956 5 next execute source code: global_ptr = buf;
93957 6 next execute source code: buf[0] = 7;
93960 9 next execute source code: buf[1] = 5;
93987 In step 10, the next command executes the source code
94364 consumed, which makes it show up much later.
94415 to include path (not tested while configuration), it causes <unistd.h>
95594 For *avx512*_vpclmulqdq-wig1 share source with *avx512*_vpclmulqdq.
95605 For *avx512*_vaes-wig1 share source with *avx512*_vaes. This in
95887 * po/hu.po: Updated Hungarian translation.
96249 ELF interpreter /path/to/rtld-step-rtld not found, error 22
96306 Regen ld/po/BLD-POTFILES.in
96493 files in GDB's current directory, specifically, the two source files:
96539 variable debug_str_section which contains a path within the output
97574 source. Instead change the test to check -Mraw results.
97978 [gdb/testsuite] Fix gdb.dwarf2/macro-source-path.exp with -m32
97979 With test-case gdb.dwarf2/macro-source-path.exp and target board unix/-m32, I
97982 as: macro-source-path-gcc11-ld238-dw5-filename-641.o: \
98376 The code path that reads from the target stack will keep caching,
98797 gprofng: use the --libdir path to find libraries
99030 show debug infcall
99050 Add ability to create reproducible source tarballs.
99351 [gdb/testsuite] Fix path in test name in gdb_load_shlib
99355 (gdb) set solib-search-path $outputs/gdb.server/solib-list^M
99357 set solib-search-path $outputs/gdb.server/solib-list
99359 set solib-search-path $outputs/gdb.server/solib-list
99364 gdb_test "set solib-search-path [file dirname $file]" "" ""
99569 make[4]: Entering directory '/home/alan/build/gas/all/bfd/po'
99570 …to make target '../elf32-aarch64.c', needed by '/home/alan/src/binutils-gdb/bfd/po/bfd.pot'. Stop.
100431 have the same name, then this will show up as duplicate registers in
100472 corresponding C++ source file. With this change made, the selftest
100697 --source
100700 no mode value is given. Mode 0 is the simplest, no source code, no
100709 The --source option will enable the /s style source code display, this
100711 command options to get the now deprecated /m style source code
100959 to minimum required extensions. Remove source line.
101297 correcting a prominent source of ODR violations in PowerPC-related target code.
101752 gdb/source.c: Fix undefined behaviour dereferencing empty string
101753 When a source file's dirname is solely made up of directory separators
101871 concluded that it is caused by the long source directory name:
101886 FAIL: gdb.tui/tui-missing-src.exp: f2.c must be displayed in source window
101887 FAIL: gdb.tui/tui-missing-src.exp: check source box is empty after return
101928 "Delete Line" operation [1] and some new ones are drawn. The source
101932 "check if inside f2" and "f2.c must be displayed in the source window"
101999 due to the directories (source and build) in which tests are ran. TUI
102529 inferior was only showing up as with a relative path, like so:
102562 relative path, but seeing as testing the full path is not important for
102565 little to allow the relative path.
102596 skipping the function square, the testsuite would show
102740 Making info in po
102741 make[3]: Entering directory '/build/gas/all/bfd/po'
102742 cd .. && make po/SRC-POTFILES.in
102743 cd .. && make po/BLD-POTFILES.in
102763 * Makefile.am (po/BLD-POTFILES.in): Don't depend on $(BLD_POTFILES).
102764 (po/SRC-POTFILES.in): Don't depend on $(SRC_POTFILES).
102845 gdb_assert (strlen (path) == 0 || !IS_ABSOLUTE_PATH (path));
102847 ... where `path` is "x". IS_ABSOLUTE_PATH eventually calls
102953 file symbols can't be directly matched against the source-level
102957 2) Demangling doesn't give the source function name as stored in
102968 containing the DWARF source name as a substring.
104261 * testsuite/config/default.exp (SIZE): Adjust relative path.
104577 a call to debuginfod_find_source in order to download missing source files.
104581 debuginfod_find_source in order to download missing source files.
104774 changes were made to the simulator source to handle the new libopcodes
105041 Fix "source" with interpreter-exec
105042 PR mi/15811 points out that "source"ing a file that uses
105156 registers always show up as <unavailable> - they are present in the
105268 'FRM' fields in $fcsr show the same information.
105357 parameter declarations in the source progam.
105567 causes debuginfod to display the wrong path of the objfile during a download.
105693 * testsuite/gas/arm/pr29494.s: New test source file.
105920 actually). There are changes to the --enable-source-highlight and
106063 * testsuite/gas/aarch64/pr29519.s: New test source file.
106505 passing to the copy function a source array view of length 0 and a
106513 path (value_of_dwarf_reg_entry and all) to manage to get to
106516 already, so the bug wouldn't show up.
106520 test. The .cpp source code is the smallest reproducer I am able to make
106648 only, there is no need to update calls from the gdb source tree.
107468 will show the errors when using a suitable target.
107840 dissably call with source code involved. E.g.
107842 …t-address=0x0000000004e0dcd0 --stop-address=0x0000000004e0df8b -l -d --no-show-raw-insn -S -C /usr…
108469 * testsuite/package_metadata_main.c: New test source.
109275 gdb/testsuite: add macros test for source files compiled in various ways
109276 Using different ways of passing source file paths to compilers results n
109307 …$ make check TESTS="gdb.base/macro-source-path.exp" RUNTESTFLAGS="CC_FOR_TARGET=clang --target_boa…
109339 "test.c". And because the path built from the line header contained the
109346 identified using the "most complete path possible", this case would be
109371 Printing macros defined in the main source file doesn't work reliably
109404 (top-gdb) p source.filename
109407 `source` is the macro_source_file that we would expect GDB to find.
109428 line_header::file_file_name prepends the directory path that the file
109440 path can be passed to the compiler by the user.
109467 objects and symtab objects use the most complete form of path possible.
109469 path. In theory, we should end up with the same path in all cases.
109471 resulted in user-visible changes (for example, paths to source files in
109486 "most complete possible" path, as discussed above. So for a given file,
109500 to start_subfile for the main source file look up the existing
109522 file_entry handy. This ensures that it will get the exact same path
109584 The first file name produces a path without a "." while the second does.
109614 removes the unnecessary "." from path names, something that can be done
109620 gdb.dwarf2/dw2-compdir-oldgcc.exp: info source gcc42
109624 (gdb) info source
109625 Current source file is /dir/d/dw2-compdir-oldgcc42.S
109630 (gdb) info source
109631 Current source file is dw2-compdir-oldgcc42.S
109639 generate a DW_AT_name with a full path ("/dir/d/dw2-compdir-oldgcc42.S")
109671 And so "info source" would show "dw2-compdir-oldgcc42.S" as the
109687 with "/dir/d/dw2-compdir-oldgcc42.S" as the name, "info source" shows
109692 current source file as "/dir/d/dw2-compdir-oldgcc42.S". If you compile
109693 a file passing "/an/absolute/path.c", DW_AT_name typically contains (at
109694 least with GCC) "/an/absolute/path.c" and GDB tells you that the source
109695 file is "/an/absolute/path.c". But we can also keep the existing
109700 ("gcc path.c -g"):
109702 DW_AT_name ("path.c")
109707 symtab (what ends up shown by "info source") is just
109879 I've used the source files in gas/testsuite/gas/aarch64/ for testing,
110192 source: file path and line number tuple: (string, long) / None
110230 Testsuite: tests the .source attribute and the disabling of
110627 path.
110675 set/show python dont-write-bytecode fixes
110691 .pyc files on the import of source modules.
110696 This commit also corrects the set/show command documentation for
110698 of that for set/show python ignore-environment.
110701 asked that the help text that I proposed for "set/show python
110838 binutils-gdb/git: highlight whitespace errors in source files
110844 which causes git to show me if I muck up and use spaces instead of
110854 source file, will highlight the following whitespace errors:
110925 source files in gas/testsuite/gas/ppc and manually checked that the
111378 (gdb) show architecture
111382 (gdb) show architecture
111553 (gdb) show mips mask-address
111558 The 'show mips mask-address' command ends up in show_mask_address in
111572 have two lines that show the same information, but using different
111590 (gdb) show mips mask-address
111600 (gdb) show mips mask-address
111618 are used as the callbacks for two set/show parameters. These set/show
111624 (gdb) show arm fpu
111625 (gdb) show arm abi
111968 Step program until it reaches a different source line.
112893 Where the source code for stap-probe.c is:
113582 maintenance show libopcodes-styling
113596 set/show style disassembler comment
113597 set/show style disassembler immediate
113598 set/show style disassembler mnemonic
113599 set/show style disassembler register
113605 set/show style disassembler address
113606 set/show style disassembler symbol
113610 set/show style address
113611 set/show style function
113623 (gdb) show architecture
113625 (gdb) maintenance show libopcodes-styling enabled
113633 (gdb) maintenance show libopcodes-styling enabled
113636 the setting will show as "off" if the user switches to an architecture
113642 (gdb) maintenance show libopcodes-styling enabled
113646 to i386:x86-64 the setting will still show as "off".
113650 (gdb) maintenance show libopcodes-styling enabled
113658 (gdb) maintenance show libopcodes-styling enabled
113661 (gdb) maintenance show libopcodes-styling enabled
114024 (dwcfi_hash_find_or_make): Adjust failure path free.
114035 read.c s_include: use notes obstack for path
114036 * read.c (s_include): Use notes obstack for path mem.
114076 * read.c (read_symbol_name): Free name on error path.
114339 source files in gas/testsuite/gas/s390 and manually checked that the
116120 Workaround this by first copying the source file to the temp dir, such that
116265 Note that I didn't touch */po/*.po{,t} on the assumption that these
116655 Improve core file path detection & put cores in output dir
116777 Let's show the current stub as well as the previous one. Of interest
117054 libctf: fix linking together multiple objects derived from the same source
117186 * prdbg.c (pr_function_type): Free "s" on failure path.
117190 * stabs.c (parse_stab_struct_fields): Free "fields" on failure path.
117264 by user manually. Of course, 'show print nibbles' is also included in
117335 * stabs.c (stab_demangle_v3_arg): Free dt on failure path.
117661 This means that when the GDB client is to show the value of "msp",
119269 The next source of content are immediate operands. The text for these
120489 (parse_comp_unit): Set unit->error on err_exit path.
120526 having to parse the output of "show language".
121046 check for types that are either not used in the source file (character1)
121586 (gdb) source test-cmd.py
121607 set/show output.
121623 (gdb) source ~/tmp/test-cmd.py
121684 handler did not find "show" in the command name, violating an
122002 ../../gdb/source.c:365
122004 ../../gdb/source.c:268
122055 display the source where the execution stopped, we have a segfault.
122059 If the main binary has debug information, GDB shows some source form the
122145 For performance testing, using "maint time 1" and "file" will not show
122192 removes the source of the warning that Luis was trying to fix).
122274 Such locations won't trigger a break, so to avoid confusion, show "y-"
122285 left side of the source window, with "b-" for a disabled breakpoint.
123707 * testsuite/binutils-all/no-weak.s: New test source file.
124015 to the question path, then it's a bug. So just remove the question
124317 At source level (as we can observe in the .ii file with -save-temps) we have
125100 * source.h: Likewise.
126749 replacement for free (see gnulib/import/m4/free.m4). In that path,
127618 architectures show "unsigned int" for both 32-bit and 64-bit integers
127619 and 64-bit architectures show "unsigned int" and "unsigned long" for
127859 bsd-kvm: Fix build after recent changes to path handling functions.
128553 functions do not show up in the object dump of the Intel or Powerpc
128599 Without the patch, the lib1_spacer and lib2_spacer function doesn't show
128602 both architectures and lib1_spacer and lib2_spacer function show up in the
128634 to mi_continue_to_line. Since the location can contain a path, that
128679 gdb: fix 'remote show FOO-packet' aliases
128682 (gdb) show remote X-packet
128695 (gdb) show remote X-packet
128714 double slash at the beginning of a file path has a special meaning. So
128719 path = first_path + second_path
128721 path = first_path + slash + second_path
128727 Introduce the path_join function that can be used to join multiple path
128731 support the use case of prepending a sysroot path to a target file path,
128732 or the prepending the debug-file-directory to a target file path. But
128734 (for example, when the right hand side is a Windows path with a drive
128738 Change a few spots to use path_join to show how it can be used. I
128740 ensure the right hand side operand is not an absolute path.
129293 This embedded offset stuff is an endless source of bugs. I wonder if
129305 a breakpoint by line at line 34, without specifying the source file. When looking at the logs:
129313 the test source file as we expect. The problem is that "b main" in Ada
129315 generated source file. So when stopped at the "main" symbol, we are not
129324 regardless of what is the current source file.
129326 However, this ends up introducing a path in the test name. Modify
129831 Do you need "set solib-search-path" or "set sysroot"?
129833 Do you need "set solib-search-path" or "set sysroot"?
129835 Do you need "set solib-search-path" or "set sysroot"?
129837 Do you need "set solib-search-path" or "set sysroot"?
130666 and alike blocks"), while dealing okay with actual assembly source files
130692 and alike blocks"), while dealing okay with actual assembly source files
130707 full path in the inserted directive). (This then leaves undisturbed any
131899 So, after this, using 'tui reg next' will (in the above case) show the
132106 * testsuite/gas/i386/secidx.s: New test source file.
132113 ld * testsuite/ld-pe/secidx1.s: New test source file.
132114 * testsuite/ld-pe/secidx2.s: New test source file.
132368 source, and it too has moved over to using interp_factory_register.
132807 This is the default path we take if:
132839 there's a breakpoint in the path the child is going to take before
133119 entire testsuite) show that it does not emit this flag either.
133153 the stream it wraps) fixes it. To show that it works, modify some
134380 This commit adds 'set debug tui on|off' and 'show debug tui'. This
134397 (gdb) set logging file /path/to/file
134564 Regen bfd po/SRC-POTFILES.in
135251 Add a "reason" parameter, only used to show in debug messages what is
135791 What we're checking for is that symbols 'foo' and 'bar' show up in the
135868 instance, but not for the 1st (if this code path is taken). (This,
136076 libtool.m4: fix the NM="/nm/over/here -B/option/with/path" case
136078 the environment to a path which contained an option, libtool's nm
136086 contains a path, and in that case avoid doing a path search itself.
136088 like a path, e.g. NM="nm -B../prev-gcc"; libtool then tries to run
136095 contains a path (but not using the clipped value for anything else),
136096 and then removing all options from the path-modified nm before
136099 NM=my-nm now does a path search and runs e.g.
136102 NM=/usr/bin/my-nm now avoids a path search and runs e.g.
136105 NM="my-nm -p../wombat" now does a path search and runs e.g.
136108 NM="../prev-binutils/new-nm -B../prev-gcc" now avoids a path search:
136305 * ctf-serialize.c (ctf_write_mem): Add flip_endian path via
136562 original source file looks wrong: Upon finishing of the processing of an
136977 path, when handling TARGET_WAITKIND_STOPPED.
137336 RUNTESTFLAGS="GDB=/path/to/other/build/gdb \
137337 GDB_DATA_DIRECTORY=/path/to/other/build/gdb/data-directory"
137358 * testsuite/gas/z80/pr28791.s: New test source file.
137687 can fold the vector shift insns with an XMM source as well. While
137771 Releases some obstack memory on an error path.
137920 * po/SRC-POTFILES.in: Regenerate.
138550 nor versioned. Taking a peek at the LLVM source code, we see that they
138637 nor versioned. Taking a peek at the LLVM source code, we see that they
138890 gprofng: Don't generate gprofng.info in source
139289 | Do you need "set solib-search-path" or "set sysroot"?
139296 libraries. These aren't available via the solib search path, and so
139299 solib-search-path, it does not set the sysroot.
139818 …PR gdb/27876 - debuginfod-downloaded source files don't pass proper fullname across mi / (gdb)info…
139821 and the actual location of the source file in the debuginfod client cache.
139824 source files due to this. Also 'info source' will fail to include the
139827 To fix this, use the debuginfod cache path as the fullname for debuginfod-
139828 downloaded source files.
139849 ~" source language c.\n"
139872 ~" source language c.\n"
140120 This patch introduces a new "ada source-charset" setting. It defaults
140221 source.
140223 source.
140258 value_copy. However, value_copy takes a non-const source value, at the
140261 If the source value is not lazy, we currently call
140552 Do you need "set solib-search-path" or "set sysroot"?
140574 This moves the copyright code from gdbarch.py to a new Python source
140595 source distribution, these are included in the tarball, and if the
141027 This patch adds the missing observer and arranges to show the MI
141255 I looked at how FreeBSD handles this, since I remembered it did show
141583 Move the message from 'show debug fbsd-lwp' to 'show debug fbsd-nat'
141704 gdb: fix detection of compilation and linking flags for source-highlight
141706 source-highlight via pkg-config in GDB's configure script:
141709 to AC_LINK_IFELSE, which results in the "-L/some/path
141720 configure and build using source-highlight installed into a custom
141722 source-highlight is too old).
141861 a compilation unit (or at least the location of a corresponding source
141869 some symbol information that is not associated with any source file.
142041 Much of the gas source and older BFD source use "long" for function
142295 code-path was changed instead of the "/"-prefixed code-path,
142307 The interaction of calling with the full program-path vs.
142309 --sysroot is used, argv[0] isn't the path by which the
142506 0, so (not) setting it in the no-working-compiler path seems
142609 show style disassembler enabled
142619 hook is very similar to the existing hook for source code
142655 already some precedent for this in GDB when we look at source styling.
142656 For example, function names in styled source listings are not styled
142937 To better understand this issue, consider the following source code,
142966 associated with the same source line number as the previous stepping
142975 for a different source line. As a result, GDB stops and returns
143117 is of course unused in any code path where it might start off as
143439 case will _only_ show up when using new-ui to create the separate tty
143523 read(9, "70-var-info-path-expression var1.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", 1024) = 64
143524 read(9, "\n71-var-info-path-expression var1.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\n", 1024) = 67
143586 gdb: add the 'set/show suppress-cli-notifications' command
144490 Currently, "ptype" of an Ada unchecked union may show a
144684 gdb: fix formatting for help set/show extended-prompt
144686 'help show extended-prompt' is a little off.
144787 path is:
144883 Finally, the test script doesn't have its own source file, it was
144884 reusing a random other source file, gdb.base/memattr.c. Now the tests
144886 source file from that directory.
144935 the source of the memory allocation is irrelevant, and so, shouldn't
145738 gdb/python: handle non utf-8 characters when source highlighting
145739 This commit adds support for source files that contain non utf-8
145740 characters when performing source styling using the Python pygments
145746 using 'maintenance set gnu-source-highlight enabled off'.
145748 The initial problem reported was that a source file containing non
145750 display the source without styling, e.g.:
145755 Further, as the user steps through different source files, each time
145756 the problematic source file was evicted from the source cache, and
145763 the source file contents, they're right there... If we disable
145774 problem, if the source file contains non utf-8 characters, then it
145780 ignore the error. This would mean that GDB would print the source
145786 is quite happy to syntax highlight my source file that contains non
145921 (gdb) help set param-set-show
145949 (gdb) help set param-set-show
145989 show function when registering the internal command object within
146001 (gdb) show param-none
146006 After my patch, we how show this:
146008 (gdb) show param-none
146032 absolute number, for example, if you wanted to show a complete history
146159 valid value for an "enum" set/show parameter.
146203 entry. I've added a test to show this as well.
146213 bfd: Make bfd.stamp depend on source bfd.texi
146214 Make bfd.stamp depend on source bfd.texi to avoid regenerating
146806 moves it out of breakpoint.c (the second largest source file in gdb)
146811 moves it out of breakpoint.c (the second largest source file in gdb)
146894 to correctly show the user how the connection was established. And in
147093 There's a single use on a generally infrequently taken code path. Put
147715 ERROR: tcl error sourcing /path/to/gdb/testsuite/gdb.python/py-events.exp.
147719 (file "/path/to/gdb/testsuite/gdb.python/py-events.exp" line 103)
147721 "source /path/to/gdb/testsuite/gdb.python/py-events.exp"
147724 "uplevel #0 source /path/to/gdb/testsuite/gdb.python/py-events.exp"
147726 "catch "uplevel #0 source $test_file_name""
148045 gdb: add 'maint set/show gnu-source-highlight enabled' command
148054 maintenance set gnu-source-highlight enabled on|off
148055 maintenance show gnu-source-highlight enabled
148076 As source files are read the contents of the file, as well as the
148096 This means that if a program contains enough source files, GDB will
148097 hold at most MAX_ENTRIES cached source file contents, but can contain
148098 offsets data for every source file.
148117 gdb: new 'maint flush source-cache' command
148118 This commit adds a new 'maint flush source-cache' command, this
148119 flushes the cache of source file contents.
148121 After flushing GDB is forced to reread source files the next time any
148122 source lines are to be displayed.
148125 in that it modifies a source file after compilation, and makes use of
148126 the cache flush so that the changes show up when listing the source
148137 gdb: rename lin-lwp to linux-nat in set/show debug
148138 Rename 'set debug lin-lwp' to 'set debug linux-nat' and 'show debug
148139 lin-lwp' to 'show debug linux-nat'.
148511 kernels, so that $_siginfo decoding can show information about
148519 gdb: testsuite: show print array-indexes after set in arrayidx.exp
148520 Add "show print array-indexes" testcases after set print array-indexes
148533 PASS: gdb.base/arrayidx.exp: show print array-indexes is off
148536 PASS: gdb.base/arrayidx.exp: show print array-indexes is on
148888 There is a expect support library in the source tree designed to help
148963 DUPLICATE: gdb.base/subst.exp: unset substitute-path from, no rule entered yet
149210 * po/fr.po: Same.
149211 * po/ru.po: Same.
149212 * po/uk.po: Same.
149229 * po/fr.po: Same.
149230 * po/ru.po: Same.
149231 * po/uk.po: Same.
149247 gdb/doc: shorten some source lines, and prevent some line breaks
149249 split long @deffn lines in the guile.texi source file. This splitting
149284 lines, and keep them under 80 characters in the texi source. This
149435 In gnu-nat.c we currently implement some set/show prefix commands
149436 "manually", that is, we call add_prefix_cmd, and assign a set and show
149439 These set/show functions print an error indicating that the user
149443 delete the set/show functions, GDB provides some default functions,
149449 set/show prefix commands, and the new behaviour is more informative.
149455 Where Tom changes the set/show functions that I delete. My suggestion
149456 is that the set/show functions still be deleted even after Tom's
149492 ("Consistently Use ui_file parameter to show callbacks").
149504 includes full paths to the source files.
150173 Fixes: 45aec4e5ed8 ("[gdb/cli] Improve show logging output")
150220 [gdb/cli] Improve show logging output
150222 following output for "show logging":
150226 -ex "show logging" \
150228 -ex "show logging"
150230 +show logging
150236 +show logging
150246 +show logging
150252 +show logging
150262 The new text seems to have been chosen to match the set/show help texts:
150264 (gdb) help show logging
150267 List of show logging subcommands:
150269 show logging debugredirect -- Show the logging debug output mode.
150270 show logging file -- Show the current logfile.
150271 show logging overwrite -- \
150273 show logging redirect -- Show the logging output mode.
150276 Make the show logging messages more clear, while still keep the boolean
150279 $ ./gdb.sh -q -batch -ex "show logging"
150355 out */po/*.pot which we don't update frequently.
150383 The sim testsuite was reorganized last year, so update the path.
150569 Use filtered output in show callbacks
150570 "show" command callbacks, like most ordinary gdb commands, should use
150576 Consistently Use ui_file parameter to show callbacks
150577 I happened to notice that one "show" callback was printing to
150722 -ex "show args" \
150723 -ex "show inferior-tty" \
150726 -ex "show args" \
150727 -ex "show inferior-tty" \
151296 to perform in the non-exception return path.
151324 mi-async' (with a similar difference for the show/-gdb-show).
151327 -gdb-show, and as -gdb-set/-gdb-show are just the MI equivalent for
151328 set/show anything that is documented under set/show can be adjusted
151344 I have updated the doc strings shown when the users enters 'help show
151345 debug lin-lwp' or 'help show debug lin-lwp'. The old title lines used
151359 show debug threads
151607 remote target, and replies received, the first path I hit is the
151639 0);', this, at least would show me when GDB was doing something
152210 using binutils 2.37, we observed a failure that didn't show up on
152213 C:\path\to\nios2-elf-ld.exe: looping in map_segments
152433 the code to check that the source string length is smaller than the
152531 the comments in the header and source files.
152550 Besides, these testcases also show the limits of the current medlow and medany
152941 C++-ify path substitution code
152942 I found some uses of xfree in the path substitution code in source.c.
153023 that user can specify path to gdbserver on remote system by setting
153120 is not passed, we will always take the path that sets print_fail to 0,
153415 (gdb) show detach-on-fork
153417 (gdb) show follow-fork-mode
153542 But, when they source this code they'll see:
153544 (gdb) source ~/tmp/value-test.py
153761 Fix bug in source.c change
153762 My earlier change to source.c ("Remove an xfree from add_path")
153921 Fix this by using a new source file main-one-line.c, that implements the
154032 When running test-case gdb.base/cached-source-file.exp with target board
154035 FAIL: gdb.base/cached-source-file.exp: rerun program (the program exited)
154269 to define symbols that show up in the system headers.
154341 gdb: don't show deprecated aliases
154342 I don't think it's very useful to show deprecated aliases to the
154512 array view to another, ensuring that the destination and source array
154526 source or vice-versa. std::copy and std::copy_backward don't support
154527 copying exactly overlapping ranges (where the source range is equal to
154532 and std::copy_backward, where the source comes before the destination.
154534 Change a few randomly selected spots to use the new function, to show
154539 ranges as well as three kinds of overlapping ranges: source before dest,
154540 dest before source, and dest == source.
154768 debugformat field") changes the debug format string in "info source" to
154769 show the actual DWARF version, rather than always show "DWARF 2".
154939 Returning from that function call using "finish" should show
155415 The "info source" command, with a DWARF-compile program, always show
155418 (gdb) info source
155419 Current source file is test.c
155430 (gdb) info source
155431 Current source file is test.c
155999 One way to show the problem with this is if we try to read the auxv
156476 sim: nltvals: pull target syscalls out into a dedicated source file
156551 [gdb/testsuite] Fix FAIL in gdb.base/list-missing-source.exp
156557 (gdb) FAIL: gdb.base/list-missing-source.exp: list
156563 Fix this by using the more specific file name list-missing-source.c.
156704 This causes the source file $src/gdb/testsuite/gdb.ada/dgopt/x.adb to be
156724 In C we can generate similar debug information, using a source file that does
156918 and would instead print it as an empty class (first path found).
156963 * po/BLD-POTFILES.in: Regenerate.
156964 * po/SRC-POTFILES.in: Regenerate.
156969 * po/fr.po; Updated French translation.
156984 observer for both source styling, and disassembler styling.
157106 following output for "show logging file":
157110 -ex "show logging file" \
157112 -ex "show logging file"
157114 +show logging file
157117 +show logging file
157124 +show logging file
157127 +show logging file
157136 - adding a new command "show logging enabled"
157373 * po/Make-in (msgid-bugs-address): Likewise.
157377 * po/Make-in (msgid-bugs-address): Update.
157380 * po/Make-in: Update bug address.
157382 * po/Make-in: Update bug address.
157384 * po/Make-in: Update bug address.
157386 * po/Make-in: Update bug address.
157388 * po/Make-in: Update bug address.
157452 The debug messages will show a string matching exactly the
157833 ld: source-cache.o: in function `source_cache::ensure(symtab*)':
157834 source-cache.c:207: undefined reference to \
157838 [ I configured gdb without explicit settings related to source-highlight, so
157842 - the source-highlight library is build with system compiler
157849 source-highlight library is build with g++ 4.8.5 and gdb is build with
157852 Fix this by checking whether the source-highlight library is usable during
158221 ...will show one failure.
158367 * testsuite/gas/all/multibyte.s: New test source file.
159349 RISC-V: Scalar crypto instruction and entropy source CSR testcases.
159450 Then, make the show commands not call "error" when debuginfod support is
159451 not compiled in. This makes the commands "show" and "show debuginfod"
159456 FAIL: gdb.base/default.exp: show
159671 Deal with full path in .file 0 directive
159678 need not be located in the former so GCC will use a full path in the file
159679 part when it is passed a full path:
159681 gcc -c /full/path/test.c -save-temps
159685 .file 0 "/current/directory" "/full/path/test.c"
159692 1 (indirect line string, offset: 0x38): /full/path
159696 0 0 (indirect line string, offset: 0x43): /full/path/test.c
159698 in the object file. Note the full path and the questionable Dir value in
159731 sim: split program path out of argv vector
159737 So let's split the path to the program to run out into a separate
159854 [PR gdb/16238] Add completer for the show user command
159855 The 'show user' command (which shows the definition of non-python/scheme
159976 * po/POTFILESin: Regenerate.
160100 to use a C source file instead.
160104 and C source.
160235 we have in the source tree is all we need and only thing we test.
160503 /* Avoid endless recursion if a `source' command is contained
160673 potential endless recursion when a 'source' command appears in
160677 Therefore, infinite recursion due to a 'source' command cannot happen
160683 infinite recursion check for potential 'source' commands on the
160744 --with-auto-load-safe-path=$debugdir:$datadir/auto-load
161046 time to put it in the binutils source tree. It's believed correct and
161105 source does this, and breaks with some mingw targets, so punt the
161267 The project has been using GPL v3 for a while now in the source files,
161272 source as everything is GPL v3.
161438 First, there's no dedicated CLI command to show whether the index-cache
161439 is enabled, so it has to be custom output in the "show index-cache
161441 if the index-cache is enabled. "-gdb-show index-cache" doesn't show it
161444 (gdb) interpreter-exec mi "-gdb-show index-cache"
161449 Fix this by introducing "set/show index-cache enabled on/off", regular
161626 We also delete some conditional source tree logic since we already
161865 More concretely, the breakpoint was set at the last insn show here:
162200 …help doc broken invariant: command 'show debuginfod' help doc first line is not terminated with a …
162223 sim: nltvals: pull target open flags out into a dedicated source file
162237 sim: nltvals: pull target signal out into a dedicated source file
162244 sim: nltvals: pull target errno out into a dedicated source file
162320 Use the srcroot path and make them all silent.
162428 gdb: add set/show commands for managing debuginfod
162444 Add 'show debuginfod status' command. Displays whether debuginfod
162447 Add 'set/show debuginfod urls' commands. Accepts a string of
162451 Finally add 'set/show debuginfod verbose' commands to control whether
162817 gdb: add "maint set/show selftest verbose" commands and use process_options
162824 This patch also adds the "maint set/show selftest verbose" setting. It
162842 add_show_prefix_cmd to add matching set and show commands. Add the
162856 -ex source outputs/gdb.server/server-kill-python/file1.py^M
163124 the dynamic loader's search path.
163141 with a suitable library search path specified via `-L', as it would be
163251 static buffer, so my message would show twice the same ptid. Change
163538 * po/BLD-POTFILES.in: Regenerate.
163576 * po/POTFILES.in: Regenerate.
163634 * po/POTFILES.in: Regenerate.
163659 * po/BLD-POTFILES.in: Regenerate.
163660 * po/SRC-POTFILES.in: Regenerate.
163993 I stumbled on a bug caused by the fact that a code path read
164099 Consequently, breakpoints no longer show up in the tui source window.
164145 variable offset, the patch still updates this code path, just in case.
164352 (gdb) show debug-file-directory
164355 (gdb) show sysroot
164661 but now, instead of always calling memory_error, I add a new path
164663 path is only used if m_err_memaddr doesn't have a value (indicating
165497 second source operand is an immediate.
165654 gdb/doc: improve 'show print elements' description
165655 The documentation for 'show print elements' contains the line:
165663 (gdb) show print elements
165667 'set print elements' section, however, for 'show print elements' the
165785 certain tui screen state. But we don't actually always show the state we
166002 which is a known source of problems, as explained in the comment of proc
166267 The change "make string-like set show commands use std::string
166401 custom logic. This is useful when the source of truth for a given
166422 gdb: make string-like set show commands use std::string variable
166437 but points to an empty string after doing "set solib-search-path". This
166479 The add_path function in source.c is really complex and twisted, I'd
166482 and back. This means more copying, but this is not used in a hot path
167439 --with-auto-load-safe-path=$debugdir:$datadir/auto-load
167453 --disable-source-highlight
167764 maintenance show internal-error backtrace
167767 maintenance show internal-warning backtrace
167966 if the source tree doesn't contain a gcc/ sub-directory. The result
167970 If a user builds a unified source tree, then the target tools and
168000 When I first wrote this, I was thinking we'd scan all source files
168004 though was only the source files that went into a particular build.
168006 There was another concern too: a source file might be included, but
168009 not actually available. A check of the source tree shows that we
168370 itself* (since we necessarily have a path to it).
168384 One wrinkle: if the user has overridden $NM, a path might have been
168385 provided: so we use the user-specified path if there was one, and
168386 otherwise do the path search as usual. (If the nm specified doesn't
168387 work, this might lead to a few extra pointless path searches -- but
168391 symlink to /usr/bin/nm on the PATH, and /not-on-the-path/my-nm where
168426 -L`pwd`/../libiberty/pic portion (in an indirect dep like this, the path
168427 comes from the libbfd.la file, and is an install path). libiberty also
168487 gdb: add setting to disable reading source code files
168489 try and access source code files, for example, the source code might
168493 directories' and/or 'set substitute-path' a user can trick GDB into
168494 being unable to find the source files, but this feels like a rather
168498 reading the source files. A user can run with source code reading
168500 that they now want to view the source code.
168750 Also, it show a FAIL:
168834 source-paths. See binutils/dwarf.c:
168940 …PATH: gdb.perf/backtrace.exp: python sys.path.insert(0, os.path.abspath("/home/pedro/rocm/gdb/buil…
168947 …-PASS: gdb.perf/backtrace.exp: python sys.path.insert(0, os.path.abspath("/home/pedro/rocm/gdb/bui…
168948 …-PATH: gdb.perf/backtrace.exp: python sys.path.insert(0, os.path.abspath("/home/pedro/rocm/gdb/bui…
168952 …+PASS: gdb.perf/backtrace.exp: setup perftest: python sys.path.insert(0, os.path.abspath("${srcdir…
169469 source language c.
169483 source language c.
170069 sane. Unfortunately, gas needs to handle mangled source.
170093 compiler generated file numbers. Two fixes for test case source are
170455 Using asm labels in global scope is a known source of problems, as explained
170809 The failure does not show up in the "no executable loaded" variant because
171317 Only the ppc arch supports this kind of source file override logic.
171399 "PSIZE" struct in their system headers. This doesn't show up yet as
171655 $ gdb -q -batch -ex "maint show worker-thread"
171701 string, while creating the actual set/show commands (using
171706 creating the actual set/show commands.
172092 source line, GDB was asked to step into libstdc++; a "finish" command
172095 breakpoint was set on a source line in the library after which a "run"
172103 Frames #6 thru #3 show various value preservation frames. If you look
172281 source. There are _FOR_TARGET versions of CFLAGS, CXX, and CXXFLAGS
172374 * po/BLD-POTFILES.in: Regenerate.
172465 [gdb/testsuite] Fix dwo path in fission-*.S
172485 The problem is that the executable refers to the dwo file using path name
172781 Add a show function for "maint show worker-threads"
172783 "maint show worker-threads" only reported "unlimited". This patch
172784 adds a show function so that it will now report the number of threads
172798 Assertion `path != NULL && path[0] != '\0'' failed.
173272 FAIL: objdump --source-comment
173412 using openSUSE, that didn't show up on other platforms.
174171 that Pygments may be used for source highlighting. This patch updates
174324 gdb/testsuite/gdb.asm/asm-source.exp | 6 +--
174391 maintenance show backtrace-on-fatal-signal
174654 code lives in a source file supposedly implementing IEEE-compliant
174910 * testsuite/gas/elf/dwarf-5-dir0.s: New test source file.
175358 TARGET_WAITKIND_EXECD, it,s the exec'd path name in execd_pathname.
175549 passed in buffer context) and a source type information that a result
175854 method, is not allowed in a CFI context. The source code of this
175982 context of a source level information (dwarf_evaluate_loc_desc
177518 code path for pointers.
177530 * guile/scm-math.c (vlscm_convert_typed_number): Add code path
177609 watchpoint registration path. This replicates the behaviour of the
178512 was the callback function type for set and show functions, hence the
178648 DUPLICATE: gdb.base/setshow.exp: test_setshow_args: show args
179172 show mismatches.
179215 expression printing path instead of erroring out and printing nothing
179779 `follow_child && detach_fork` path. I think we need to call it,
180413 This is because this code path never disables commit-resumed (a
180419 which does it. But the --thread-group code path uses its own thing
180421 in this code path.
180528 Choose path based on filter_ptid (all threads, all threads of
180615 status to report is something that we do quite often in the fast path
181046 -file-list-exec-source-files (unexpected output)
181048 -file-list-exec-source-files (unexpected output)
181050 -file-list-exec-source-files --group-by-objfile, look for \
181053 -file-list-exec-source-files --group-by-objfile, look for \
181108 It would only make sense to assert or report dwarf.c/readelf.c source
181273 maybe_software_singlestep is never used. This path removes
181675 * po/gas.pot: Regenerate.
181682 * po/bfd.pot: Regenerate.
182328 Commit f375d32b35ce changed a generated file. Edit the source instead.