Lines Matching +refs:po +refs:cycle +refs:source +refs:reference
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.
1370 existing gdb.Objfile and gdb.Progspace so they all reference a single
2057 that compiler will reference the runtimes installed with the
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
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
6162 /usr/lib/../lib32/libexecinfo.so: undefined reference to `elf_begin@R1.0'
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
8851 pointer/reference type, not the actual class type.
9030 ~15% off the total cycle time.
9317 - the source for the current frame,
9318 - the source for main, or
9615 source charset don't affect the DWARF index.
10014 determine whether the current source tree is a dev build (e.g.
10176 dis_nonbranch. No annotation is done for data reference instructions
10318 'source' commands are acceptable. But now, if a user does try a
10883 to GDB_AC_COMMON"), which introduced a reference before assignment:
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,
11746 A better solution might be to have the address spaces be reference counted
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
14220 * testsuite/gas/bpf/asm-extra-sym-1.s: New test source.
14227 A simple refactor to make the reference to current_program_space bubble
14239 This makes the reference to global context bubble up one level, a small
14449 (The mnemonic suffix describes the source operand, not the destination
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.
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.
19093 When printing a value, I think the history reference -- the "$1" in
19111 disposer parameter to be a reference rather than a pointer, so had to
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.
19384 manage the reference.
19438 the source of the move was.
19557 gdbsupport: use "reference" and "pointer" type aliases in intrusive_list
19583 that interps_notify did not work with reference parameters.
19586 reference (&&). Change the type of the method to be auto-deduced as an
19841 source-highlight library.
20350 executable as GDB is (via the BFD cache) holding an open reference to
20359 was holding an open reference to the file, the bfd_stat will return
21076 - Stopped passing 'nowarnings' flag when building the source file.
21077 I see no reason why this source should issue a warning,
21499 create_clear_objfiles_event_object, making the reference to
21733 A better solution might be to have the address spaces be reference
21735 call completely, and just rely on the reference count to auto-delete
22561 gdb::byte_vector and passes a reference to this byte vector to the functions,
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='.
23801 other test-cases that source unwind-on-each-insn.exp.tcl and use a .s file.
24783 included in a Source object, then the DAP client _must_ make a "source"
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
26192 than the test's source file, changes to the C++ runtime could cause
26196 reference to the inferior's output, and replacing it with '.*', which
26271 were written in the source code of tests. These were usually dummy
27364 x86: correct source used for two non-AVX512 VEXWIG tests
27767 already present, in the process keeping a reference to the malloc'd
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.
28655 [gdb/symtab] Handle self-reference in inherit_abstract_dies
28663 When encountering the self-reference DIE in inherit_abstract_dies we loop
28874 Oops there was a reference to the old name.
29467 [gdb/build] Support reference return type in make-target-delegates.py
29480 gdb/target-delegates.c:1889:22: error: ‘result’ declared as reference but not \
30441 source bit, despite operating on registers. If BPF_SRC_X (=1) is set,
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.
30878 that we need to have $srcdir in the generated #line reference back to
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.
30931 [gdb/build] Return const reference in target_read_auxv
30942 Return a const reference instead, saving a copy.
31129 [gdb/symtab] Handle self-reference DIE
31489 source.
31937 mt print symbols [-objfile OBJFILE] [-source SOURCE] [--] [OUTFILE]
31949 mt print psymbols [-objfile OBJFILE] [-source SOURCE] [--] [OUTFILE]
32402 Fix hppa64-hpux11 build to remove source paths from embedded path.
32753 c++: source position of lambda captures [PR84471]
32834 RISC-V: Add reference to Zve32*
32875 binary shrinks by almost a third (the generated source code shrinks by
32988 The DIE at 0x25 contains an intra-CU forward reference, and is deferred during
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
33818 The test-case gdb.base/index-cache.exp uses only one source file, which
33831 - adding another source file containing function foo, and
34984 Implement DAP "source" request
34985 This implements the DAP "source" request. I renamed the
35046 memory reference code:
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.
37696 done by implementing a reference counting mechanism so the underlying
40244 On MIPS, for PIC objects, symbols may reference 2 times:
40246 Thus ld may complains 2 times about "undefined reference".
40326 The alternative is 1 byte shorter when the source is %xmm0-7, as a
40460 PyModule_AddObject steals a reference on success, but not on error,
40689 source of a recent kernel. The code mentioned in the lkml.org posting
40848 gas: NEWS: Announce LoongArch changes in the 2.41 cycle
40855 binutils: NEWS: Announce LoongArch changes in the 2.41 cycle
40866 shared builds. Commit d2fddb6d783 fixed this reference but did not
40876 Fixes: d2fddb6d783 ("LoongArch: Fix ld "undefined reference" error with --enable-shared")
41572 in the spec, so we can finally remove support in the next release cycle
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
43273 a reference from the .ptid attribute of the ThreadExitedEvent
43290 2 - A python user can hold a global reference to an exiting thread. Thus
43292 reliably (both as a global reference, but also inside the thread exit
43297 that if a user holds takes a global reference to that
43540 LoongArch: Fix ld "undefined reference" error with --enable-shared
43559 gdb: update IRC reference from Freenode to Libera.Chat
43561 however, there's still a reference to Freenode in the 'gdb --help'
44168 Note that the copyright dates on the new test source file are not
44343 No source file named src/util.c.
44889 a reference to it in the bfd_map.
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
46263 I got a source window with only one line in it, and the cmd window taking most
47414 arm-linux-gnueabi: "undefined reference to `__aeabi_read_tp'"
47416 m68k-linux-gnu: "undefined reference to `__m68k_read_tp'"
47417 microblaze-linux-gnu: "undefined reference to `__tls_get_addr'"
47816 If a header file defining a static function is included in multiple source
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----------------+
49468 Use reference parameter in remove_extra_symbols
49469 Changing ada-lang.c:remove_extra_symbols to take a reference parameter
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.
50510 PR30343, LTO ignores linker reference to _pei386_runtime_relocator
50511 Make a reference to _pei386_runtime_relocator before LTO recompilation.
50512 This is done regardless of whether such a reference will be used,
50861 GDB/MI commands does not take reference types into account, so that
50865 structures passed by reference.
50878 the program stops. However, it does not take C++ reference types into
50910 a reference to a structure, which is not a simple value.
50923 of '--simple-values' so that it takes reference types into account:
50925 union, nor a reference to an array, struct or union.
50951 …* emultempl/pep.em (set_entry_point): Add an undefined reference to the entry point if it has been…
51069 commit 9b0ccb1ebae ("Pass const frame_info_ptr reference for
51095 Pass const frame_info_ptr reference for skip_[language_]trampoline
51102 …inlined from ‘void intrusive_list<T, AsNode>::push_back(reference) [with T = frame_info_ptr; AsNod…
51123 Since passing the frame_info_ptr as const reference is cheaper, use
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
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
53505 setting. The source of truth is really current_language and
54063 unbalanced braces in memory reference"), which wrongly identified
54255 to generate the man pages from the source.
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:
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:
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
56234 under bfd/po/, i.e. in maintainer mode.
56245 whether translatable strings in the source files were actually marked as
56336 of the few ways for a client to actually acquire a memory reference.
56687 changed. However, if I make that change then every reference to
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.
60796 x86: Check unbalanced braces in memory reference
60797 Check unbalanced braces in memory reference to avoid assembler crash
60808 in memory reference.
61228 depends on symbols from within the C++ source code.
61263 reference - there's no point in forcing people to parenthesize the
61463 Regen ld/po/BLD-POTFILES.in
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
62554 source line:
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.
63744 the testcase to actually use distinguishable source and destination
64112 and update the reference to Microsoft's docs.
64240 gdb: make get_interp_info return a reference
64242 so they can return a reference instead of a pointer.
64245 avoid a copying it in a local variable, instead of getting a reference.
64613 BSD's use SYS_exit rather than SYS_exit_group. Update the C source
65104 As described in C++ reference [1], static data members are not part
65703 &"No source file named mi-pendshr.c.\n"
66497 reference. Being a strong reference means that if that thread has
66561 Convert previous_inferior_ptid to strong reference to thread_info
66573 strong reference to the thread, called previous_thread.
66617 the previous_thread thread was being help due to the strong reference.
69009 * testsuite/ld-scripts/ascii.s: New test assembler source.
69029 I don't see much point in cluttering the source with the PROGRESS
70037 delete the directory from their source tree but... it doesn't make
70414 seems to me that due to reference counting, we may someday want to
70637 (gdb) source tui.py
70647 Instead, GDB retains a reference to the window factory object, which
70663 list and release the reference that is held to the underlying Python
70664 object. By releasing this reference the Python object will now be
70669 reset the reference to the underlying Python object. I don't think
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
72299 global is meant to contain a reference to the "target" sentinel, so
72816 Remove the stale reference to INFO, which is now "this target
73584 gdb: make install_breakpoint return a non-owning reference
73586 non-owning reference to it. Make install_breakpoint return a non-owning
73587 reference, to make that easy.
73778 gdb/linespec.c: Fix missing source file during breakpoint re-set
74626 that happens is the source window displays no content.
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
76148 frame-view.c:73: undefined reference to `pthread_create'
76149 ld: frame-view.c:76: undefined reference to `pthread_join'
76299 source language c.
76773 Using full pointers to reference the insn mnemonic strings is not very
76882 Likewise, the documentation is just updated to reference the new setting
77081 binutils-gdb source tries to link against it.
77249 the wrong names for some source files. Finally, a couple of obsolete
77304 Revert "gprofng: PR29987 bfd/archive.c:1447: undefined reference to `filename_ncmp'"
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
77465 gas: arm: Change warning message to not reference specific A-class architecture revision
77702 sim: common: move modules.c to source tracking
78086 gprofng: PR29987 bfd/archive.c:1447: undefined reference to `filename_ncmp'
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
79298 * po/SRC-POTFILES.in: Regenerate.
79568 reference is ambiguous and lists all possibilities. Otherwise it returns
79718 object to gdbarch_alloc and then retrieve a non-owning reference from
79838 sim: mips: add multi source to built sources
79841 In the multirun mode, be lazy and declare all of these generated source
80195 by reference, and this patch avoids the crash.
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
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
81408 (sframe_decode): Update the reference to the buffer.
81670 sim: endian: move bfd.h from header to source
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)
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
82916 When the source program contains a goto label, it turns out it's
82958 type be a pointer or reference, which the builtin_core_addr type is
83107 gdbsupport: change xml_escape_text_append's parameter from pointer to reference
83109 reference.
83139 pessimization. I changed it to passing in a reference to an std::string
83314 reference counts, we might think that we don't need to unpush targets
83336 decrements the targets reference count, it is possible that the target
83371 gdb: have target_stack automate reference count handling
83374 benefit of this change is that some of the reference counting of
83439 reference to the gdb.TargetConnection object. When the map is
83446 they have a non-zero reference count.
83456 reference count even after this final pop_all_targets call, and
83474 released, we automatically decrement the target_ops reference count.
83483 the reference out of m_stack like this:
83495 first decrement the target_ops reference count, and then set the array
83499 reference count then the target_ops object will be closed by calling
83506 By using std::move to move the reference out of m_stack, this clears
83509 scope and the reference count is decremented, target_close can run
83519 gdb/remote: remove some manual reference count handling
83520 While working on some other target_ops reference count related code, I
83521 spotted that in remote.c we do some manual reference count handling,
83526 reference count management.
83529 first, I use gdb::ref_ptr to handle the reference counts. Then,
83599 a reference to the bool control variable, and evaluating the variable
84087 to reference macro invocation sites. As mentioned in a comment this may
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.
85687 inferior_ptid reference bubble up close to the target_ops::xfer_partial
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.
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
86405 The call site does have a reference to the corresponding function f1, with
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,
89122 and updates the call to standard_testfile (removing the reference to
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
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
93098 Further, some of the source file generation (e.g. .c files, or igen,
93175 fix '@menu reference to nonexistent node `Hash tables''
93263 Note: the interf.o reference in here is a bit of a misdirect. Since
93309 that operation into a noop, so we keep a reference to the current_file
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
95178 to my SOM reference). I figure it doesn't matter since any unhandled
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.
96306 Regen ld/po/BLD-POTFILES.in
96493 files in GDB's current directory, specifically, the two source files:
96559 but in Makefile.in a critical reference to pe-aarch64.lo was missing.
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: \
99050 Add ability to create reproducible source tarballs.
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.
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.
101350 …/home/pedro/gdb/binutils-gdb/src/gdb/linux-tdep.c:1831: undefined reference to `gcore_elf_build_th…
101352 …/home/pedro/gdb/binutils-gdb/src/gdb/linux-tdep.c:2117: undefined reference to `gcore_elf_make_tde…
101370 /home/pedro/gdb/binutils-gdb/src/bfd/compress.c:42: undefined reference to `ZSTD_decompress'
101371 …/usr/bin/ld: /home/pedro/gdb/binutils-gdb/src/bfd/compress.c:44: undefined reference to `ZSTD_isEr…
101373 /home/pedro/gdb/binutils-gdb/src/bfd/compress.c:195: undefined reference to `ZSTD_compress'
101374 …/usr/bin/ld: /home/pedro/gdb/binutils-gdb/src/bfd/compress.c:198: undefined reference to `ZSTD_isE…
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
102680 ... except "b". I could not have found any reference to this operand type
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).
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.
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
104784 /tmp/build/sim/../../src/sim/erc32/interf.c:247: undefined reference to `fprintf_styled'
105041 Fix "source" with interpreter-exec
105042 PR mi/15811 points out that "source"ing a file that uses
105357 parameter declarations in the source progam.
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
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.
107840 dissably call with source code involved. E.g.
107908 As seen the reference is defined in xxx.so shared part:
108469 * testsuite/package_metadata_main.c: New test source.
108705 destruction of the BFD reference (and thus the per-bfd object) until
109267 meaning the new reference output is 18446744073709551615 instead of -1.
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…
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.
109471 resulted in user-visible changes (for example, paths to source files in
109500 to start_subfile for the main source file look up the existing
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
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
109694 least with GCC) "/an/absolute/path.c" and GDB tells you that the source
109707 symtab (what ends up shown by "info source") is just
109720 object reference, instead of an index to look up.
109879 I've used the source files in gas/testsuite/gas/aarch64/ for testing,
110108 Also added the more safe Python reference count decrement PY_XDECREF,
110114 reference counted object was not the way to go, so this has instead been
110148 to the individual locations holding a reference to
110192 source: file path and line number tuple: (string, long) / None
110230 Testsuite: tests the .source attribute and the disabling of
110369 inline-small-func.c:21: undefined reference to `callee'
110520 varobj which reference a global variable), and floating varobj (i.e.
110550 variable) and expression. All of those can reference data on an
110578 This patch also makes sure to keep a reference to the expression's
110691 .pyc files on the import of source modules.
110838 binutils-gdb/git: highlight whitespace errors in source files
110854 source file, will highlight the following whitespace errors:
110925 source files in gas/testsuite/gas/ppc and manually checked that the
111124 which need to reference section vma and lma respectively, SIZEOF can
111968 Step program until it reaches a different source line.
112083 protected symbols and non-canonical reference to canonical protected
112893 Where the source code for stap-probe.c is:
113525 that is that detach_command grabs an extra strong reference to the
114339 source files in gas/testsuite/gas/s390 and manually checked that the
114907 cycle for merging LoongArch port into the upstream Linux kernel, so
115562 Presumably this being there was a result of taking CALL as a reference
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
117054 libctf: fix linking together multiple objects derived from the same source
117145 This commit adds a cross reference to the file command for these options.
117919 removes the need for manual reference count management, and allows the
117927 constructor, without having to add one that handles the reference
118007 reference to a non-existent manpage. Provide basic
119269 The next source of content are immediate operands. The text for these
119564 windows_nat_target. This avoids having to reference the
120567 Changed offset from decimal to hex to match architecture reference
120607 x86: Properly handle IFUNC function pointer reference
120614 x86: Properly handle function pointer reference
120616 to properly handle IFUNC function pointer reference. Since IFUNC symbol
120618 function pointer reference in PDE so that it will be resolved to its PLT
120625 for IFUNC function pointer reference in PDE.
120672 cache in the background, and this would let gdb keep a reference alive
121046 check for types that are either not used in the source file (character1)
121439 binutils-gdb/gdb/loongarch-tdep.c:443: undefined reference to `loongarch_r_normal_name'
121441 binutils-gdb/gdb/loongarch-tdep.c:37: undefined reference to `loongarch_insn_length'
121443 binutils-gdb/gdb/loongarch-tdep.c:87: undefined reference to `loongarch_insn_length'
121444 binutils-gdb/gdb/loongarch-tdep.c:88: undefined reference to `loongarch_decode_imm'
121445 binutils-gdb/gdb/loongarch-tdep.c:89: undefined reference to `loongarch_decode_imm'
121446 binutils-gdb/gdb/loongarch-tdep.c:90: undefined reference to `loongarch_decode_imm'
121447 binutils-gdb/gdb/loongarch-tdep.c:91: undefined reference to `loongarch_decode_imm'
121448 binutils-gdb/gdb/loongarch-tdep.c:92: undefined reference to `loongarch_decode_imm'
121586 (gdb) source test-cmd.py
121623 (gdb) source ~/tmp/test-cmd.py
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
122192 removes the source of the warning that Luis was trying to fix).
122285 left side of the source window, with "b-" for a disabled breakpoint.
123707 * testsuite/binutils-all/no-weak.s: New test source file.
124317 At source level (as we can observe in the .ii file with -save-temps) we have
125100 * source.h: Likewise.
125771 user/kernel/vdso cycle is balanced with the addition of the "brctl"
125948 LTO: Handle __real_SYM reference in IR
125968 LDPR_PREVAILING_DEF for __real_SYM reference.
127282 alloc.c:(.text+0x20): undefined reference to `rpl_malloc'
127283 alloc.c:(.text+0x70): undefined reference to `rpl_realloc'
127290 x86: Properly handle function pointer reference
127299 to allow function pointer reference and make sure that PLT entry isn't
127300 used for function reference due to function pointer reference.
127306 pointer_equality_needed nor check non-canonical reference for
127307 function pointer reference.
128914 passing a reference to the index object to this function. This avoids
129195 cloned or used as reference here, and instead the bogus legacy forms of
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.
129876 missing commas, and fixes an incorrect reference to NewInferiorEvent.
130301 However, this work is all done without reference to any data outside
130487 if a second CU is needed to resolve an inter-CU reference, the abbrevs
130666 and alike blocks"), while dealing okay with actual assembly source files
130692 and alike blocks"), while dealing okay with actual assembly source files
131723 update the .c to reference the .h.
131764 Add a new function gdbarch_reggroups that returns a reference to a
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.
133919 but a reference was accident left in gdb/Makefile.in (in the
133920 HFILES_NO_SRCDIR variable), this commit removes that reference.
134564 Regen bfd po/SRC-POTFILES.in
135515 * DWARF DIE dumping - doesn't reference gdb_stdout.
136039 update 'chain'. I changed it to accept a const reference, making it
136562 original source file looks wrong: Upon finishing of the processing of an
136998 reference that overwrites the 'T', so if 'buf' was advanced, we'd
137358 * testsuite/gas/z80/pr28791.s: New test source file.
137614 debug print statements), due to a reference to
137687 can fold the vector shift insns with an XMM source as well. While
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
138827 the new closure captures 'pc' by reference, but later code updates
138890 gprofng: Don't generate gprofng.info in source
139004 were kept alive by an owned reference within the mi_command_py object.
139024 dictionary, and it is this reference that keeps the objects alive.
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
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
140574 This moves the copyright code from gdbarch.py to a new Python source
140580 updated copyright.py to remove the reference to gdbarch.sh. We don't
140595 source distribution, these are included in the tarball, and if the
141704 gdb: fix detection of compilation and linking flags for source-highlight
141706 source-highlight via pkg-config in GDB's configure script:
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
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
142840 reference to protected function and disable copy relocation. With
142842 be accessed via canonical reference and the protected data symbols in
142844 reference to the canonical protected function will get the run-time error:
142846 ./y: internal_f: ./libfoo.so: non-canonical reference to canonical protected function
142853 Update x86 linker to disallow non-canonical reference to the canonical
142856 ld: plt.o: non-canonical reference to canonical protected function `internal_f' in libfoo.so
142871 reference to canonical protected function.
142879 * testsuite/ld-i386/i386.exp: Check non-canonical reference to
142890 * testsuite/ld-x86-64/x86-64.exp: Check non-canonical reference
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
144476 To access this field, we need to pass down a reference to the
144480 jit_dbg_reader_data) plus a reference to the jit_code_entry as read into
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
146087 The simple fix is to reference the array, `MEMS' as the destination of the copy.
146112 reference, as explained in the comment. I think it would make sense to
146114 return a const reference.
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)
147573 and thus correctly have no version reference added. Causing failure
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
148888 There is a expect support library in the source tree designed to help
149209 * configure.ac: Remove reference to priv spec 1.9.
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
149504 includes full paths to the source files.
150355 out */po/*.pot which we don't update frequently.
152261 offset/constant reference DW_FORMs being given an indexed string
152433 the code to check that the source string length is smaller than the
152531 the comments in the header and source files.
152895 .../src/gdb/mips-tdep.c:8730: undefined reference to `disassembler_options_mips'
152897 .../src/gdb/riscv-tdep.c:3851: undefined reference to `disassembler_options_riscv'
152942 I found some uses of xfree in the path substitution code in source.c.
153041 …/home/simark/src/binutils-gdb/gdbserver/../gdbsupport/tdesc.cc:407: undefined reference to `tdesc_…
153042 …simark/src/binutils-gdb/gdbserver/../gdbsupport/tdesc.cc:408: undefined reference to `tdesc_archit…
153043 …simark/src/binutils-gdb/gdbserver/../gdbsupport/tdesc.cc:411: undefined reference to `tdesc_osabi_…
153044 …simark/src/binutils-gdb/gdbserver/../gdbsupport/tdesc.cc:416: undefined reference to `tdesc_compat…
153045 …simark/src/binutils-gdb/gdbserver/../gdbsupport/tdesc.cc:418: undefined reference to `tdesc_compat…
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)
154450 gdb: change some alias functions parameters to const-reference
154452 pass cmd_list_element arguments by const-reference rather than by
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.
154539 ranges as well as three kinds of overlapping ranges: source before dest,
154540 dest before source, and dest == source.
154571 Make the setters return the "this" object as a reference, such that it's
154581 However, making the setters return a reference to the object achieves
154648 the error is thrown. If the only reference to the target is the one
154661 then decrements the reference count on the remote_target object. This
154768 debugformat field") changes the debug format string in "info source" to
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
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
156865 /usr/bin/ld: extension.o:(.rodata+0x120): undefined reference to `extension_language_python'
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.
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.
157437 gdb: pass more const target_waitstatus by reference
157439 const target_waitstatus objects could be passed by reference instead of
157455 As a convenience, make string_appendf return the same reference to
157597 - readelf interprets the DW_FORM_line_strp reference to .debug_line_str as
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
158367 * testsuite/gas/all/multibyte.s: New test source file.
159207 In the next commit I'd like to reference gdb_unique_ptr within the
159213 include to common-utils.h I was getting a dependency cycle; before my
159217 To break this cycle, I propose to move xfree into its own header file,
159349 RISC-V: Scalar crypto instruction and entropy source CSR testcases.
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
161034 we might want to be able to pass bpstats objects by const-reference, not
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.
161465 by const reference. This is not necessary for scalar values (like bool
161479 value by value instead of by reference, when the underlying data type is
161626 We also delete some conditional source tree logic since we already
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
162635 src/gdb/maint.c:1183: undefined reference to \
162856 -ex source outputs/gdb.server/server-kill-python/file1.py^M
163139 reference sneaked through to the linker directly behind libtool's back
163150 with no link-time reference to the installation directory other than to
163154 Use a direct reference to `libbfd.la' then, making the load error quoted
163360 * testsuite/ld-ctf/conflicting-cycle-1.B-1.d: Likewise.
163361 * testsuite/ld-ctf/conflicting-cycle-1.B-2.d: Likewise.
163362 * testsuite/ld-ctf/conflicting-cycle-1.parent.d: Likewise.
163363 * testsuite/ld-ctf/conflicting-cycle-2.A-1.d: Likewise.
163364 * testsuite/ld-ctf/conflicting-cycle-2.A-2.d: Likewise.
163365 * testsuite/ld-ctf/conflicting-cycle-2.parent.d: Likewise.
163366 * testsuite/ld-ctf/conflicting-cycle-3.C-1.d: Likewise.
163367 * testsuite/ld-ctf/conflicting-cycle-3.C-2.d: Likewise.
163368 * testsuite/ld-ctf/conflicting-cycle-3.parent.d: Likewise.
163373 * testsuite/ld-ctf/cross-tu-into-cycle.d: Likewise.
163375 * testsuite/ld-ctf/cycle-1.d: Likewise.
163376 * testsuite/ld-ctf/cycle-2.A.d: Likewise.
163377 * testsuite/ld-ctf/cycle-2.B.d: Likewise.
163378 * testsuite/ld-ctf/cycle-2.C.d: Likewise.
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.
164099 Consequently, breakpoints no longer show up in the tui source window.
165497 second source operand is an immediate.
165918 inferior object ensures that the reference count on the Python
165941 pointer to nullptr and finally reduces the reference count on the
165944 If at this point the user still holds a reference to the Python
165958 we (a) set the gdb.Inferior reference inside GDB's inferior to
165963 1. The Python gdb.Inferior reference within GDB's inferior object
165964 holds a reference count, thus, setting this reference to nullptr
165965 without first decrementing the reference count would leak a
165966 reference, however...
165968 2. As GDB's inferior holds a reference then infpy_dealloc will never
165971 reference. At this point there is no longer a need to call
165973 have been cleared in order to get the reference count to zero, which
166002 which is a known source of problems, as explained in the comment of proc
166401 custom logic. This is useful when the source of truth for a given
166479 The add_path function in source.c is really complex and twisted, I'd
166560 setting can be constructed from a pre validated type erased reference to
166568 Given that a cmd_list_element may or may not reference a setting, the
167453 --disable-source-highlight
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
168487 gdb: add setting to disable reading source code files
168489 try and access source code files, for example, the source code might
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.
168592 GDB doesn't know the stack is corrupted (with a cycle), GDB still
168656 return nullptr when it sees a cycle.
168696 cycle detection for inline frames, even when we spot a duplicate frame
168834 source-paths. See binutils/dwarf.c:
169469 source language c.
169483 source language c.
170038 on being able to get the value from such variables, using a named reference.
170064 fields might reference a previous .loc. It becomes a little more
170067 info on seeing compiler generated line info, so any reference back
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
171317 Only the ppc arch supports this kind of source file override logic.
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"
172281 source. There are _FOR_TARGET versions of CFLAGS, CXX, and CXXFLAGS
172374 * po/BLD-POTFILES.in: Regenerate.
173272 FAIL: objdump --source-comment
174171 that Pygments may be used for source highlighting. This patch updates
174324 gdb/testsuite/gdb.asm/asm-source.exp | 6 +--
174654 code lives in a source file supposedly implementing IEEE-compliant
174910 * testsuite/gas/elf/dwarf-5-dir0.s: New test source file.
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
179171 pointer/reference types in a special way, so we can validate tags and
179200 pointer or reference type first, and only if so then proceed to check
180239 makes detach_command hold a reference to the target, so the remote
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
181165 3. Treate reference to protected symbols with indirect external access
181675 * po/gas.pot: Regenerate.
181682 * po/bfd.pot: Regenerate.
182328 Commit f375d32b35ce changed a generated file. Edit the source instead.