Lines Matching +refs:po +refs:auto +refs:edit +refs:with +refs:msgid

25 … s9 register) and a0aa6f4ab (LoongArch: ld: Add support for TLS LE symbol with addend) to 2.42 bra…
90 	aarch64: Eliminate unused variable warnings with -DNDEBUG
159 	Append "#pass" to APX tests for targets which pad text sections with NOPs.
177 	x86/APX: be consistent with insn suffixes
183 	This was missed in 6177c84d5edc ("Support APX GPR32 with extend evex
214 	PR30824 internal error with -z pack-relative-relocs
230 	configured with --enable-default-hash-style=gnu.
277 	Along with the relevant unit-tests, this adds the following rcpc3
295 	with `#<simm>' taking on a signed 8-bit integer value in the range
301 	Along with the relevant unit tests and updates to the existing
335 	The particular choices of address indexing, along with their encoding
337 	descriptions, along with the relevant inserter/extractor set.
343 	pre-indexed with writeback for Store-Release insns.
354 	post-indexing or pre-indexing with writeback is available.  This
356 	AARCH64_OPND_ADDR_OFFSET, with the difference that FLD_index should
369 	pre-indexed with write-back.
374 	disassembly, along with the definition of two insn fields for use with
412 	Binutils, together with the necessary macro for encoding rcpc3
448 	nm: Replace --with-symbol-versions with --without-symbol-versions in --help output
511 	along with +sve2p1 optional flag to enabe this feature.
529 	along with the optional flag +sme2p1.
572 	When a test is executed with --scfi=experimental command line option,
582 	    --x32 with SCFI results in hard error.
593 	machinery in GAS currently issues, with an intent to help user correct
793 	- GAS instructions are ID's with a natural number in order of their
803 	register is updated with the result of the address calculation: before
805 	instructions like GINSN_TYPE_LOAD, GINSN_TYPE_STORE together with
815 	the user enables SCFI with --32, GAS issues an error:
821 	   - Hand-written asm block must begin with a .type   foo, @function
823 	   - Hand-written asm block ends with a .size foo, .-foo
825 	The SCFI machinery encodes some rules which align with the standard
867 		(i386_target_format): Add hard error for usage of SCFI with non AMD64 ABIs.
971 	--scfi=inline option for dealing with inline asm may be added in the
1062 	[gdb/testsuite] Fix gdb.mi/mi-dprintf.exp with read1
1063 	When running test-case gdb.mi/mi-dprintf.exp with check-read1, I run into:
1094 	Tested on x86_64-linux, with:
1100 	[gdb/testsuite] Fix gdb.cp/namespace.exp with read1
1185 	The following change broke simulator testsuite with host GCC 13:
1187 	  sim: warnings: compile build tools with -Werror too
1321 	with Clang.
1355 	can (hopefully) avoid conflicting with any future attributes that GDB
1360 	  1. Don't start user attributes with a lower case letter, all the
1361 	  current GDB attributes start with a lower case letter, and I suspect
1362 	  all future attributes would also start with a lower case letter, and
1364 	  2. Don't start user attributes with a double underscore, this risks
1365 	  conflicting with Python built in attributes (e.g. __dict__) - though
1366 	  clearly the user would need to start and end with a double
1440 	As the new gdb.Progspace object is not associated with an actual C++
1492 	which is inline with how other invalid objects are displayed.
1520 	Which is inline with how other invalid objects are displayed.
1549 	gdb: add trailing '/' when using 'complete' with directory names
1586 	with the complete filename options support.
1602 	path starting with a tilde character.
1635 	'break f1' then, as 'f1' is a unique match, we'd get 'break f1 ' with
1730 	`get_prev_frame_always (next_frame)` with `next_frame`in the call to
1755 	The test-case attemps to emulate additional entry points of a function, with
1901 	We've been building this file with -Wno-error, so clean up unused
1912 	gdbsupport: tighten up libiberty code a bit with dnl
1952 	This directory contains example programs for the user to experiment with.
2034 	    will attempt to create site.exp if it doesn't exist and will interfere with
2051 	    embedded runpath to executables (and libraries with dependents).
2056 	    For an installed compiler, it means that any executable built with
2057 	    that compiler will reference the runtimes installed with the
2252 	Note that this bug would not be possible with my type-safe hash table
2288 	Add --enable-mark-plt linker configure option to mark PLT entries with
2430 	only ever used together with SAE (hence why the overlaying works in the
2443 	Synchronize sourceware version of the libiberty sources with the master gcc versions.
2450 	    libiberty: Fix build with GCC < 7
2452 	    Tobias reported on IRC that the linker fails to build with GCC 4.8.5.
2506 	    cases found by running the testsuite with -Wabi forced on:
2525 	    I aim to resolve these with the ABI committee before GCC 14.1.
2551 	    broke Solaris/x86 bootstrap with the native as:
2563 	    Tested on i386-pc-solaris2.11 with as and gas.
2574 	    If anyone from ARM would be willing to implement it similarly with
2589 	    Regenerate libiberty/aclocal.m4 with aclocal 1.15.1
2592 	    with the correct versions (automake 1.15.1 and autoconf 2.69).
2595 	    Correct one file that was generated with the wrong version.
2628 	    r13-4035 avoided a problem with overloading of constrained hidden friends by
2629 	    checking satisfaction, but checking satisfaction early is inconsistent with
2645 	    these friends as a member function with an extra 'F' before the name.  I
2706 	  * When a `tlbip' operation is labeled with the `F_HASXT' flag, xzr
2708 	  optional register needs to be specified with a non-xzr value.
2718 	starting with Armv9.4-a, a mechanism for manipulating their contents
2719 	is introduced with the `msrr' and `mrrs' instruction pair.
2744 	invalidate (TLBI) operations and barriers can also be annotated with
2747 	With the introduction of the 128-bit translation tables with the
2751 	with the `tlbip' insn.
2758 	The addition of 128-bit page table descriptors and, with it, the
2761 	with the new 128-bit model.  This is introduced with the `tlbpi'
2787 	range of operand values for fields in the instruction tagged with the
2822 	this with relatively few changes to existing code.
2907 	possible -march options in Binutils, together with the necessary macro
2912 	sim: warnings: compile build tools with -Werror too
2913 	Add support for compiling build tools with various -Werror settings.
2914 	Since the tools don't compile cleanly with the same set of flags as
2924 	Fix warnings from calling printf functions with "" which normally
2934 	Leave the igen code in place as it's meant to be used with newer
3007 	When gdb starts up with a symbol file, it uses the program's "main" to
3179 	None of that is relevant for us with current automake, so drop it.
3252 		`fp=64' used with a 32-bit ABI
3281 	when running it with "taskset -c 0" I run into:
3305 	or to aarch64linux.sh with Linux-specific logic removed; and mainly different
3308 	Coupled with a corresponding GCC patch, this produces a toolchain that can
3314 	On aarch64-linux, with gcc 13.2.1, I run into:
3324 	   backtrace (with wrong libs) (data collection)
3325 	 FAIL: gdb.base/solib-search.exp: backtrace (with wrong libs)
3360 	   backtrace (with wrong libs) (data collection)
3361 	 PASS: gdb.base/solib-search.exp: backtrace (with wrong libs)
3390 	replace S with L on adcx and adox.
3404 		(prefix_table): Replace S with L on adcx and adox.
3410 	This brings us in sync with current set of gdb warnings (for C).
3517 	There are a number of issues with 734dfd1cc966 ("x86: pack CPU flags in
3519 	- the condition when two array slots need writing wasn't correct (with
3561 	While there also drop two adjacent redundant (with read.h) declarations
3567 	While there doesn't look to be anything wrong with this override,
3586 	other precautions against subsections being used on ELF with .bss. It
3598 	pru: fix .text/.data interaction with .previous
3613 	other precautions against subsections being used on ELF with .bss. It
3623 	ELF and COFF have. While in this case interaction with ELF's .previous
3626 	d30v: fix .text/.data interaction with .previous
3639 	against subsections being used on ELF with .bss. It also doesn't look
3651 	other precautions against subsections being used on ELF with .bss. It
3676 	Avoid an error when compiling with older versions of gcc.
3769 	a backtrace, any addresses that required unmasking will be postfixed with the
3796 	2) Run "etc/update-copyright.py --this-year" with an extra external
3799 	3) Build with --enable-maintainer-mode --enable-cgen-maint=yes.
3800 	4) Check out */po/*.pot which we don't update frequently.
3804 	Synchronize config.sub and config.guess with their upstream master versions.
3823 	With old "medium" code model, we call a function with a pair of PCALAU12I
3832 	If "g" is a data symbol and ld with -shared option, it may load two
3870 	that gcc produces, with some kind of '~~~~~^' marker on the second
3906 	object and often combined with other output, it's not immediately
3936 	and -mla-global-with-abs.
3939 	also satisfy 32 pcrel, using -mabi=ilp32* and -mla-global-with-abs
3954 	module is still pretty similar in API, so we can unfork them with
3966 	is still pretty similar in API, so we can unfork them with a little
3998 	The common/ code has macros with the same name but different behavior:
4003 	sim: ppc: sync WITH_TARGET_{ADDRESS,CELL}_BITSIZE with common/
4080 	compiled with:
4087 	Now let's debug it with target record, using current gdb git master
4154 	Now let's undo the "next", with "reverse-next":
4241 	Patch has been tested on PowerPC, X86 and AArch64 with no regressions.
4250 	Patch has been tested on PowerPC with both gcc and clang.
4259 	While the standard allows for multiple points marked with epilogue_begin
4289 	then with the port name like we do with all other ports.
4349 	to the top-level build, and matches what we did with the common/ hw
4380 	sim: ppc: fix bad AC_CACHE_CHECK call with semun
4412 	We want to avoid conflicts with the common igen enums.  This should
4424 	sim: ppc: replace filter_filename with lbasename
4451 	registers, but it does so incrementally with bit operations, and it
4485 	On aarch64-linux with a gdb build without libexpat, I run into:
4520 	The gdb docs promise that methods with more than two or more arguments
4564 	Please DON'T edit this file.  READ THE COMMENT!
4578 	Append "#pass" to APX tests for targets which pad text sections with NOPs.
4589 	x86: Don't use .insn with '/'
4590 	'/' starts a comment for some targets.  Use .byte instead of .insn with
4594 		instead of .insn with '/'.
4627 	After this patch it is possible to set a breakpoint in gdb with the
4662 	a second variation to retrieve the pc bounds for DIEs tagged with
4780 	with the programming model of the 'V' extension ([1]), we consider
4837 	if the instruction is encoded with the REX2 prefix when possible.
4898 	if the instruction is encoded with the REX2 prefix when possible.
4924 		(output_insn): Don't add empty REX prefix with REX2 prefix.
4960 	if the instruction is encoded with the REX2 prefix when possible.
5006 	if the instruction is encoded with the REX2 prefix when possible.
5216 	Add tests for APX GPR32 with extend evex prefix
5240 	Support APX GPR32 with extend evex prefix
5269 		(md_assemble): Handle apx with evex encoding.
5324 	Support APX GPR32 with rex2 prefix
5346 		opcode 0/1 use gpr32 with rex2 prefix.
5358 		target apx, 64-bit mode and with rex_prefix.
5418 	This patch fixes simulator to align with latest recommendations from TI.
5432 	RISC-V: PR31179, The SET/ADD/SUB fix breaks ABI compatibility with 2.41 objects
5443 	relocations with non-zero addend.
5452 	write the .reloc R_RISCV_SUB* with non-zero constant, and then report
5467 		rebuild the objects with binutils 2.42 and up, to get the right zero
5511 	into our table too.  The values don't conflict with each other -- the
5611 	inline frame as the next frame id of register struct values, and go with
5624 	Remove VALUE_REGNUM, replace it with a method on struct value.  Set
5634 	Remove VALUE_NEXT_FRAME_ID, replace it with a method on struct value.  Set
5656 	This is no longer relevant, since we now create a value with a valid next
5763 	that requires initializing variables like "res" with something.
5839 	Rename shadowed vars with different types to avoid confusion.
5882 	Rename shadowed vars with different types, and delete redundant decls.
5885 	Rename the shadowed var to avoid confusion with the function argument
5891 	retained, and fix some weirdness with nested enums in structs.
5953 	Fix build with clang 16
5955 	these operators to be declared starting with C++14, but apparently
5994 	warning fixes with "val" variables.
6030 	nios2: fix .text/.data interaction with .previous
6036 	hppa/ELF: fix .text/.data interaction with .previous
6053 	x86-64: refuse "high" 8-bit regs with .insn and VEX/XOP/EVEX encodings
6055 	only starting with APX - permit use of "new" 8-bit registers only. %ah,
6073 	with .insn we can't make assumptions anymore on all respective templates
6108 	This will make compiler diagnostics much better with generated code
6149 	to do with backtraces.  This patch renames them to "tui-status".
6171 	Fix Clang build issue with flexible array member and non-trivial dtor
6175 	That caused a build problem with Clang, which errors out like so:
6178 …> gdb/python/py-unwind.c:126:16: error: flexible array member 'reg' of type 'cached_reg_t[]' with …
6183 	whole structure with xmalloc, and then initializes the array elements
6184 	with in-place new, and then takes care to call the destructor
6222 	Replace some fall through comments with the attribute.
6230 	Replace some fall through comments with the attribute.
6233 	Replace some fall through comments with the attribute.
6245 	Replace some fall through comments with the attribute.
6251 	Replace some fall through comments with the attribute.
6257 	Replace some fall through comments with the attribute.
6260 	Replace some fall through comments with the attribute.
6263 	Replace some fall through comments with the attribute, and add some
6268 	Replace some fall through comments with the attribute.
6302 	This helps the compiler with optimization and fixes fallthru warnings.
6309 	This helps the compiler with optimization and fixes fallthru warnings.
6365 	with the amd-dbgapi target's handling of exited threads.  The test
6370 	The test spawns a kernel with a number of waves.  The waves do nothing
6451 	with one entry for each wave, that seems like the place to store that
6572 	wave is gone and deletes it with delete_thread_silent.
6575 	set_thread_exited (with the default silent=false) early, which emits
6584 	displaced_step_finish can be called with event_status.kind ==
6616 	"si", we always end up with the exiting thread as selected even
6634 	- Add a third axis to stepping over the breakpoint with displaced vs
6635 	  inline stepping -- also test with no breakpoint at all.
6643 	- Fixes a race that Simon ran into with GDBserver testing.
6650 …(gdb) FAIL: gdb.threads/step-over-thread-exit.exp: displaced-stepping=auto: non-stop=on: target-no…
6664 	  new threads when testing with "cmd=continue" and schedlock off, in
6693 		 we acknowledge it with vStopped.  But clear its contents, so
6702 	Complete use of unique_ptr with notif_event and stop_reply
6703 	We already use unique_ptr with notif_event and stop_reply in some
6738 	mnemonics with their condition (e.g. "on A high"). This complements
6760 	Print instruction description as comment in disassembly with s390
6763 	- For objdump it can be enabled with option "-M insndesc"
6764 	- In gdb it can be enabled with "set disassembler-options insndesc"
6771 	Or when using in combination with objdump option --visualize-jumps:
6778 	s390-opc.o with instruction descriptions   : 348432 bytes
6827 	to strerr and either continues processing or exists with a non-zero
6850 	Provide descriptions for instructions introduced with commit ba2b480f103
6879 	Suffix the s390-mkopc build utility executable file name with
6880 	EXEEXT_FOR_BUILD. Otherwise it cannot be located when building with
6963 	which is used with software watchpoints, since the expression of the
7058 	performed for symbols with hidden visibility. For example, if a.c is:
7067 	If compiling and linking with:
7093 	Tested by running ld test suite, bootstrapping and regtesting GCC with
7094 	the patched ld, and building and testing Glibc with the patched ld.  No
7106 	problem as we saw with right shifts.  The input value may have been sign
7272 	We already build cleanly with these.
7296 	When compiled with optimization, the entry point of foo is at
7375 	readline_hidden_cols by comparing the environment variable COLS with cols as
7411 	While experimenting with can_box () == false by default, I noticed two places
7412 	in tui-regs.c where we can replace a hardcoded 1 with box_width ().
7415 	the last char of the last line with register info will cause a scroll.
7588 	revert "x86: allow 32-bit reg to be used with U{RD,WR}MSR"
7608 	redundant with just ATTMnemonic. Drop the now meaningless ATTSyntax and
7678 	For example, with an introduced error, we can see w/gcc-13:
7687 	(with this change)
7709 	with fuzzed objects.  Restore those checks.  Also, for dwo look at
7767 	follow the same pattern, just with different registers.
7879 	For consistency with the declarations around.
7889 	registers needed to make up the pseudo register value.  The problem with
8018 	with frame_register_unwind.
8081 	with one {get,put}_frame_register_bytes calls), and in which situation.
8109 	when connecting with other APIs already using gdb::array_view.
8135 	be converted to use array_view with not much work, in which case these
8229 	end up calling raw_read with the same regnum as the function received
8354 	as the forward execution command, but with the opposite case. This way
8416 	what was wrong with their input, and what they should do to fix
8425 	is a permissions issue with '/tmp/hello', which is not the case.
8611 	with auipc+addi.
8613 	We can't rewrite all existing auipc+ld pairs with auipc+addi in the
8621 	This patch is to annotate R_RISCV_GOT_HI20 with R_RISCV_RELAX only
8644 	RISC-V: Resolve PCREL_HI20/LO12_I/S fixups with local symbols while `-mno-relax'
8648 	will finish the fixup of the local relocations while with `-mno-relax' option.
8655 	Besides, maybe not only pcrel_hi/lo12 relocation with local symbols can be
8671 		the pcrel_hi relocs, mark as done while with `-mno-relax'.  For
8672 		PCREL_LO12_I/S relocation, do fixup and mark as done while with
8675 		* config/tc-riscv.h (md_end): Define md_end with riscv_md_end.
8781 	with the more strict:
8817 	classes with virtual methods are involved, some of the results
8850 	And the TEM value at the value address was created with the
8937 	and overflow checking.  gold had all of the bfd problems with this
8998 	A bit of digging with perf shows that we're spending a crazy amount of time
9016 	things with encoding branches in the 0x4XYY opcode space.  It uses an "always
9056 	Fix this by increasing available_size for fixed-size layouts with shared box.
9119 	in most cases the <some pattern> could be replaced with "\r\n" though
9176 	style commands.  Just like with the previous commit, the COMPONENT can
9184 	the components have to be entered one at a time with the monitor
9193 	text, again, this feels more inline with GDB's existing boolean
9240 	component with '-' to disable that component, so I can write:
9372 	gdb.python/py-symtab.c with clang, I noticed that it was going wrong
9381 	behavior with trailing !is_stmt lines", but that commit only changes the
9469 	The cgen code mixes virtual insn enums with insn enums, and there isn't
9486 	Debugging applications with "record full" fail to record with the error
9501 	Sync with the list of flags from gdbsupport, and add a few more of
9503 	as we don't build with C++.
9509 	which claims to "Test stepping and other mundane operations with
9577 	The new behavior started with 9675da25357c7a3f472731ddc6eb3becc65b469a,
9604 	The previous patch fixed the immediate performance problem with Ada
9686 …715: constexpr const _Tp& std::clamp(const _Tp&, const _Tp&, const _Tp&) [with _Tp = int]: Asserti…
9688 	This may only be visible because I compile with:
9741 	Commit 0e3c1eebb22 made the output match that seen with a 64-bit host
9761 	libiberty: Fix build with GCC < 7
9762 	Tobias reported on IRC that the linker fails to build with GCC 4.8.5.
9783 	Fix breakpoints on symbols with multiple trampoline symbols
9797 	[Inferior 1 (process 10004) exited with code 03]
9806 	[Inferior 1 (process 5532) exited with code 03]
9876 	not familiar with the MIPS ISA in these cases, these look like
9878 	fixes compiling with -Wenum-conversion.
10032 	Fix building with -Wmisleading-indentation.
10042 	clashing with the system ones and leading to build failures with
10047 		zero-parameter prototype in C2x, conflicting with a previous
10061 	Fix this by running the test with --hash-style=sysv, and adjust
10100 	by replacing them with '@@'. This was already done for the
10158 	Annotate the (conditional) jump and branch relative instructions with
10182 	print_address_func() is only called with addresses and never with
10203 		  instructions with information for jump visualization.
10230 	of threads on many-core systems under environments with restrictive
10262 	GDB built with GCC 13.
10279 	The clamping was tested on machines with both 16 cores and a single
10382 	reproducer script does (with regard to shutting things down), but
10425 	problems with detach.  Upon hearing of this problem, he came up a test
10433 	For the LWP exit / termination case with no checkpoint, that's handled
10446 	Lastly, I'll note that the checkpoint code needs some work with regard
10449 	the situation with detach because, due to the check noted above,
10451 	are multiple inferiors.  (There are at least two other problems with
10468 	with no checkpoint, process termination with no checkpoint, process
10469 	exit with a checkpoint, and process termination with a checkpoint.
10501 	files which should be avoided with -r option for linker tests.
10504 	linker tests with -r.
10508 		for tests with --64.  Remove -nostdlib for tests with -r.
10589 	   aarch64_linux_collect_za_regset calls `regcache->collect_regset` with
10591 	 - transfer_regset gets called with a buffer size of 0.
10643 	This was observed with upcoming GCC improvements which eliminate
10674 	completion. The difference is that when testing with the complete
10699 	ld: fix build with old makeinfo
10706 	warning with at least some gcc versions.
10723 	fiddling with that's "guilty" in that fiddling being suppressed.
10746 	x86: allow 32-bit reg to be used with U{RD,WR}MSR
10778 	riscv_is_mapping_symbol currently accepts any symbol that starts with $x
10802 	coprocessor, it able to encoding opcode like .insn but with predefined
10844 	before ratification and this has happend with the vector crypto
10972 	broke Solaris/x86 bootstrap with the native as:
10984 	Tested on i386-pc-solaris2.11 with as and gas.
11109 	modified to support the GNU style long option syntax.  Compatibility with
11200 	Of all the changes, this is possibly the one with the biggest
11208 	is going to break after this commit.  I think we can live with this
11248 	gdb_get_worker_threads.  This proc uses gdb_test_multiple with two
11249 	possible patterns.  One pattern is anchored with '^', while the other
11292 	strlen with a string literal argument:
11296 	is replaced with sizeof:
11308 	SINGLE_KEY) lower-case, but that clashed with a pre-existing pc_prefix, so
11361 	sha_ni ISA support) without/with the patch and on AMD Ryzen 5 3600
11362 	(which does have it) without/with the patch.
11418 	board, I have to run make-check-all.sh with --verbose and --dry-run in
11421 	I always run with --keep-results on, so, in this commit, I propose
11452 	a given GDB build with a given executable), and by sorting the chains
11486 	compiled with the same tool-chain, we should get the exact same output
11548 	size of 90M, with a hash usage (in the generated index file) of just
11552 	I now see a gdb-index file size of 30M, with a hash usage of 41.9%.
11726 	- a program space with an address space is created
11730 	- a second program space with the same address space is created
12290 	[gdb/testsuite] Add boards/cc-with-index-cache.exp
12291 	We have a target board cc-with-gdb-index that uses the gdb-add-index script to
12296 	Add a new target board cc-with-index-cache.
12300 	  index-cache does: the index-cache can add an index to an exec with a
12301 	  .gnu_debugaltlink (note that when using the cc-with-gdb-index board this
12311 	Shell script changes checked with shellcheck.
12452 	else in the Python completion code, we instead just return with the
12556 	The reason is that cmdline is read with target_fileio_read_stralloc(),
12565 	Commit 27b33966b18e "RISC-V: disallow x0 with certain macro-insns"
12579 	Deal with what 58bceb182740 ("x86: prefer VEX encodings over EVEX ones
12593 	RISC-V: disallow x0 with certain macro-insns
12614 	Fix building for the s390 target with clang
12664 	be added, as they would clash with the existing non-standard extended
12778 	exercise the brasl mnemonic with its largest allowed negative and
12780 	addressing mode. Therefore the ESA test cases are assembled with -m31.
12785 	Therefore the z/Architecture (zarch) test cases are assembled with -m64.
12804 	Use regular expressions with backreferences to verify results of test
12805 	cases containing instructions with relative addressing. This makes the
12828 	Reformat gdb/python/lib/gdb/missing_debug.py with black after commit
12833 	Fix build with GCC 7.5
12834 	A recent change to 'struct field' caused a build failure with GCC
12851 	for packing reasons in ancient times, but with m_accessibility not
13199 		* riscv-dis.c (print_insn_args): Prefix the CSRs disassembly with 'th'.
13216 	of the "TheadVector" instructions overlaps with those of
13255 …The reason for the same was GDB core trying to switch to a child thread with tid not set that does…
13267 	When starting TUI in a terminal with 3 lines:
13279 	This discrepancy eventually leads to a call to newwin in make_window with:
13316 	When starting TUI in a terminal with 2 lines (likewise with 1 line):
13332 	This discrepancy eventually leads to a call to newwin in make_window with:
13367 	I ran into a failure in test-case gdb.python/py-missing-debug.exp with python
13371 	However, I subsequently ran into a failure with python 3.11:
13391 	I could just install it, but the test-case worked fine with 3.11 before commit
13396 	Tested on x86_64-linux, with both python 3.6 and 3.11.
13529 	bpf: Fixed register parsing disambiguating with possible symbol.
13530 	This changes parse_bpf_register to detect possible symbols that start with valid
13595 	[gdb/testsuite] Fix spurious FAILs with examine-backward.exp, again
13596 	Commit 59a561480d5 ("Fix spurious FAILs with examine-backward.exp") describes
13672 	gdbsupport: Replace gdb::invoke_result with std::invoke_result
13674 	with std::invoke_result which is provided by <type_traits>.
13688 	and the tests which came with it.
13716 	gdb::string_view with std::string_view.
13747 	as well as the self-tests which came with it.
13755 	gdb: Replace gdb::optional with std::optional
13773 	gdb::make_unique is a wrapper around std::make_unique when compiled with
13853 	gdb: Fix segfault with a big .dynamic section size
13854 	Consider a binary with an erroneous size of the .dynamic section:
13863 	section into memory allocated on the stack with alloca().  However, the
13903 	function.  The test must be compiled with -fvar-tracking for the
13911 	The patch has been tested on Power 10 and X86-64 with no regressions.
13929 	with different "CU name"s: the ctf_link() following that will put all
13933 	So it's clear enough what happens if you call it repeatedly with the same
13935 	what if you call it with the same "CU name" repeatedly?
13958 	gdb: fix reopen_exec_file for files with target: prefix
13967 	executables with a target: prefix.  Before this commit we used the
13968 	system 'stat' call, which obviously isn't going to work for files with
13975 	The program_space::ebfd_mtime variable, with which we compare the
13976 	result of bfd_stat is set with a call to bfd_get_mtime, which in turn
13998 	target (i.e. one with a 'target:' prefix).
14000 	To do this I have replaced a system 'stat' call with a bfd_stat call.
14011 	prompt, or with the inferior running, and then later we use bfd_stat
14014 	This is of course slightly different than using system stat on with
14041 	bfd, so I fixed this (with another bfd_cache_close_all() call), and
14048 	I see two problems with the current approach:
14080 	  in this case we don't display a prompt.  As with (a) above, when an
14090 	with the following commit.
14092 	However, I see a problem with this solution.
14185 	tries again with a new instruction template. However, symbols created
14257 	the callers pretty much always know which thread they are dealing with.
14323 	DAP specifies that a request can fail with the "notStopped" message if
14427 	ELF-only functions don't need to be built when dealing with a non-ELF
14429 	dealing with non-AOUT targets. Similarly tc_fix_adjustable() can be a
14432 	Furthermore x86_elf_abi is already used in ELF-only code sections, with
14482 	When calling ld with --no-relax, pcalau12i + ld.d still can be relaxed.
14483 	This patch fix this bug and pcalau12i + ld.d can be relaxed with --relax.
14527 	The same is true for str.isalnum(), which is replaced with
14635 	319b460545dc79280e2904dcc280057cf71fb753), with:
14686 	For now, this commit just makes the testcase cope with the non-one
14711 	found with an older version of GNAT -- it emits a duplicate "x".
14738 	  * intl: Remove directory.  Replaced with out-of-tree GNU gettext.
14740 …with gettext. (hbaseargs, bbaseargs, baseargs): Split baseargs into {h,b}baseargs. (skip_barg): Ne…
14742 …* Makefile.def (host_modules): Replace intl module with gettext module. (configure-ld): Depend on …
14790 	end decided to fix it in gdbserver, with the reason being that it
14868 	Replace some spaces with tabs.
14948 	All but one regexps in the .exp file use "clone\[23\]?" with "?" to
15008 	information handler objects, and registers these handlers with GDB.
15096 	  3. Check with debuginfod to see if it can supply the required
15147 	objfile::find_and_add_separate_symbol_file, with some additional
15148 	logic, so starting with a simpler function will make the following
15189 	As with the previous commit, I've done some minimal testing using the
15197 	gdb/coffread: bring separate debug file logic into line with elfread.c
15216 	I've tested this with a simple test binary compiled with the mingw
15394 	target), and you step over thread exit with scheduler-locking on, this
15458 	for syscalls with up to 3 arguments, and, if the syscall doesn't
15488 	GDB getting confused.  For example, with a following patch that
15581 	If scheduler-locking is in effect, e.g., with "set scheduler-locking
15590 	I think that letting the new threads run with scheduler-locking
15653 	In more detail, here's what happens with that testcase:
15681 	     threads with pending events:
15721 	looks like with displaced-stepping, on x86-64 Linux, where we have two
15765 	When trying the same but with in-line step over (displaced-stepping
15809 	displaced or in-line step over exits.  We can do that with the new
15819 	 - the exiting thread was doing an in-line step-over with an all-stop
15821 	 - the exiting thread was doing an in-line step-over with a non-stop
15823 	 - the exiting thread was doing a displaced step-over with a non-stop
15845 	because TARGET_WAITKIND_THREAD_EXITED can also end up with the event
15876 	When stepping over a breakpoint with displaced stepping, GDB needs to
15879 	result in deadlock, with other threads waiting for their turn to
15962 	it, with QThreadEvents, or with the GDB_THREAD_OPTION_EXIT
15995 	with all other threads of the process, there's nothing special that
16005 	to GDB, when GDB has requested them with the GDB_THREAD_OPTION_CLONE
16057 	In order to be able to do that with GDBserver, we need a new remote
16066 	processed left to right, with the options field being a number
16176 	   running or stopped, but as with the continue case above, the new
16187 	- For both all-stop and non-stop modes, with in-line stepping:
16214 	- For both all-stop and non-stop modes, with displaced stepping:
16229 	There is one problem with the displaced stepping scenario above:
16259 	associated with the clone parent.  TARGET_WAITKIND_THREAD_CREATED
16268 	that we end up with a new thread in the same process, instead of a new
16275 	after a fork/vfork event is thus reused for THREAD_CLONE, with some
16289 	displaced_step_in_progress_thread becomes unused with this patch, but
16291 	readding it back, this patch marks it with attribute unused, and the
16293 	the function is static, and with no callers, the compiler would warn,
16294 	(error with -Werror), breaking the build.
16297 	exercises stepping over a clone syscall, with displaced stepping vs
16299 	over clone syscalls with gdb.base/step-over-syscall.exp, but this test
16316 	was passing cleanly, but still, we'd end up with four new unexpected
16388 		Since Linux 3.0, the former thread ID can be retrieved with
16416 	The crash with gdb.threads/step-over-exec.exp is not observable on
16432 	on Linux native, which also exposes the stale LWP problem with an
16464 	When building gdb with -O2, we run into:
16735 	The tests are not compatible with ilp32 abi: the GNU property
16779 	When a relocation requires a stub with a name that already exists, the
16785 	The BTI stub can end up with the same stub group id and thus the same
16793 	same stub area, a better solution is to emit a single stub with a
16801 	symbol of the stub so a BTI stub may end up with *_veneer instead of
16837 	[-Werror,-Wconstant-logical-operand] check.  Together with this fix we
16842 	implementation (with which only the former was of concern in the cited
16869 	x86: do away with is_evex_encoding()
16872 	far was done at runtime: Deal with templates indicating EVEX-encoding by
16880 	Right now the opcode table has entries with ISA restrictions of the form
16884 	these features required". Split the field, with the original one
16910 	omit explicit "&x64" from any insn templates dealing with 64-bit-mode-
16912 	templates we already have, this will also help with what is going to be
16953 	with no regressions.
16965 	Once the register mapping was fixed, an underlying issue with the unwinding
17050 	The patch has been tested on Power 8 LE/BE, Power 9 LE/BE, Power 10 with
17078 	can become out of sync with the actual thread count of the inferior,
17079 	and will disagree with the number of threads reported by 'info
17183 	extern, with a declaration in completer.h.
17192 	gdb: error if /r and /b are used with disassemble command
17204 	We have a similar situation with the /m and /s flags, but here, if the
17266 		* po/bfd.pot: Regenerate.
17281 		* po/bfd.pot: Regenerate.
17295 		* po/bfd.pot: Regenerate.
17304 	Implement, together with the necessary tests, the following new LSE128
17337 	Enable the `+lse128' feature modifier which, together with new
17414 	Add Binutils support for system registers associated with the
17447 	When compiling gdb with -fsanitize=address on ARM, I get a crash in test
17448 	gdb.arch/arm-disp-step.exp, reproduced easily with:
17472 	0x549 is the address of the test_call_subr label, 0x548, with the thumb
17473 	bit enabled.  Before doing some math with the address, I think we need
17479 	would be a change with a broad impact, so for now just fix the issue
17501 	with "ISA v3 needed" notes. Eventually other tests ought to be
17623 		* riscv-dis.c (print_insn_args): Disassemble information with
17699 …an address with all f's in hexadecimal are assigned. Hence the testcase fails with many failures s…
17805 	gdbsupport: mark array_view::slice with [[nodiscard]]
17815 	using it, it's useless.  Mark the slice methods with [[nodiscard]]
17856 	First of all the respective original changes didn't deal with just 0
17859 	were accepted, while valid suffixes with U following the L(s) weren't.
18069 	with:
18080 	The problem is the filename_for_id which is the source file prefixed with the
18236 	gas: bpf: new test for MOV with C-like numbers ll suffix
18243 	to avoid ambiguity with the assembler's support for C-like numerical
18295 	Fix "finish" with range types on ARM
18306 	Fix calls with small integers on ARM
18307 	On big-endian ARM, an inferior call with a small integer will pass the
18396 	The first GCC release which with full C++17 support is GCC-9[2],
18400 	A discussions with many distros showed that a C++17-able compiler is
18643 	reported to the user with a 'Can't detach process' error.  As the test
18726 	a FAIL in gdb.python/py-watchpoint.exp. Since this is nothing wrong with
18733 	gdb/testsuite: fix running gdb.python/py-explore-cc with clang
18751 	This bug was introduced with this commit:
18766 	std::string, which copies the buffer contents, leaving ownership with
19010 	x86: don't use operand size override with NOP in 16-bit code
19058 	-value in two words (with an imm instruction).No relocation is
19061 	+     two words (with an imm instruction).  No relocation is done here -
19086 		* reloc.c: Remove uses of COMMENT and edit ENUMDOC paragraphs.
19200 	yielding a CTF dictionary with invalid content (readable, but meaningless):
19204 	given parent can be associated with many different children).
19241 	value in two words (with an imm instruction).
19250 	with gcc's check_GNU_style.{sh,py}.
19337 	Remove this function, replace it with deleting the so_list in callers.
19364 	Replace the hand-made linked list implementation with intrusive_list,
19454 	 - Replace rocm_solib_copy_list with so_list_from_rocm_sos.
19475 	so_list copyable, with all the complexity that entails, just to satisfy
19490 	   order to return them to the core) with so_list_from_svr4_sos, which
19537 	gdb: allocate so_list with new, deallocate with delete
19580 	gdb: make interps_notify work with references
19583 	that interps_notify did not work with reference parameters.
19586 	reference (&&).  Change the type of the method to be auto-deduced as an
19599 …s-gdb/gdb/interps.c:378:18: note:   inconsistent parameter pack deduction with ‘gdb_signal’ and ‘g…
19693 	libctf: check for problems with error returns
19695 	(with ssize_t longer than unsigned long) use PE, and we do not have support
19705 	nodiscard depending on the configuration[1] (when compiled with C++17).
19776 	which built with the old -misa-spec.
19886 	To consistent with LoongArch lld, RELASZ chang to only the size of .rela.dyn.
19942 	This patch fixes the problem, partly with a small patch in varref.py,
19969 …tecture option is given exactly two dashes, so that it does not become confused with the -a option.
19975 	with the same frame would yield different variableReference values in
19987 	When using glibc debuginfo generated with gas 2.39, we run into PR gas/29517:
20000 	and likewise with glibc debuginfo generated with gas 2.40.
20012 	with gas 2.40.
20066 	Now, with the assertion in place, this is running into issues.
20112 	gdb: replace architecture_changed with new_architecture observer
20113 	This commit replaces the architecture_changed observer with a
20118 	with the architecture.
20124 	Python unwinder registered with them.
20163 	support for LP64E (LP64 with reduced GPRs).
20180 	This commit removes a restriction that prevents making base ISA with
20181 	reduced GPRs with XLEN > 32.
20329 	Simon pointed out that the new file-then-restart.exp test fails with
20343 	In GDB we have a problem with the BFD cache.
20404 	then, should the sysconf call fail, we'd end up with max becoming a
20411 	There should be no user visible change with this commit.
20432 	worked fine for hosts with a 32 bit wide long and failed miserably for hosts
20433 	with a 64 bit wide long.
20449 		* src/Experiment.cc: Replace er_archive with gp-archive.
20470 	The root cause is related with a struct containing floating-point
20609 	belonging to this inferior.  Call registers_changed_ptid instead, with
20676 	Guard against fuzzed files where .plt size isn't commensurate with
20687 	This fixes multiple places in read_and_display_attr_value dealing with
20774 	gdb.fortran/nested-funcs-2-exp when running the test-case with target board
20775 	cc-with-gdb-index. ]
20793 	The main use case for this patch is in improving startup times when dealing with
20800 	In my testing (a binary with about 1.8GB worth of DWARF data) this change brings
20803 	When testing the patch with target board cc-with-gdb-index, test-case
20807 	Tested on x86_64-linux, with target board unix and cc-with-gdb-index.
20853 	When testing with READ1 set this assumption was failing.
20855 	Fix this by extending the offending patterns with a trailing '\r\n'.
20923 	On x86_64-linux, with test-case gdb.arch/i386-signal.exp I run into:
20929 	compiler exited with status 1
20939 	This is with gas 2.41, it compiles without problems with gas 2.40.  Some more
20954 	The test-case passes with target board unix/-m32.
20959 	Tested on x86_64-linux, with target boards:
21002 	breakpoint, GDB is out of sync with the inferior.  This causes the tests
21121 	when run with the native-extended-gdbserver board contained several
21132 	After this commit the gdb.base/args.exp is 100% passing with the
21210 	If we compare this to a packet with only a single argument and no
21222 	We break out of this loop when the character we start with (in that
21224 	empty argument case, we abort the loop before doing anything with the
21229 	was empty, with this change we now notice the trailing empty
21281 	used with the "set args" command is just to show GDB that the single
21291 	      Share fork_inferior et al with gdbserver
21296 	extended-remote target as with the native target.
21299 	with newline handling which I'll address in a later commit.
21324 	gdb/configure.ac: Add option --with-additional-debug-dirs
21330 	Configuring GDB with '--prefix=$PREFIX' sets the GDB 'debug-file-directory'
21336 	with the '-nx' option.
21338 	There's the configure option '--with-separate-debug-dir' to set the default
21364 	but with gcc-11:
21441 	The free_objfile observable is never called with a nullptr objfile.
21481 	gdb: add program_space parameters to some auto-load functions
21489 	gdb: use objfile->pspace in auto-load.c
21529 	test (gdb.python/py-progspace-events.exp) was failing when run with
21530 	the native-extended-gdbserver board.  This test was added with this
21544 	with this commit:
21555 	This bug is interesting because it exposes a number of issues with
21615 	does GDB get into a position where it tries to interact with the
21666 	can't rely on the current inferior having any relationship with the
21735 	call completely, and just rely on the reference count to auto-delete
21756 	now passes when run with the native-extended-remote board.
21793 	Fix: addr2line testsuite fails when targeting PowerPC 64 big-endian with ELFv2 ABI
21795 …* testsuite/binutils-all/addr2line.exp: Do not use PowerPC specific options when working with a MU…
21803 	  * testsuite/ld-shared/shared.exp: Add XFAILs for tests that fail with the MUSL library.
21813 …* testsuite/ld-i386/i386.exp: Skip the pr22001 test with TEXTREL relocations enabled on configurat…
21864 	I think the problem with the previous thread related to the changes in
21926 	fails; there's no file with that name (usually).  As a consequence of
21931 	however, BFD just fills the 'struct stat' buffer with zeros (except
21963 	This started with me running into this comment in symfile.c:
21969 	In this particular case I think I disagree with the comment; I think
21992 	takes a filename, which is printed with styling, and an errno, which
22126 	stack or a segment with all three read, write and execute permissions.
22186 	Since most of the code used by gdbserver for SME2 is shared with gdb, this
22274 	for most targets, it doesn't work correctly for AArch64 with SVE or SME
22367 	created for set A, but it is really dealing with a frame that was using set
22370 	This is problematic, specially with SME, because now we have a different
22385 	context, and with which we can make various decisions.
22447 	It is also unlikely we will find a process starting up with SVL set to 256.
22478 	with a nullptr element at the end to signal its last element.
22494 	The SME (Scalable Matrix Extension) [1] exposes a new matrix register ZA with
22535 	out in a way that allocates the buffer with the size of the register, but
22619 	something a bit more meaningful that can be shared with the SME code.
22713 	One concrete example of where this is useful is with the
22738 	For architectures with dynamic architectures (e.g. AArch64 with
22751 	In many cases (though NOT all) targets with dynamic architectures
22756 	Additional work will be needed in order to support corefiles with
22769 	regressions with `mips64-linux-gnuabi64', `mips64el-linux-gnuabi64',
22783 …ation. (read_and_display_attr_value): Replace uses of fetch_indexed_value with fetch_indexed_offse…
22791 	gdb/python: reformat file with black
22792 	Reformat a Python file with black after this commit:
22799 	There should be no functional change with this commit.
22845 	This setting is enabled by default if gdb is built with debuginfod
22848 	Also update debuginfod command help text and gdb.texinfo with
22858 	debuginfod servers for an individual ELF/DWARF section associated with
22866 	When running test-case gdb.ada/import.exp with gcc 7, most test fail:
22878 	When running with gcc 8 or 9, only 2 tests fail:
22884 	The test-case passes fully with gcc 10, 11, 12 and 13.
22889 	The two FAILs with gcc 8 and 9 seem to be due to problems in debug info.  Add
22911 	I don't see the same problem with gcc 7.5.0, because the exec doesn't contain
22913 	linked in.  Adter adding "with Ada.Strings.Maps; use Ada.Strings.Maps;" to
22914 	gdb.ada/widewide/foo.adb I run into the same problem with gcc 7.5.0.
22960 	should change that -- and so, we end up with the consequence that we
22972 	Finally, when testing, I did hit a slightly weird issue with some of
23000 	It turns out that this has nothing to do with my changes, this is just
23014 	do with this change, I just mention it because I ended up needing to
23118 	Add an x86-64 linker option, -z mark-plt, to mark PLT entries with
23199 	    with
23225 	Also, while testing with CC_FOR_TARGET=clang, I found that
23230 	My testing for this v2 patch shows the same results as with v1,
23231 	but I've done additional testing with CC_FOR_TARGET=clang as
23285 	 Program terminated with signal SIGSEGV, Segmentation fault.
23289 	I tried to reproduce the segfault with exec next-fork-other-thread-fork, using
23534 	Additionally, with this change, it should be possible to update the
23552 	isn't directly associated with a change of the executable file, and so
23573 	This commit continues with the task started in the previous commit,
23584 	observable and replaced it with a new_obfile observer instead, and
23595 	As with the previous commit, I think we can safely replace the use of
23596 	the executable_changed observable with a use of the new_obfile
23597 	observable.  All the tests still pass, and with some locally placed
23676 	Progspace.objfiles, and then search for the objfile with a name that
23707 	all-registers"), saves a core with the "gcore" command, loads the core,
23715 	One strange thing with this machine is that the bitset of state
23742 	with this condition:
23791 	When running test-case gdb.base/unwind-on-each-insn-amd64-2.exp with target
23796 	  recompile with -fPIE
23835 	only read is merely to determine whether to write it with another value).
23845 	starts with (almost) all functionality enabled, while cpu_arch_isa_flags
23865 	[1] - with system GDB.  Upstream GDB is missing a couple patches
23880 	 [Thread 3732.0x265c exited with code 1]
23881 	 [Thread 3732.0x2834 exited with code 1]
23882 	 [Thread 3732.0x2690 exited with code 1]
23884 	 Program terminated with signal SIGHUP, Hangup.
23891 	were not defined.  I.e., ignore ENOTSUP errors, and proceed with
23906 	 [Thread 8732.0x28f8 exited with code 1]
23907 	 [Thread 8732.0xb50 exited with code 1]
23908 	 [Thread 8732.0x17f8 exited with code 1]
23910 	 Program terminated with signal SIGHUP, Hangup.
23939 	gdb.threads/pthreads.c is declaring functions with old K&R style.
23958 	Following the folding of some generic AVX/AVX2 templates with their
23963 	Following the folding of some generic AVX/AVX2 templates with their
23977 	- the EVEX form being AVX512F (with or without AVX512VL), not any of its
24014 	gdb: Fix an ODR warning with byacc with GDB_YY_REMAP
24015 	With byacc, we get an ODR warning with YYSTACKDATA between ada-exp.c.tmp
24039 	with:
24064 	[gdb/testsuite] Fix gdb.ada/mi_task_arg.exp with newer gcc
24081 	On openSUSE Leap 15.4 with gcc 7.5.0 I get instead:
24095 	the compiler, so I don't see a problem with gdb here.
24151 	because there's no process with pid 1 and cmd init or systemd.
24188 	(1) Turn the ARM_FEATURE_FOO macros into an enum, with the enum
24238 	- openSUSE Leap 15.4 with python 3.6, and
24239 	- openSUSE Tumbleweed with python 3.11.5.
24245 	fbsd-nat: Fix build failure with GCC 12
24246 	A user pointed out that the build failed on FreeBSD/amd64 with my last
24316 	Revert "arc: Update ARC's Gnu Assembler backend with ARCv3 ISA."
24341 	with ARCv3 32bit machines.
24343 	with ARCv3 64bit machines.
24345 	When configuring with `--enable-targets=all` some patterns are defined
24350 	RISC-V: Protect .got with relro
24351 	Move .got before .data so that it can be protected with -zrelro.  Also
24424 	        (fpnames): New strings with fp-regs name.
24439 	arc: Update ARC's Gnu Assembler backend with ARCv3 ISA.
24487 		(arc_show_cpu_list): Update with ARC64 cpus.
24551 	32-bit ISA.  The new 32-bit ISA is not compatible with the old
24667 	fbsd-nat: Pacify gcc with no functional changes
24706 	delegate code preserves this keyword -- but, with C++, it does not
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").
24803 	resolving the breakpoint source information. This is consistent with
24844 	I use the mouse with my terminal to select and copy text. In gdb, I use
24848 	When gdb is compiled with ncurses mouse support, gdb's TUI mode
24878 	3. Click and drag text with the mouse. Observe no selection.
24880 	5. Click and drag text with the mouse. Observe that selection works now.
24882 	7. Click and drag text with the mouse. Observe no selection.
24904 	(gdb) file struct-with-sig-2^M
24905 	Reading symbols from struct-with-sig-2...^M
24920 	The test-case is a modified copy from gdb.dwarf2/struct-with-sig.exp, so it
25027 	This replaces some casts to various kinds of catchpoint with
25035 	This replaces some casts to 'code_breakpoint *' with
25043 	This replaces some casts to 'tracepoint *' with checked_static_cast.
25052 	This replaces some casts to 'watchpoint *' with checked_static_cast.
25168 	    The AMD GPU can overlap the execution of memory instructions with other
25170 	    or hardware data watchpoint hit with a program counter beyond the
25224 	command.  Add the inferior_cloned observable to help with this.
25231 	Fix build failure with GCC 4.8
25232 	A user pointed out that the build failed with GCC 4.8.  The problem
25255 	Replaced the amdgpu target call to delete_thread with a call to
25277 	with an old version of Bison (2.3, the version available on macOS).
25356 	with the purpose of ensuring that GDB doesn't hold the BFDs open
25361 	with the result that GDB would continue to hold open some BFD objects
25399 	x86: don't play with cpu_arch_flags.cpu{,no}64
25456 …$ gdb -q -nx -iex 'set auto-load no' -iex 'set debuginfod enabled off' -ex file ./libgraph_tool_in…
25495 	Using a gdb built with this commit, I now see this behavior instead:
25497 …$ gdb -q -nx -iex 'set auto-load no' -iex 'set debuginfod enabled off' -ex file ./libgraph_tool_in…
25554 	of the problem, and with this patch in place there are no longer
25565 	I've been running the test-suite on an i686-linux laptop with 1GB of memory,
25572 	The test-case is compiled with -DCRASH_GDB=2097152, so this:
25576 	with sizeof (int) == 4 represents two arrays of 8MB each.
25608 	The subsequent 8MBs are consistent with the values being saved into the value
25647 	   auto iter = std::find (all_values.begin (), all_values.end (), mark);
25685 	I managed to apply the compilation loop for the Ada variant as well, but with
25716 	"dst" to "src", thus bringing things in line with Exy.
25727 	While for most insns we can suppress their use with too wide operands
25822 	I see the following warning when building GDB on FreeBSD/amd64 with
25891 	This makes it a little easier to use with standard containers.
25921 	commit to start the test from running to line with tag "First Breakpoint"
25937 	Also merge btrace_tinfo_bts with btrace_tinfo_pt and inline into
25990 	I toyed with the idea of changing the test program to make it so the CPU
26023 	second as is correct for other cases with split frags.  This would
26033 	The auto-builders pointed out that I neglected to run 'black' after a
26053 	Intel or AMD manuals.  Similarly, I can imaging someone familiar with
26096 	I ran test-case gdb.dwarf2/dwzbuildid.exp with target board cc-with-gdb-index,
26196 	reference to the inferior's output, and replacing it with '.*', which
26205 	x86: restrict prefix use with .insn VEX/XOP/EVEX
26232 	The modified test in function-calls.exp actually passes with ifort and
26234 	test was introduced it was only tested with gfortran (actually the
26235 	whole patch was written with gfortran and the GNU Fortran argument
26259 	set at the first program statement.  This works with both compiler
26276 	with ifort (2021.6.0) these statements do not actually create any
26285 	compiled with gfortran (13.0.0, -O0 -g).  The linetable as emitted by
26324 	This removes a few FAILs in the testsuite when ran with ifort.
26351 	e array the actual output in the test (with gfortran/ifx) is
26388 	kvx: Add a testcase for bundles with KVXMAXBUNDLEWORDS syllables
26402 	bundle_words[word_count-1] with the parallel bit clear and all other
26420 	This bug points out that if one uses -var-set-visualizer with "None"
26476 	The easiest way to see what's going wrong is with readelf.  We have in section
26508 	When running test-case gdb.ada/local-enum.exp with target board debug-types, I
26516 	The array V1 is of type A1 which is an array with index type E1, containing
26558 	When running test-case gdb.ada/arr_acc_idx_w_gap.exp with target board
26559 	cc-with-dwz, I run into:
26580 	the extra test passes with target board cc-with-dwz, but fails with target
26617 	Following the commit f818c32ba459 ("gdb/mi: fix ^running record with
26660 	The vendor operands should be named starting with `X', and preferably the
26706 	the notes obstack twice, with the second call to obstack_free
26768 	When running test-case gdb.python/py-symbol.exp with target board
26769 	cc-with-dwz-m, we run into:
26776 	while with target board unix we have instead:
26806 	When running test-case gdb.base/setshow.exp with target board cc-with-dwz I
26829 	Tested on x86_64-linux, target boards unix, cc-with-dwz and cc-with-dwz-m.
26844 	libsframe requires libctf/swap.h, with no dependencies on built or
26860 	Tested on aarch64 and x86_64 with and without --enable-shared and --target=<>.
26875 	extra output that ends up mixed with GDB's own output.  For example,
26900 	This patch fixes some testcases that formerly had patterns with
26911 	may print as "0x0" or as an address with a symbol name following.
27017 	print_spaces was called with a negative number, which
27051 	Avoid crash with Ada and -fdata-sections
27069 	There's no need to have almost identical code twice. Do away with
27103 	Note that, because mcyclecfg and minstretcfg CSRs conflict with the
27144 		incompatible with the privileged specification version 1.9.1.
27158 	> The hypervisor extension depends on an "I" base integer ISA with 32 x
27161 	Also in the latest draft, it also prohibits RV64E with the 'H' extension.
27183 	very to understand, so this patch replaces the numbers with the
27203 	When running test-case gdb.base/add-symbol-file-attach.exp with target board
27272 	On a machine with AVX512 support (AMD EPYC 9634), I see these failures:
27325 	$build nor $target, resulting in the compilers not being linked with
27326 	-rdynamic and plugins not being usable with such a compiler.  In fact
27332 	with -rdynamic as expected.  Also bootstrapped with no regressions for
27360 	The name we use internally isn't in line with the SDM, and also isn't in
27361 	line with CpuVPCLMULQDQ. Add the missing suffix, but of course leave
27369 	Commit 916fae91358d ("Add Size64 to movq/vmovq with Reg64 operand" was
27409 	Replace two uses of alloca with std::string.
27435 	1. Generic linker targets don't comply with all orhpan section merging
27457 	Replace with a new equivalent "is_packed" method on struct field.
27465 	Replace with type::field + field::bitsize.
27473 	Replace with field::bitsize.
27490 	Replace with type::field + field::is_artificial.
27498 	Replace uses with field::is_artificial.
27599 	assumes that it won't be called with the OBF_MAINLINE flag set for
27701 	This patch merges the DW_TAG_typedef case in new_symbol with some
27720 	know why.  Anyway, all this means is that, with this reversion,
27733 	[gdb/contrib] Require minimal dwz version in cc-with-tweaks.sh
27734 	I usually run target boards cc-with-dwz and cc-with-dwz-m using a dwz build
27747 	Fix this by minimally requiring dwz version 0.13 in cc-with-tweaks.sh, such
27750 	gdb compile failed, cc-with-tweaks.sh: dwz version 0.12 detected, version \
27754 	Tested on x86_64-linux, verified with shellcheck.
27803 		(s_stab_generic): Replace stab_secname_obstack_end param with
27831 	[gdb/symtab] Replace TYPE_ALLOC with TYPE_ZALLOC where required
27833 	- replacing with TYPE_ZALLOC, or
27842 	[gdb/symtab] Replace TYPE_ALLOC + B_CLRALL with TYPE_ZALLOC
27845 	Replace these with TYPE_ZALLOC.
27853 	[gdb/symtab] Replace TYPE_ALLOC + memset with TYPE_ZALLOC
27856 	Replace this with TYPE_ZALLOC.
27904 	 /* Allocate the fields array of this type, with NFIELDS elements.  If INIT,
27940 	When running test-case gdb.dwarf2/per-bfd-sharing.exp with target board stabs,
27961 	Update ARC's elfarcv2 script template with:
27983 	elf: Don't merge sections with different SHF_LINK_ORDER
27987 		* ldelf.c (elf_orphan_compatible): Don't merge sections with
28000 	on LLVM IR object with NULL elf_tdata.
28037 	[gdb/testsuite] Fix gdb.dwarf2/nullptr_t.exp with cc-with-dwz-m
28038 	When running test-case gdb.dwarf2/nullptr_t.exp with target board
28039 	cc-with-dwz-m, I run into:
28050 	Tested on x86_64-linux, with make-check-all.sh.
28055 	Replace the manual fill of the vector with the appropriate std::vector
28105 	Note that this commit alone will not make XVentanaCondOps extension with
28127 	Re: readelf/objdump: Handle DWARF info with mixed types of range section
28161 	Fix this by replacing nullptr with (void *)0.
28172 	patch replaces one with a better name, and entirely removes the other.
28229 	alloca with a std::vector in array_operation::evaluate.  This function
28265 	When running test-case gdb.arch/i386-avx512.exp with gcc 4.8.4, I run into:
28278 	When running test-case gdb.linespec/cpls-abi-tag.exp with gcc 4.8.4, we run
28294 	[gdb/testsuite] Handle some test-cases with older compiler
28295 	When running test-case gdb.mi/print-simple-values.exp with gcc 4.8.4, I run
28299 	Fix this by compiling with -std=c++11.
28343 	getpkt, with a suitable default, and removes the wrappers.
28374 	When running test-case gdb.reverse/getrandom.exp on a system with eglibc 2.19,
28441 	  registers with a single variable.  Make use of this to merge
28465 	Replace the extended state area fields of i387_xsave with methods which
28609 	with a fixed layout.  The final region (extended region) contains zero
28656 	Building gdb with gcc 7.5.0 and -flto -O2 -flto-partition=one generates a
28701 		Delete unnecessary sanity check with unsigned _n_offset.
28702 		Return with failure if debug section can't be read, to avoid
28710 	case with a C_FILE sym using multiple auxents for a long file name
28716 		(fill_comdat_hash): Only look at symbols with one auxent.
28721 	When running test-case gdb.cp/subtypes.exp with gcc 4.8.4, we run into:
28750 	[gdb/testsuite] Handle gdb.cp/*.exp with older compiler
28751 	When running test-cases gdb.cp/*.exp with gcc 4.8.4, I run into compilation
28755 	Fix this by compiling with -std=c++11.
28770 	with the corresponding `mips64*-*-linux*' targets.
28780 	or mips*el* may cause some problem with other components of
28831 	Entries added to the hash table with bfd_malloc ought to be freed when
28895 	After the upstream changes, either Guile 2 or Guile 3 will work, with
28907 	The author of 'mold' pointed out that with a certain shared library,
28911 	segment and ended with a call to 'abort'.
28967 	dependency files made while generating e*.c files, replacing them with
28973 		files with one pattern rule.
28991 	This patch addresses an issue with malformed/fuzzed debug information that
28992 	was recently reported in gdb/30639. That bug specifically deals with
29071 	years ago with GCC 8.
29119 	alone: The harness fiddling with section names there didn't help before
29133 	with adding or removing some. Note that documenting the interaction
29134 	with '?' as undefined is a precautionary measure.
29156 	buffer contents are needed, so replace with free, bfd_malloc.  There
29179 		  // need to mess with the relaxation machinery checkpointing.
29220 	the architecture associated with the code object to open is fully
29247 	This fixes the build when building with -std=c++20.
29279 	testing with clang-15 from around 150 to 2, and correctly identifies
29292 	at dealing with asm statements that change the rbp register. It can be
29315 	gdb/testsuite: fix testing gdb.reverse/step-reverse.exp with clang
29319 	if there is only one instruction associated with that line, which is how
29322 	to get seriously out of sync with the test expectations, and result in 13
29323 	spurious failures. The same issue occurs with gdb.reverse/step-precsave.exp.
29342 	be slightly changed to work with empty "current locations", so that we
29354 	gdb/testsuite: Fix many errors in gdb.reverse with clang
29369 		* kvx-dis.c (print_insn_kvx): Init dec with memset.
29395 	  ./ld/ld-new: warning: load.S.x has a LOAD segment with RWX permissions
29399 	issues with the move.  Namely:
29401 	  - fpu tests: were incorrectly using l.ori with ha(anchor) which now
29585 	readelf/objdump: Handle DWARF info with mixed types of range section.
29622 	problem with GDB after the above commits.  Neither of the above
29624 	when an inferior function call fails with a signal GDB will unwind the
29820 	doesn't help with this case, so that test is not changed.
29827 	differences between targets, like e.g. with the remote target, we
29831 	with gdbserver, letting it run for a bit, and then pressing Ctrl-C, we
29882 	 [Thread ... exited with code <exit_code>]
29932 	with silent true or false, because:
30003 	If GDB is being compiled with a C++14 compiler then the new
30005 	checked with gcc, and at -O1 and above gdb::make_unique will be
30009 	to go through the code and replace gdb::make_unique with
30029 	limited support was added in lib/mi-support.exp to help with testing
30147 	with bfd_vma, and removes _bfd_kvx_elf_resolve_relocation, a
30210 	When building gdb with -flto -O2, I run into:
30216 	opcodes/or1k-desc.h:624:14: note: an enum with different value name is \
30224 	opcodes/or1k-desc.h:433:14: note: an enum with different value name is \
30275 	everything associated with the A-profile cores end in `A' and likewise
30292 	Finally, this is more in line with conventions within GCC and adds consistency
30489 	Add required code to support core file dumps with NT_ARM_ZA and NT_ARM_SSVE
30499 	This bug was found by oss-fuzz with the trigger being an old bug in
30545 	I believe this snuck in by error with the recent cgen-related changes.
30555 	Tested with the following tools from a recent binutils build in
30676 	do with --enable-maintainer-mode, and added --enable-cgen-maint
30822 	attempting to use the inferior keyword with a watchpoint will give an
30826 	  Cannot use 'inferior' keyword with watchpoints
30853 	When building gdb with -O2 -flto on openSUSE Tumbleweed (using bison 3.8.2) I
30858 	c-exp.c.tmp:398: note: an enum with different value name is defined in \
30885 	of files and regen with our standard automake/autoconf.
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.
30914 	When building gdb with -std=c++20, I run into:
30952 	When building gdb with -std=c++20, I run into:
30969 	When building gdb with -std=c++20 I run into:
30973 	10713 |   auto do_op = [=] (LONGEST x, LONGEST y)
30987 	When building gdb with -std=c++20, I run into:
31004 	When building gdb with clang 15 and -std=c++20, I run into:
31021 	When building gdb with clang 15 and -std=c++20, I run into:
31075 	  Relaxing to jump instructions with wider range is only performed
31089 		(md_assemble): Do not relax instructions with
31142 	The same test-case with -readnow makes gdb hang, so also fix this in
31174 	This patch adds a missing bounds check.  Tested with the self-tests in
31198 	fully qualified if some global variable with the same base name
31248 	run with the native-gdbserver or native-extended-gdbserver boards:
31260 	with target-non-stop turned off, then we see the same failures on the
31288 	with inferior 2, the newly exited vfork-child, selected.
31307 	with the commit, but the change was harmless.
31312 	  1. GDB calls proceed with the vfork-parent selected, as schedule
31364 	  1. GDB calls proceed with the vfork-parent selected, as schedule
31406 	with, these were:
31436 	commit b1e0126ec56e, and with this new fix is:
31438 	  1. GDB calls proceed with the vfork-parent selected, but,
31574 	This commit replaces all such occurrences of 18446744073709551615 with
31580 		18446744073709551615 with generic regular expression.
31644 		including auto-compression without C prefix and explicit C prefix.
31696 	When building gdb with -O2 -flto I run into:
31706 	Tested on x86_64-linux.  Also tested with byacc rather than bison on
31724 	FreeBSD's ptrace fails requests with EBUSY against a running process.
31725 	Report that the thread is alive instead of dead if ptrace fails with
31737 	fbsd-nat: Fix several issues with detaching.
31759 	fbsd-nat: Fix resuming and waiting with multiple processes.
31825 	I noticed that the call to alloca in osabi.c can be replaced with a
31834 	When building gdb with -O2 -flto I run into:
31863 	When build gdb with -O2 -flto I run into:
31889 	When building gdb with -O2 -flto, I run into:
31895 	gdb/python/py-param.c:33:6: note: an enum with different value name is \
31962 	the symbols for the file with code at that address".
31973 	ld: Build libpr23169a.so with -z lazy
31974 	pr23169b test only works with lazy binding.  To work with linker which
31975 	disables lazy binding by default, build pr23169b binaries with -z lazy.
31978 		* ld-ifunc/ifunc.exp: Build pr23169b binaries with -z lazy.
32022 	When running test-case gdb.python/py-symbol.exp with target board
32023 	cc-with-gdb-index, we run into:
32039 	This passes with gdb-12-branch, and fails with gdb-13-branch.
32060 	Tested on x86_64-linux, with target boards unix and cc-with-gdb-index.
32131 	the executable associated with that test would die due to a SIGTRAP
32167 …exec-other-thread.exp: fork_func=fork: target-non-stop=auto: non-stop=off: displaced-stepping=auto…
32168 …FAIL: gdb.threads/next-fork-exec-other-thread.exp: fork_func=fork: target-non-stop=auto: non-stop=…
32169 …FAIL: gdb.threads/next-fork-exec-other-thread.exp: fork_func=fork: target-non-stop=auto: non-stop=…
32170 …xp: fork_func=fork: target-non-stop=off: non-stop=off: displaced-stepping=auto: i=3: next to other…
32173 …xec-other-thread.exp: fork_func=vfork: target-non-stop=auto: non-stop=off: displaced-stepping=auto…
32174 …FAIL: gdb.threads/next-fork-exec-other-thread.exp: fork_func=vfork: target-non-stop=auto: non-stop…
32175 …FAIL: gdb.threads/next-fork-exec-other-thread.exp: fork_func=vfork: target-non-stop=auto: non-stop…
32176 …xp: fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=auto: i=47: next to othe…
32178 …p: fork_func=vfork: target-non-stop=off: non-stop=off: displaced-stepping=auto: i=1: next to break…
32195 …xp: fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=auto: i=143: next to oth…
32204 	problem.  They are also racy - I've seen runs with no failures or only
32206 	with the loop count in next-fork-exec-other-thread.exp set to 200.
32212 	reliably reproduce the failures that Zhiyong reported (in which, with
32213 	the proper settings, core files are created).  But, with the loop
32223 	kernel+userland) with --target_board=native-gdbserver.  Additionally,
32269 	"--enable-languages=go" (and not using make with multiple threads).
32285 	since inlining decisions with -fauto-profile are different from
32302 	cc1, cc1plus, and lto  built during STAGEautoprofile need to be built with
32317 	When we collect just user events for autofdo with lbr we get some events where branch
32320 	it can't map at least 95% of events. We sometimes get below this threshold with just
32359 		(STAGE1_CONFIGURE_FLAGS): Add --with-libphobos-druntime-only if
32404 	paths that were specified with the -L option from the embedded path.
32413 	shared libs on VxWorks ports configured with --enable-shared,
32415 	code model !large - currently not compatible with -fPIC).
32421 	to begin with.
32429 	toplevel: reconcile few divergences with GCC
32521 	to be built with that enabled (since it makes a significant
32544 	and condition variables with the mcfgthread library.
32554 	Fix PR bootstrap/102389: --with-build-config=bootstrap-lto is broken
32556 	with LTO to work so we need to pass down NM just like we do for ranlib
32565 	32-bit PA-RISC with HP-UX: remove deprecated ports
32586 		Add entry for language=m2 with gcc-check-target=check-m2
32698 	configure: When host-shared, pass --with-pic to in-tree lib configs.
32706 		'--with-pic' when building 'host_shared'.
32748 		* dwarf2.h: Update with additional languages from dwarf
32783 	the strings "new_type" and "new_num_children" are printed along with their
32862 	It's not documented anyway, and having it makes no sense anymore with
32871 	compact representation: Only identifiers which need to combine with
32873 	into an enum, with a new helper added to transform the table entries
32913 		Fix bitrotted code to look for first section with non-zero filepos.
33017 	  for (const auto &entry : m_deferred_entries)
33137 	Patch tested on Power10 with no new regressions.
33143 	Change py-thread-exited.exp to work with gdbserver
33185 	[gdb/testsuite] Fix gdb.dwarf2/enqueued-cu-base-addr.exp with cc-with-gnu-debuglink
33186 	When running test-case gdb.dwarf2/enqueued-cu-base-addr.exp with target board
33187 	cc-with-gnu-debuglink, I run into:
33197 	Fix this by replacing "-objfile enqueued-cu-base-addr" with "-source cu2".
33204 	I ran test-case gdb.dwarf2/enqueued-cu-base-addr.exp with target board
33205 	cc-with-debug-names, and ran into:
33216 	Tested on x86_64-linux, with target boards unix and cc-with-debug-names.
33221 	When running test-case gdb.dwarf2/pr13961.exp with target-board
33222 	cc-with-debug-names, I run into:
33241 	Tested on x86_64-linux, using target boards unix and cc-with-debug-names.
33396 	[gdb/build] Fix build breaker with -std=c++11
33397 	When building with -std=c++11 I run into:
33402 	  available with -std=c++14 or -std=gnu++14 [-Werror]
33412 	Tested by building with and without -stdc=++11 on x86_64-linux.
33467 	solved by only allowing symbols not marked with language_fortran to be
33483 	GDB built with GCC 13.
33551 	unconditionally registered with the cache, and their underlying file
33579 	A local gdb test failed with this error message:
33634 	With gdb build with -fsanitize=thread, and the exec from test-case
33727 	With gdb build with -fsanitize=thread, and the exec from test-case
33834 	This triggered a segfault with target board native-extended-gdbserver, filed
33847 	With gdb build with -fsanitize=thread and test-case gdb.base/index-cache.exp
33974 	With gdb build with -fsanitize=thread and test-case gdb.base/index-cache.exp I
34085 	With gdb build with -fsanitize=thread and test-case gdb.base/index-cache.exp I
34198 	With gdb build with -fsanitize=thread and test-case gdb.base/index-cache.exp I
34303 	b) the symbol is global with non-default visibility, and
34317 	gdb/testsuite: Disable gdb.compile when testing with clang
34318 	Attempting to test the gdb.compile with clang as the compiler results in
34335 	gdb.ada/O2_float_param.exp with target board cc-with-gdb-index:
34361 	c-linkage-name.exp with gdb index"), which got us again:
34370 	together with commit dd05fc7071a ("Change .gdb_index de-duplication
34390 	+		 gdb, it has to use the encoded name, with any
34438 	Tested on x86_64-linux, with target boards unix and cc-with-gdb-index.
34530 	above commit was applied, this shows the problem with the above
34605 	PROMPT_NEEDED, and leaves stdin registered with the event loop.
34633 	Tested by rebuilding with --enable-targets=all.
34657 	This replaces sprintf and strcat calls with stpcpy, and makes use of
34672 	functions is unused.  I admit to getting a little carried away with
34695 	Avoid the use of sprintf with a "%s" format string, replacing with
34702 		* resrc.c (look_for_default): Likewise.  Add quotes with memmove
34737 		* config/tc-xtensa.c (xtensa_add_config_info): Use auto buffer
34749 		auto rather than malloc'd buffer.  Use sprintf count.
34779 	because with some older C libraries it wasn't reliable.  Nowadays it
34789 	Seen on Ubuntu 23.04 x86_64-linux using gcc-12.2 and gcc-12.3 with
34810 	doesn't happen with -m64, maybe due to inlining differences, I haven't
34925 	Avoid failures in fixed_points.exp with older GCC
34927 	failed with older versions of GCC.  This patch fixes the problem by
34943 	gprofng: Fix build with 64bit file offset on 32bit machines
34970 	It's better to include the proper header, which has declarations with
35093 	to DAP.  My first attempt at this ended up with recurse imports,
35111 	I'm not entirely happy with this patch, because if a user frame filter
35140 	In Python, a member name starting with "__" is specially handled to
35182 	ld: Fix test failures with --enable-textrel-check=error
35204 	I build gdb with -fsanitize=thread and ran the testsuite, and ran into the
35300 	- GDB core calls the callback associated with this file descriptor
35342 	This patch has been tested on a system with multiple GPUs which had more
35345 	testcase has been tested with `make check check-read1 check-readmore`.
35453 	generates with these bits.
35459 	supported version" (the BPF CPU versions start with v1.)
35636 	After looking into this for a while (with no results) using ASan and
35664 	Make the n64 ABI the default for 64-bit Linux targets specified with
35669 	There are the following regressions with the new target triplet:
35747 	mips64-openbsd  -FAIL: Compact EH EB #1 with personality ID and FDE data
35748 	mips64-openbsd  -FAIL: Compact EH EB #2 with personality routine and FDE data
35749 	mips64-openbsd  -FAIL: Compact EH EB #3 with personality id and large FDE data
35750 	mips64-openbsd  -FAIL: Compact EH EB #4 with personality id, FDE data and LSDA
35751 	mips64-openbsd  -FAIL: Compact EH EB #5 with personality routine, FDE data and LSDA
35752 	mips64-openbsd  -FAIL: Compact EH EB #6 with personality id, LSDA and large FDE data
35753 	mips64-openbsd  -FAIL: Compact EH EL #1 with personality ID and FDE data
35754 	mips64-openbsd  -FAIL: Compact EH EL #2 with personality routine and FDE data
35755 	mips64-openbsd  -FAIL: Compact EH EL #3 with personality id and large FDE data
35756 	mips64-openbsd  -FAIL: Compact EH EL #4 with personality id, FDE data and LSDA
35757 	mips64-openbsd  -FAIL: Compact EH EL #5 with personality routine, FDE data and LSDA
35758 	mips64-openbsd  -FAIL: Compact EH EL #6 with personality id, LSDA and large FDE data
35759 	mips64el-openbsd  -FAIL: Compact EH EB #1 with personality ID and FDE data
35760 	mips64el-openbsd  -FAIL: Compact EH EB #2 with personality routine and FDE data
35761 	mips64el-openbsd  -FAIL: Compact EH EB #3 with personality id and large FDE data
35762 	mips64el-openbsd  -FAIL: Compact EH EB #4 with personality id, FDE data and LSDA
35763 	mips64el-openbsd  -FAIL: Compact EH EB #5 with personality routine, FDE data and LSDA
35764 	mips64el-openbsd  -FAIL: Compact EH EB #6 with personality id, LSDA and large FDE data
35765 	mips64el-openbsd  -FAIL: Compact EH EL #1 with personality ID and FDE data
35766 	mips64el-openbsd  -FAIL: Compact EH EL #2 with personality routine and FDE data
35767 	mips64el-openbsd  -FAIL: Compact EH EL #3 with personality id and large FDE data
35768 	mips64el-openbsd  -FAIL: Compact EH EL #4 with personality id, FDE data and LSDA
35769 	mips64el-openbsd  -FAIL: Compact EH EL #5 with personality routine, FDE data and LSDA
35770 	mips64el-openbsd  -FAIL: Compact EH EL #6 with personality id, LSDA and large FDE data
35794 	three, with subsequent relocation types set to R_MIPS_NONE if further
35812 	with the respective dump patterns, also discarding `xfail' annotation
35906 		with addresses.
35929 		zeros and spaces with addresses as appropriate.
35936 	Also discard the `.MIPS.options' section, used with n64 MIPS binaries,
35937 	along with similar other MIPS sections (`.reginfo', `.MIPS.abiflags')
35975 	Expect IRIX 6 to fail with n32 testing then, removing this regression:
35983 		* testsuite/ld-mips-elf/mips-elf.exp: Expect IRIX 6 to fail with
35990 	with 32-bit addressing, otherwise causing assembly warnings:
35996 	n32 ABIs only, replacing the `-mips4' option from the `as' tag with
36001 	Error: -mips4 conflicts with the other architecture options, which imply -mips3
36003 	with n32 testing for some targets, and ultimately removing these
36022 	A few GAS tests expect to be assembled with 32-bit addressing, otherwise
36030 	unconditionally, removing these failures with OpenBSD targets:
36084 		* testsuite/gas/mips/llpscp-64.d: Add `as' tag with `-32'.
36091 	to run it with the n64 ABI.  And there is a corresponding `got-dump-2'
36103 	MIPS/LD/testsuite: Fix `attr-gnu-4-10' failures with OpenBSD targets
36112 		* testsuite/ld-mips-elf/attr-gnu-4-10.d: Add `notarget' tag with
36117 	MIPS/LD/testsuite: Fix `attr-gnu-4-10' failures with IRIX targets
36119 	default, which causes a failure with the `attr-gnu-4-10' test case due
36130 		* testsuite/ld-mips-elf/attr-gnu-4-10.d: Add `as' tag with
36135 	MIPS/LD/testsuite: Fix JALR relaxation test failure with IRIX 6
36144 	framework made with commit 78da84f99405 ("MIPS/LD/testsuite: Correct
36164 	MIPS/LD/testsuite: Fix unaligned JALX failures with OpenBSD targets
36165 	There are only n64 linker emulations included with `mips64*-*-openbsd*'
36167 	targets and force the n32 ABI, causing link errors with the targets
36170 	./ld-new: tmpdir/unaligned-jalx-0.o: ABI is incompatible with that of the selected emulation
36172 	./ld-new: tmpdir/unaligned-insn.o: ABI is incompatible with that of the selected emulation
36209 		with `run_dump_test_o32' and `run_dump_test_n32' rather than
36214 	MIPS/GAS/testsuite: Disable compact EH #7 tests with OpenBSD targets
36220 	mips64-openbsd  -FAIL: Compact EH EB #7 with personality id and fallback FDE
36221 	mips64-openbsd  -FAIL: Compact EH EL #7 with personality id and fallback FDE
36222 	mips64el-openbsd  -FAIL: Compact EH EB #7 with personality id and fallback FDE
36223 	mips64el-openbsd  -FAIL: Compact EH EL #7 with personality id and fallback FDE
36234 	MIPS/LD: Include n64 `.interp' with INITIAL_READONLY_SECTIONS
36239 	Let's include it with INITIAL_READONLY_SECTIONS, just like o32/n32 do,
36243 	with commit 94bb04b3c611 ("Use .reginfo rather than .MIPS.options in n32
36254 		* emulparams/elf64bmip-defs.sh: Include `.interp' with
36391 	".*" happens to work with the usual section names starting with a dot,
36619 	When building gdb with -O2 -fsanitize-threads, I ran into
36667 	gdb.dwarf2/typeddwarf.exp with target board native-gdbserver on Ubuntu
36697 	Without nopie the executable is PIE, with nopie it's static instead.
36725 	End with a line saying just "end".
36732 	are left with:
36736 	End with a line saying just "end".
36750 	[gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2 -flto=auto and gcc 7.5.0 some more
36751 	With a gdb build with -O2 -flto=auto and gcc 7.5.0 and test-case
36765 	This is the "value_print" variant of the problem with "c_print_type" I fixed
36766 	in commit 0d332f11122 ("[gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2
36767 	 -flto=auto and gcc 7.5.0").
36792 	With a gdb build with -O0 or -O2, the static destructor calling order seems to be:
36803 	However, when building gdb with -O2 -flto=auto, the static destructor calling
36835 	but with glibc debuginfo installed I get instead:
36847 	The FAIL is due to a mismatch with regexp:
36924 		std::string.  Return section name for STT_SECTION symbols with
37055 	This commit prohibits the combination: RV64 (or any ISA with XLEN > 32)
37227 	bpf: add support for jal/gotol jump instruction with 32-bit target
37329 	gdb/testsuite: replace $testfile with $binfile in one case
37367 	Tested on x86_64-linux, with target boards unix and readnow.
37375 	Fix crash with DW_FORM_implicit_const
37376 	Jakub pointed out that using DW_FORM_implicit_const with
37399 		* bpf-dis.c (print_insn_bpf): Print offsets with value 0 as "+0".
37403 		* testsuite/gas/bpf/mem.s: Add tests with offset 0.
37526 	In a review, Eli pointed out that @findex is redundant when used with
37590 	Tested with target bpf-unknown-none with both 64-bit little-endian
37606 	port.  The bpf.cpu file is becoming so complex and so nested with
37621 	* To replace the CGEN generated opcodes table with a new hand-written
37627 	* To replace the CGEN generated assembler with a new assembler that uses the
37630 	* To replace the CGEN generated simulator with a new simulator that uses the
37665 	* Target bpf-unknown-none with 64-bit little-endian host and 32-bit
37668 	* Target x86-64-linux-gnu with --enable-targets=all
37705 	upstream GDB testsuite with no regression.
37712 	Bring disassembly back in line with what the assembler accepts, thus
37713 	also making it self-consistent (with, in particular selector load/store
37774 	Tested gdb.opt/static-optimized-out.exp with gcc-8 to gcc-12, for which we now
37780 	and with gcc 7.5.0 and clang 13.0.1, for which we still consistently get:
37795 	In test-case gdb.tui/long-prompt.exp, with a prompt of 40 chars, the same size
37917 	scoped_restore_current_inferior_for_memory cause GDB to crash with a
37938 	could go forward with this and just fix ports if they break.
37943 	Inferior.read_memory, we only have the inferior to work with, so this
37984 	To improve consistency, this patch replaces `current_inferior ()` with
37992 	[gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2 -flto=auto and gcc 7.5.0
37993 	With a gdb build with -O2 -flto=auto using gcc 7.5.0, I run into:
38004 	This is a problem with the debug info, which marks the CU containing the
38032 	Build all the objdump extensions with --enable-targets=all
38202 	loading my machine, and the test seems fine with these removed.
38215 	run with different configurations:
38221 	We don't test with schedule-multiple on if we are using a remote
38234 	where, when testing with non-stop mode, GDB stops in a different
38253 	occurring in infrun.c.  Just like with that previous commit, this bug
38259 	is off, and again, schedule-multiple is on.  As with the previous
38327 	  processed the event associated with the completion yet, and (b) upon
38355 	Just like with the earlier commit, the fix is to spot the vfork parent
38390 	gdb: fix an issue with vfork in non-stop mode
38464 	And this makes sense, if we have a vfork parent with two thread, and
38498 	For testing, there is no test included with this commit.  The test was
38571 	  processed the event associated with the completion yet, and (b) upon
38619 	multi-threaded inferior with many threads, and GDB running in non-stop
38662 	with our cleverness.
38672 	check_vfork_catchpoints, and then continue with the test of _this_
38730 	This patch is aimed at making __bss_start properly aligned with the
38849 	separate "warning" calls.  If we do end up with multiple warnings in
38865 	[gdb/testsuite] Fix gdb.dwarf2/forward-spec.exp with read1
38866 	When running test-case gdb.dwarf2/forward-spec.exp with check-read1 we run
38924 	with the built-in type of the same name and can be confusing when
38957 	before GDB 14.  It can be reinstated (with modifications) later if we
38968 	Add a have_native_target helper function for use with require.
38969 	Move logic from auto-connect-native-target.exp into this helper.
39020 	gdb/cli: Improve UX when using list with no args
39021 	When using "list" with no arguments, GDB will first print the lines
39091 	We may as well start with the symbol table a little larger, saving
39092 	time resizing.  Even a simple C hello world compiled with -O2 -g will
39093 	exceed 16 symbols (by well over 3 times with gcc-11).
39095 		* symbols.c (symbol_begin): Create sy_hash with more entries.
39099 	Fix loongarch build with gcc-4.5
39106 	This makes sure copy_archive exits with ibfd and obfd closed.  Error
39151 	ada_attribute_name uses an array that must be kept in sync with an
39175 		symbols for a file with no section headers until all the
39188 	The values ascii and space however don't work well with !HAVE_WBORDER.
39284 	It's more elegant to make the section match up with its "_start"
39307 		(_bfd_xcoff_openr_next_archived_file): Start with clean ranges.
39326 	  with a simple change to the code.
39422 	with their legacy counterparts as well. Note how this change of decode
39468 	This adds a DAP test for fetching scopes and variables with an Ada
39583 	Replace use of xfree with byte_vector
39584 	This replaces a use of xfree with a byte_vector.
39591 	This removes a use of xfree from tracefile-tfile.c, replacing it with
39598 	Avoid crash with absolute symbol
39615 	      gdbserver: allow agent expressions to fail with invalid memory access
39617 	Now that agent expressions might fail with the error
39676 	      gdb/testsuite: add test for core file with a 0 pid
39711 	Just as with how GDB reports a normal breakpoint stop, if a breakpoint
39721 	gdb/testsuite: Testing with the nvfortran compiler
39722 	Currently, the Fortran test suite does not run with NVIDIA's Fortran
39750 	Types defined as fortran_complex16 do not compile with nvfortran, so it
39753 	gdb.fortran regression tests run with GNU, Intel, Intel LLVM and ACfL.
39756 	The gdb.fortran test results with nvfortran 23.3 are as follows.
39805 	    (check_new_section_flags): Error if "large" is used with a
39884 	This patch replaces all such casts with safer variants.
39938 	replacing alloca with a C++ container type would introduce unnecessary
39951 	So, in this commit, I propose replacing the use of alloca with a
39962 	with gdb::byte_vector.
39979 	So in this commit I replace the use of alloca with std::byte_vector
40065 	ld: fix build with old glibc / gcc
40066 	"rename" conflicts with a function of that name, which gcc from that
40076 	offers increased utilization of functional units with a limited
40097 	      gdb: handle core files with .reg/0 section names
40105 	there are any problems with me changing the license, this commit does
40138 	Those addresses are 64-bit addresses with the high bits set.  When
40211 	Thus calling target_resume with inferior_ptid == null_ptid is bogus.
40214 	with inferior_ptid == null_ptid on entry exactly to help catch such
40233 	assertion failure with his test case, and Marcel Telka also confirmed
40256 	binutils with a newly built compiler, ie. when $CC specifies -B itself.
40329 	x86: optimize pre-AVX512 {,V}PCMPGT* with identical sources
40333 	x86: optimize pre-AVX512 {,V}PCMPEQQ with identical sources
40350 	is being dealt with.
40359 	how this is being dealt with.
40380 	interpreter session invoked with the 'pi' command in GDB, giving more
40472 	gdb: handle core files with .reg/0 section names
40474 	tests GDB's ability to load a core file containing threads with an
40477 	with an lwpid of 0 represents idle cores.
40480 	crash when confronted with such a core file, there are still some
40481 	problems with GDB's handling of these core files.  These problems all
40498 	  Program terminated with signal SIGSEGV, Segmentation fault.
40559 	Because both these threads are created with an lwpid of 0 GDB reports
40577 	renumbers these sections inline with their .reg section.
40582 	don't clash with any of the pid's that might already be in use --
40585 	that core, so we don't want GDB to assign an lwpid that clashes with
40592 	  warning: found threads with pid 0, assigned replacement Target Ids: LWP 1, LWP 2
40597 	  Program terminated with signal SIGSEGV, Segmentation fault.
40647 	gdb/testsuite: add test for core file with a 0 pid
40665 	image generated by the Linux kernel GDB would (sometimes) crash with
40678 	However, if a core is idle, with no process currently running on it,
40704 	OK, GDB creates a thread with lwpid of 0 and carries on.
40706 	When we find the next thread (core) with lwpid of 0, we attempt to
40707 	create another thread with an lwpid of 0.  This of course clashes with
40713 	switch to a thread with minus_one_ptid, this resulted in a call to
40754 	compressed the core file with bzip2, which reduces it to just 750
40768 	  Program terminated with signal SIGSEGV, Segmentation fault.
40774 	anything with an lwpid of 0 as a process, rather than an LWP.  And
40797 	the first section with a name like ".reg/NN".  If we find no such
40876 	Fixes: d2fddb6d783 ("LoongArch: Fix ld "undefined reference" error with --enable-shared")
41366 	caused a regression with the native-gdbserver target board.  The bug
41387 	* fli (load-immediate) with pre-defined immediates
41388 	* fminm/fmaxm (like fmin/fmax but with different NaN behaviour)
41394 	Zfa defines its instructions in combination with the following
41525 …Prevent an illegal memory access when running the strings program with an excessively lerge minimu…
41529 	Fix used-before-initialized warnings when compiling elf.c with Clang-16.
41534 	  Blocks of 8 spaces be replaced with tabs.
41598 	opcodes/loongarch: print unrecognized insn words with the .word directive
41615 	inspect code with heavy bit manipulation, or of unclear signedness, but
41673 		throughout with proper styles.
41702 	be realized on LA64 with any of `addi.w`, `addi.d` or `ori`. If we tie
41703 	disassembly of such aliases with the corresponding GAS support, only one
41783 	gas generates SFrame section with version SFRAME_VERSION_2 by default.
41808 		output SFrame section with version SFRAME_VERSION_2.  Also,
41812 		section for plt entries with version SFRAME_VERSION_2.
41990 	For DT_GNU_HASH/DT_MIPS_XHASH, only defined symbols with non-STB_LOCAL
41992 	symbols with STB_LOCAL binding before symbols with other bindings and
42069 		* elfcode.h (elf_swap_ehdr_out): Omit section header with
42108 		* lexsup.c (parse_args): Enable --strip-all with
42109 		-z nosectionheader.  Disallow -r with -z nosectionheader.
42118 …I see these warnings from time to time, when configuring a build with  --enable-pgo-build=lto, I h…
42170 	(that does work also with the prefix tree matcher).
42172 	But I intended to not actually change behaviour with the prefix
42174 	archive names with a similar FIXME comment we already have in
42196 	reader -- in particular with gdb_index, this would require expanding
42393 	with the changed semantics, the call to sframe_fre_get_fp_offset () will
42398 	an error into non-error.  This change will be included with the next
42400 	with version node LIBSFRAME_1.0 for the first time.
42415 	whether the RA offset is fixed or not from the consumer.  Now, with the
42422 	following is seen with objdump --sframe:
42428 	error into non-error.  This change will be included with the next
42451 	some other linker (with a different command line option for symbol
42493 	lisbframe was first released with Bintuils 2.40.  As the library
42578 	Synchromize libiberty sources with master version in gcc repository
42580 	Sync config.guess and config.sub with upstream master versions.
42592 	We refer to FCSRs as $fcsrX, which ensures compatibility with LLVM
42641 	Since the test binary is compiled with debug information, fix by changing
42661 	relocations for these addresses are not sorted properly with other
42717 	lto test fails with -fno-inline in CFLAGS
42739 	gdb/testsuite: fix gdb.python/py-unwind.exp with python >= 3.11
42781 	standard_output_file dir is the wrong thing to do, because an invocation with
42783 	earlier invocation with GDB_PERFTEST_MODE == compile.
42812 	I looked into implement this using dprintf with the new %V printf
42828 	I realized that with a small refactoring, it is possible to type-check
42953 	PASS: gdb.tui/wrap-line.exp: width-auto-detected: cli: wrap
42962 	FAIL: gdb.tui/wrap-line.exp: width-auto-detected: cli: prompt after wrap
43059 	Prune linker warnings about an executable stack being created with the -z execstack option.
43062 	For test for PR 29072 when the linker is configured with --enable-default-execstack=no.
43064 …target_defaults_to_execstack): Always return false for linkers configured with the --enable-defaul…
43147 	patch replaces it with a std::vector<bool>, simplifying the code.
43200 	Replacing this with std::string simplifies it.
43331 	_get_threads returns threads with name field = None.
43339 	GDB does not pick up, but with this patch, GDB will pick up the thread
43352 	Test-case gdb.ada/catch_ex_std.exp passes for me with package
43361 	The test-case contains a require gnat_runtime_has_debug_info to deal with
43443 	Replace this with cleaning up the entire directory instead, for all
43458 	on openSUSE Leap 42.3, with python 3.4, I run into a
43469 	When running test-case gdb.arch/i386-disp-step.exp with target board
43505 	Running test-case gdb.ada/call-no-debug.exp with target board unix/-m64 works
43506 	fine, but if we run it again with target board unix-m32, we run into:
43509 	ld: i386:x86-64 architecture of input file `b~prog.o' is incompatible with \
43513 	This is due to compiling with no-force.
43517 	- then compiles prog.adb and pck.o into prog (with debug info).
43520 	compiled again, with debug info.
43540 	LoongArch: Fix ld "undefined reference" error with --enable-shared
43567 	The logic can actually be expressed with less code that way, utilizing
43606 	Allegrex supports some MIPS32 and MIPS32r2 instructions (albeit with
43649 	Revert "MIPS: fix some ld testcases with compiler"
43690 	[gdb/testsuite] Fix gdb.base/step-over-exit.exp with glibc debuginfo
43694 	Without glibc debug info installed, we have with target board unix/-m64:
43700 	and with target board unix/-m32:
43801 	[gdb/testsuite] Fix gdb.tui/long-prompt.exp with read1
43802 	When running test-case gdb.tui/long-prompt.exp with check-read1, we get:
43819 	Fix this by replacing the sequence with a single command:
43834 	interact with it, like Term::command.
43845 	starts with a bit that is supposed to anchor the prompt to the border:
43866 	[gdb/testsuite] Allow procs with default value args in with_override
43867 	Currently proc with_override does not work with procs with default value args.
43875 	[gdb/testsuite] Fix gdb.dap/type_check.exp with older python
43876 	On openSUSE Leap 15.4 with system python 3.6, I run into:
43969 	gdb/testsuite: Testing with the armflang compiler
43970 	Currently the Fortran test suite does not run with armflang because the
43975 	message notes that it was not tested with armflang.
43984 	>From what I can understand, the auto detection leverages the
44001 	gdb.fortran regression tests run with GNU, Intel and Intel LLVM. No
44004 	The gdb.fortran test results with ACfL 23.04.1 are as follows.
44037 	works with the version I have.
44122 	I've tried to make this code compatible with older versions of Python,
44123 	but I've only been able to try it with 3.9 and 3.10.
44285 	I can reproduce the same issue with gdb trunk on x86_64, by using optimize=-O3
44297 	[gdb/tui] Replace macro HELP_ATTRIBUTE_MODE with std::string
44298 	Replace macro HELP_ATTRIBUTE_MODE with a std::string.
44317 	Permit DW_OP_GNU_uninit to be used with DW_OP_piece
44337 	This GDB supports auto-downloading debuginfo from the following URLs:
44468 	As noted by Tom Tromey, there are some formatting issues with the ternary
44531 	issue with the way that debuginfod is cleaned up.
44727 	characters with no null-terminator at the end.
44737 	Running the above test with ASan compiled in no longer gives an error.
44784 		* elfxx-mips.c (free_ecoff_debug): Delete.  Replace uses with
44791 		with alloc_syments.
44842 	If a file is found but cannot be opened with BFD (bfd_open /
44920 	ELF targets with target-specific free_cache_info functions need to
45010 	there are issues with both the prologue skipper for AArch64 and Arm and an
45084 	output message when "memory-tag check" is issued with no arguments.  That's
45086 	similar messages are issued with error_no_arg.
45149 	uninitialized" warning with some combination of compiler and
45239 	dwarf2_record_block_ranges is only ever called with the text section
45245 	ELF: Don't warn an empty PT_LOAD with the program headers
45246 	When rewriting the program headers, don't warn an empty PT_LOAD with the
45298 	Bug PR gdb/21699 makes the observation that using $_as_string with
45342 	pass a pointer to this string, along with the length of this
45358 	is found, with unpredictable results.
45410 	Fortran and Ada this can be a bounded array of characters with no null
45506 	oprand char with micromips. So for mips32, we use:
45515 		For mips32, the position of sel in MFTR/MTTR is same with mfc0 etc,
45519 		concatenating rs with rx as the index of control or data.
45558 	MIPS: fix some ld testcases with compiler
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
45617 	Replace `addi` with `addiu` for some cases for both r6 and pre-R6.
45619 	Introduce some new testcases for r6 with FPXX/FP64.
45649 	When configure with triples mipsisa[32,64]rN[el,], the march value
45652 	      -march=mips32r6 is not compatible with the selected ABI
45653 	   2) mipsisa64r2el-linux-gnu -o32 generates objects with 64bit CPU:
45863 	Fix by replacing with "Disabling" and "use".
46016 	For TLS GD/IE, add the same condition with the relocate_section in the
46193 	[gdb/testsuite] Fix gdb.tui/wrap-line.exp with --disable-tui
46194 	When running the test-case gdb.tui/wrap-line.exp with a build configured with
46203 	Fix this by guarding the command with allow_tui_tests.
46210 	When running test-case gdb.tui/pr30056.exp with target board
46263 	I got a source window with only one line in it, and the cmd window taking most
46320 	The reason for this is that $_as_string returns a value object with
46392 	This works just fine with %V too:
46587 	For symmetry with on_inferior_appeared, I named this one
46692 	all existing notifications to the signal_received observers with calls
46702 	need to deal with the current interpreter (the "this" pointer).
46723 	[gdb] Mention --with/without-system-readline for --configuration
46724 	Simon reported that the new test-case gdb.tui/pr30056.exp fails with system
46731 	- mentioning --with-system-readline or --without-system-readline in the
46736 	  --with-system-readline.
46747 	Improve header information displayed with objdump -P for PE binaries.
46887 		with the default value 1.
46947 	arm-pe looks to be a very old PE implementation, incompatible with
47023 	gdb/mi: fix ^running record with multiple MI interpreters
47030 	2. Add a second MI interpreter with the new-ui command
47210 		* elfnn-riscv.c (riscv_elf_check_relocs): Replace bfd_link_pic with
47247 	ptrdiff_t (signed long) with size_t (unsigned long) values. Since just
47254 	Add a test-case that sets a prompt with color in TUI.
47330 	The present way of dealing with them - misusing MAX_MNEM_SIZE, which has
47331 	nothing to do with insn length - leads to inconsistent results. Since we
47358 	pseudo-prefixes (bringing things in line with the other use of figure
47415 	ia64-linux-gnu: "Explicit stops are ignored in auto mode"
47451 	Fix scoped_value_mark not working with empty value chain
47470 	later in the 'bad case', which lead me to notice the issue with
47547 	gdb: link breakpoints with intrusive_list
47563 	Replace the hand-maintained linked lists of breakpoint locations with
47608 …_advance(_BidirectionalIterator&, _Distance, bidirectional_iterator_tag) [with _BidirectionalItera…
47609 …  required from ‘constexpr void std::advance(_InputIterator&, _Distance) [with _InputIterator = re…
47610 …::next(_InputIterator, typename iterator_traits<_Iter>::difference_type) [with _InputIterator = re…
47742 	Add a checked_static_cast overload that works with references.  A bad
47743 	dynamic cast with references throws std::bad_cast, it would be possible
47771 	  (gdb) PASS: gdb.server/multi-ui-errors.exp: interact with GDB's main UI
47797 	If expect sees the prompt with nothing following it then everything is
47815 	gdb, infcmd: Support jump command with same line in multiple symtabs
47827 	This patch augments the DAP launch request with some optional new
47859 	"When a file is opened with update mode ('+' as the second or third
47886 	I considered letting callers pass in a block instead, with None
47989 	clear_current_line overwrites the current line with chars_per_line
47997 	of the line with '\r'.  A new line isn't actually started, so the prompt
48001 	Answering the prompt with 'q' throws an exception intended to bring gdb
48008 	indicate that it is a special purpose function intended for use with
48025 	generate the relocations).  Or with alternative toolchains that do encode
48026 	stuff in the relocated places with the assumption that a relocation
48056 	When testing gdb.arch/disp-step-insn-reloc.exp with clang in an x86_64
48058 	the function can_relocate_call, with a suggestion of a broken stack.
48124 	it to allow access to symbols with names matching that of a register (or,
48236 	annotates a tuiterm line with the active attributes.
48238 	For instance, the line representing the TUI status window with attribute mode
48239 	standout looks like this with Term::get_line:
48243 	but like this with Term::get_line_with_attrs:
48304 	decided after a while that I didn't want to mess with this code..
48311 		flagword*, and adjust to suit.  Replace while loop with for
48326 	function being unused.  I could have kept that declaration with its
48419 	GDB built with GCC 11.
48466 	gdb/testsuite: test for a function with no line table
48477 	added along with the original commit, but as was written, the test is
48489 	The new test creates a CU with two functions, only one of which is
48529 	  2. Update the warning text, I now start with a lower case 'e', which
48551 	will fail when GDB is built with Python 3.6 or earlier.  This is
48564 	building GDB against Python 3.7.9 and 3.6.15, with this commit all
48577 	* The R_RISCV_SET_ULEB128 needs to be paired with and be placed before the
48588 		must be paired with and be placed before the R_RISCV_SUB_ULEB128.
48666 	Most of those which use this hook already cope with NULL being passed
48693 	too relaxed: Any indication of a mode that's possible with BFD64 only
48791 	with the actual address of IFUNC symbol, it will call the IFUNC resolver
48916 	In this test, we create three dummy SFrame FDEs with 4 FREs each.  Then,
48917 	we use few negative tests to lookup FREs with PCs not in the range of
48931 	libsframe provides an API to find the FRE associated with a given PC in
48934 	In this test, we create two dummy SFrame FDEs with 4 FREs each.  Then we
48995 	parser doesn't look for types with names like this, but instead tries
49022 	variants.  This patch adds the extra tests to cope with the old
49033 	Trying to build binutils with an older gcc currently fails.  Working
49135 	with no changes in the test names.
49253 	The DisassemblerTextPart will capture a small piece of text along with
49277 	to display the disassembled instruction with the correct styling.
49279 	The new API lives in parallel with the old API.  Any existing code
49286 	This matches up with what happens when the Python API is not involved,
49348 	The tests that dealt with sub-classing DisassemblerResult have been
49425 	PR28902, -T script with INSERT ordering
49470 	makes the code a bit easier to read, by replacing "(*syms)" with plain
49648 	When running test-case gdb.dwarf2/opt-out-not-implptr.exp with target board
49662 	The DW_OP_constu pushes a value with "generic type" on to the DWARF stack, and
49683 	I ran test-case gdb.dwarf2/opt-out-not-implptr.exp with make-check-all.sh, and
49684 	with target board dwarf64 ran into:
49695 	compiler exited with status 1
49698 	The FAIL is the same FAIL I run into with target board unix/-m32: is_target_64
49713 	Say we have a terminal with a width of 40 chars:
49726 	And with TERM=ansi, a width of 39 chars:
49733 	Gdb uses readline to auto-detect screen size, and readline decides in the
49734 	TERM=ansi case that the terminal does not have reliable auto-wrap, and
49742 	- readline wrapping (in other words, prompt edit wrapping), and
49747 	III. Readline wrapping, auto-detected screen size
49749 	Let's investigate readline wrapping with the auto-detected screen widths.
49751 	First, let's try with xterm:
49759 	Now, let's try with ansi:
49781 	IV. gdb output wrapping, auto-detected screen size
49788 	but with TERM=ansi:
49794 	So what happened here?  With TERM=ansi, the width setting is auto-detected to
49824 	I didn't manage to come up with a regression test for PR cli/30411.  Perhaps
49927 	stops, it automatically deletes the breakpoints with their disposition
49965 	This is one part of the fix for GCC PR109128, along with a
49970 	records the object as one with offload data. That is, the linker never
49981 	with offload data.
50050 	represented with only 1 digit.
50066 	gdb/rust: fix crash for expression debug with strings
50144 	Consider a hello.c, with less than 10 lines:
50149 	and compiled with -g into an a.out.
50170 	but with compact-source on:
50182 	There are a couple of problems with compact-source.
50282 	with ASan.
50431 	Another fuzzer attack.  This one was a "set" with elements using an
50535 	I noticed that select_source_symtab is only ever called with nullptr
50545 	this patch replaces it with a for-each and an explicit temporary
50549 	This replaces ALL_DICT_SYMBOLS with an iterator so that for-each can
50553 	This replaces ALL_OBJFILE_OSECTIONS with an iterator so that for-each
50616 	gdbpy_initialize_*, and gdbpy_finalize_*, with the second being called
50644 	One possible problem with this change is that there is now no
50650 	Just like with init.c, when this environment variable is set we
50652 	functions.  As there is already a test that starts GDB with the
50655 	protection I guess we'd need to run all gdb.python/*.exp tests with
50658 	I have tested this patch with the environment variable set, and saw no
50683 	if these procs remained in sync with gdb_test.  Actually, the bug
50684 	specifically calls out gdb_test_multiple when using with '-wrap', but
50700 	  if the pattern from the test script ends with a '\r', '\n', or '.'
50701 	  then these will partially match the trailing newline, with the
50705 	  this case the '\[\r\n\]*' is replaced with '\r\n'.
50807 	longer called.  This is nice because it helps with the long term goal
50815 	Add a test-case that tests prompt edit wrapping in CLI, both
50816 	for TERM=xterm and TERM=ansi, both with auto-detected and hard-coded width.
50818 	In the TERM=ansi case with auto-detected width we run into PR cli/30346, so
50826 	Add a test-case that tests prompt edit wrapping behaviour in the tuiterm, both
50827 	for CLI and TUI, both with auto-detected and hard-coded width.
50829 	In the CLI case with auto-detected width we run into PR cli/30411, so add a
50836 	Debug info is lost for functions only called from functions marked with cmse_nonsecure_entr
50873 	name, type, and value of variables with simple types, and print only the
50874 	name and type of variables with compound types.
50877 	to update their user interface with the program's call stack every time
50949 	Stop the linker from loosing the entry point for COFF/PE code when compiling with LTO enabled.
51101 …In member function ‘void intrusive_list<T, AsNode>::push_empty(T&) [with T = frame_info_ptr; AsNod…
51102 …inlined from ‘void intrusive_list<T, AsNode>::push_back(reference) [with T = frame_info_ptr; AsNod…
51148 	annotated with keywords, and generates much of bfd.h and libbfd.h from
51166 		with a FUNCTION comment.
51186 	hash.c: replace some unsigned long with unsigned int
51199 		(bfd_getb24, bfd_getl24): Replace unsigned long with uint32_t.
51206 	The crc calculated is 32 bits.  Replace uses of unsigned long with
51216 		* auto-load.c (auto_load_objfile_script): Update type of
51253 	xcoffread.c: Fix -Werror=dangling-pointer= issue with main_subfile.
51273 	deallocated together with inclTable in allocate_include_entry and
51403 	A user found that an array expression with just a single value (like
51410 	Replace field_is_static with a method
51429 	with the resulting width being 77 instead of the expected 78.
51440 	cannot auto-wrap lines, and reserves one column to deal with that, and as a
51469 	After starting gdb with TERM=ansi, entering TUI, and issuing the command, we
51506 	[gdb/testsuite] Fix gdb.base/readline.exp with stub-termcap
51526 	gdb: Fix building with latest libc++
51596 	With a build with --disable-tui, we get:
51668 	The other option is to pull the MI into line with the CLI and prevent
51689 	to run with the separate MI/CLI UIs, and then tested 'info
51729 	gdb: make set/show inferior-tty work with $_gdb_setting_str
51731 	to work with $_gdb_setting_str.
51744 	gdb: make set/show cwd work with $_gdb_setting_str
51745 	The previous commit fixed set/show args when used with
51757 	gdb: make set/show args work with $_gdb_setting_str
51758 	I noticed that $_gdb_setting_str was not working with 'args', e.g.:
51813 	I see these failures, when running with the native-gdbserver of
51897 	Allow strings with printf/eval
51898 	PR 13098 explains that if a user attempts to use a string with either
51974 	There were some regressions in gdb.trace/*.exp tests when run with the
52084 		* coff/xcoff.h (struct xcoff_artdata): Replace min_elt with
52170 	Fix PR30358, performance with --sort-section
52208 	deficiency with GDB's documentation of the jump command.
52252 	bother anchoring the output with a '^', and a quick scan of the
52282 	injects the '\r\n' after the command regexp, thus we end up with this
52317 	that.  But also, with the current gdb_test, if a blank line suddenly
52322 	newline.  There are a strangely large number of tests that end with a
52403 	None of the expected test result need updating with this commit,
52405 	sequences, so the tests are as happy with one newline (after this
52406 	commit) as they are with two newlines (before this commit).  A later
52452 	occurs after a '\r\n', and that they never start with a 0.  Our
52505 	        to ensure that they neither conflict with future standard
52506 	        extensions nor clash with other vendors
52560 	  because the syntax collides with the pseudo-C BPF assembly syntax.
52676 	After a false start, I came up with this patch, which seems to work.
52719 	5) Masking with & 0xffffffff is better than casting to unsigned.  We
52731 	I noticed in the binutile Makefile that runtest is being invoked with
52737 	being compiled with the default "-g -O2" picked up in
52740 	Also, with the binutils testsuite now taking notice of CC_FOR_TARGET,
52741 	I found a couple of debuginfod.exp fails with one of my compilers that
52749 		with -Wl,--build-id.
52783 	when using many wild-statements with non-wildcard filenames we
52795 	against local_sym_name with a comment to that effect.
52814 	(i.e. with the workarounds remove testing would still succeed). Nor is
52815 	there any test for uses of symbols with names matching GPRs, where such
52816 	is permitted. Before altering how this is to be dealt with, install two
52847 	with the same O4 or O2, so avoiding errors earlier on doesn't really
52848 	help. Plus constructs with a relocation specifier (as percent_op_itype
52851 	starts with % or ( - i.e. these will be seen as e.g. "i%lo(x)", and
53044 	   21 Program terminated with signal SIGTRAP, Trace/breakpoint trap.
53112 	[gdb/testsuite] Fix auto-indent in gdb.gdb/python-helper.exp
53113 	When editing gdb.gdb/python-helper.exp, auto-indent is broken in my editor
53138 	[gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2 -flto
53139 	On openSUSE Leap 15.4, with gcc 7.5.0, when building gdb with
53140 	-O2 -g -flto=auto, I run into:
53164 	On openSUSE Tumbleweed, with gcc 13.0.1, when building gdb with
53165 	-O2 -g -flto=auto, I run into timeouts due to the breakpoint in c_print_type
53174 	combination with -prompt and found out that it doesn't work, because -wrap uses
53220 	Test-case gdb.base/utf8-identifiers.exp compiles starting with GCC 5, so
53327 	When running the dap tests on a system with tcl 8.5, we run into:
53367 	asm code with lots of debug info.
53377 	The triples with vendor `img` should do same.
53392 	Let's use N64 abi by default for the triple with gnuabi64.
53415 	rather than dejagnu's copy (mimicing what happens with an older dejagnu
53434 	We should exclude matches to the ending PC to prevent false matches with the
53464 	can be removed.  There isn't really an "auto" language, it's only a
53466 	language automatically".  But "auto" is never the current language.  The
53468 	fact that we're in "auto language" mode is noted by the language_mode
53471 	 - Change set_language to handle the "auto" (and "local", which is a
53473 	   cases (auto vs explicit language) more clearly separated anyway.
53475 	 - Adjust add_set_language_command to hard-code the "auto" string,
53476 	   instead of using the "auto" language definition.
53494 	   appears to "normalize" this value from "unknown" to "auto", remove
53506 	language_mode (auto vs manual), which are set by the
53539 	combination with each other.  This is a threshold to start using them.
53553 	 TARGET BOARD: cc-with-gdb-index
53580 	  less than the actual screen size, to deal with lack of auto-wrap.
53584 	  adjust to deal with lack of auto-wrap.  This becomes readlines notion
53618 	is due to gdb making readline adjust twice for the lack of auto-wrap, this is
53627 	And for TERM=ansi, with width and heigth set to 0:
53693 	On PPC64, with the test case included in an earlier patch, we found
53717 	linker might replace this with another instruction.
53772 	away with the abuse of "rex_used".
53791 	other functions need respective constification then, too (along with
53802 	RISC-V: Optimize relaxation of gp with max_alignment.
53826 	deal with the gp relaxation at this time.
53837 		(_bfd_riscv_relax_lui): Called _bfd_riscv_get_max_alignment with the
53876 	be a problem with ld random element access via the armap.
53964 	with the left number being unsigned int.
53967 		with uint16_t and unsigned char with uint8_t.  Make li_line_base
54097 	gdb: re-format Python code with black 23
54122 	gdb.base/whatis-ptype-typedefs.exp on PowerPC with IEEE float 128 as the
54128 	patch as also been tested on X86-64 with no new regression failures.
54132 	Symbols with GOT relocatios do not fix adjustbale
54134 …* config/tc-loongarch.c (loongarch_fix_adjustable): Symbols with GOT relocatios do not fix adjustb…
54162 	The instruciton didn't have the same address with mapping symbol will
54309 	space, which is shared with the child, so trying to attach would cause
54347 	However, you can have two inferiors that share a process target, but with one
54360 	layer).  fetch_inferior_event will then switch to the first inferior with
54381 	either of these, switch to an arbitrary inferior with that process
54391 	inferiors that fork, we end up with target stacks in the following
54404 	 - we start with inferior 1 as current
54409 	 - fetch_inferior_event calls switch_to_target_no_thread with linux-nat
54412 	   it's the first inferior with that target.
54686 	nothing wrong with this in any way.  However, this is causing my
54707 	This was fixed in gdb 13 onwards, but that means we're stuck with gdb's out
54719 	backwards compatibility with older gdb's/gdbserver's.
54839 	Avoid double-free with debuginfod
54891 	to its original state with another bfd_preserve_restore call before
54892 	exiting with a bfd_error_file_ambiguously_recognized error.
55032 	set to on replaces the spaces in the left margin with either '_' or '0',
55061 	The new command allows us to spot the problem with any window width.
55095 	Use 'require' with gnatmake_version_at_least
55111 	Note: R6 is not compatible with pre-R6.
55127 	This is a fuzzing PR, with a testcase involving a SHF_ALLOC and
55129 	section.  BFD doesn't handle compressed relocation sections, with most
55139 		* elf.c (bfd_section_from_shdr): Exclude reloc sections with
55179 	problems, save and restore iostream and iovec along with flags, and
55217 	1) The if (..) is meaningless -- we're xoring with that value, and of
55225 	3) anding with 0xf0 after shifting by 24 bits can allow betterin
55226 	encoding on RISC ISAs than masking with '0xf0 << 24' before shifting.
55247 	Replace an assertion in the dwarf code with a warning message.
55380 	prologue scanning unwinder doesn't know what to do with this
55452 	libctf, link: fix CU-mapped links with CTF_LINK_EMPTY_CU_MAPPINGS
55454 	even be invoked from ld with a feature added to stop ld of the
55458 	just with their input CU name but with a version of their input CU name
55459 	that was augmented with a numeric prefix if their linker input file name
55460 	was changed, to prevent distinct CTF dicts with the same cuname from
55474 	you ended up with a pile of useless empty dicts and then all the content
55475 	was in full dicts with the same names suffixed with a #0.  This seems
55493 	CTF dicts have per-dict errno values: as with other errno values these
55555 	allocated with 'new'.  This patch reimplements the symbol cache to use
55699 	Clang with LTO (clang -flto) garbage collects unused global variables,
55700 	Thus, gdb.base/align-c.exp and gdb.base/align-c++.exp fail with
55724 	because the align-c++.exp testcase is compiling with the C compiler
55733 	format it with black:
55819 	Frame.read_register to accept named arguments.  As with the previous
55825 	with the PendingFrame.read_register method, this allows for the
55890 	should change with this commit.  It is possible that a user has some
55901 	This commit aims to address a problem that exists with the current
55906 	with the current approach which will impact amd64 and ARM, and can
55951 	with %rcx having its value adjusted to contain the original %rip
55955 	with a corrupted value.  Obviously corrupting any register is bad; in
55964 	signal, and then tries again with the displaced step.  But it is that
56055 		"num_parents" non-zero with tests of "parents" non-NULL
56095 		strings in auto buffers.
56175 	building with libraries was highly repetitive.  Some of the text
56234 	under bfd/po/, i.e. in maintainer mode.
56259 	Some of the stabs handling code grows arrays of pointers with realloc,
56260 	to deal with arbitrary numbers of fields, function args, etc.  The
56298 		with string_used.  Copy so_string passed to debug_set_filename
56586 	gdbserver: allow agent expressions to fail with invalid memory access
56594 	with that area of gdb/gdbserver, and I don't want to break anything,
56696 	example with the updated error:
56721 	with native-gdbserver and native-extended-gdbserver target boards.
56746 	was compiled for 64-bit RISC-V with compressed instruction support:
56794 	I'm OK with that, we're no worse off that we are right now in that
56798 	and (in our imagined situation) with more aggressive levels of
56807 	After this commit gdb.base/unwind-on-each-insn.exp passes with no
56883 	the whitespace in the cpsie instruction was inconsistent with most of
56916 	correct, and were causing problems when trying to run with the
56921 	correctly with the remote-gdbserver-on-localhost board file.
56936 	all the breakpoints associated with the remote inferiors.  We then
56964 	Then run gdb.server/server-kill.exp with and without this patch.  You
56966 	while with this patch there will be one failure like this:
56981 	A potential test failure was introduced with commit:
57039 	A case of a string section ending with an unterminated string.  Fix it
57044 		to terminate string sections with a NUL.  Adjust invocation.
57176 	[gdb/testsuite] Fix gdb.base/trace-commands.exp with editing off
57190 	[gdb/testsuite] Fix gdb.threads/threadapply.exp with editing off
57195 	End with a line saying just "end".^M
57200 	but with editing set to off, we run into:
57204 	End with a line saying just "end".^M
57284 	attribute has not been provided, such as with Fortran code compiled with
57289 	Original code was removed with commit 6209cde4ddb8 ("Delete DWARF
57291 	("[gdb/symtab] Support DW_AT_main_subprogram with -readnow.") has also
57298 	there is also a minimal symbol called main, such as with programs built
57299 	with GCC version 4.4.7 or below, the backtrace will erroneously stop at
57350 	    'Zfh', 'F', 'D', 'Q': rounding modes "m" with special handling
57366 	This can't be done for all insns currently encoded with .byte. For one
57372 	together with EVEX.W (which could be expressed; note though EVEX.W set
57377 	In {,x86-64-}disassem.s many bogus encodings exist - some with ModR/M
57378 	byte but insufficient displacement bytes, some using SIB encoding with
57382 	in the way it deals with unrecognized encodings.
57386 	opcode{,-intel,-suffix}.d are also adjusted (along with an according
57433 	Deal with register and memory operands; immediate operands will follow
57438 	up cannot be used with .insn outside of 64-bit mode. Users would need to
57439 	specify an explicit LOCK prefix in combination with %cr0 etc.
57465 	For starters this deals with only very basic constructs.
57525 	sync_quit_force_run along with the quit flag.  This will allow the
57594 	The patch makes sure that, when parsing SME2 instructions with
57643 	would be redundant with USDOT.
57649 	x multi-vector forms (which would be redundant with USMLALL).
57654 	operand having a range of offsets.  As with ZA tiles, the expected
57723 	the range pn8-pn15.  Although we already had register fields with upper
57734 	to and from ZA.  As with SME, the instructions are also available
57766 	Like with the earlier vgx2 and vgx4 support, we get better error
57876 	consistent with the SP-based names.
57882 	between 32-bit and 64-bit forms of an instruction, with the 32-bit
57883 	forms being part of base SME2 and with the 64-bit forms being part
57918 	something that fails with a syntax error at operand 1.
57937 	AARCH64_OPDE_INVALID_VARIANT with the lowest argument.
58003 	There are often multiple forms, with different forms taking
58011 	the 2-register form with an out-of-range value, the out-of-range value
58022 	with the enum.
58050 	The problem becomes especially acute with SME2, since many SME2
58063 	which only triggers with SME2.
58100 	with the error being reported against the single-vector version
58143 	qualifier associated with the register, and the logic to calculate
58217 	with the error severity scheme, which becomes important later.
58224 	function becomes more complex with later patches.
58231 	of the index.  The patch keeps that test but adds another with
58246 	with a single argument for the index as a whole.
58256 	so there should be no memory problems with doing this.
58315 	The patch also replaces the boolean in_reg_list parameter with
58365 	immediates, due to the obvious potential for confusion with
58437 	gdb/python: Allow gdb.UnwindInfo to be created with non gdb.Value args
58489 	override this error with the error about 'sp' being missing.
58494 	return a tri-state enum, with states OK, MISSING, or ERROR.  The
58506 	clearer.  Errors from lower levels are not blindly overridden with the
58574 	Any functional user code will not have any issues with this change.
58583 	gdb.UnwindInfo classes, along with some tests.
58687 	Some of the exception messages will change slightly with this commit,
58740 	  3. The 'enabled' attribute is now implemented with a getter and
58816 	RISC-V: PR28789, Reject R_RISCV_PCREL relocations with ABS symbol in PIC/PIE.
58817 	The non-preemptible SHN_ABS symbol with a pc-relative relocation should be
58822 	* -pie, or -shared with -symbolic
58843 	    referneced with pc-relative relocation when generating shared object.
58851 	RISC-V: Clarify link behaviors of R_RISCV_32/64 relocations with ABS symbol.
58854 	* R_RISCV_32 with non ABS symbol cannot be used under RV64 when making
58863 	Seems like we should makes all R_RISCV_32/64 relocs with ABS symbol
58871 	    * elfnn-riscv.c (riscv_elf_check_relocs): Only allow R_RISCV_32 with ABS
58873 	    (riscv_elf_relocate_section): R_RISCV_32/64 with local ABS symbol under
58953 	with 'require'.
59020 	instruction GDB replaced that with when performing the displaced step.
59040 	with 'set debug displaced on').  The two interesting lines contain the
59246 	is built with amd-dbgapi support but where I don't have a suitable GPU
59306 	When running test-case gdb.server/stop-reply-no-thread-multi.exp with
59367 	[gdb/testsuite] Fix gdb.server/non-existing-program.exp with remote-gdbserver-on-localhost
59373 	During startup program exited with code 127.^M
59378 	But with target board remote-gdbserver-on-localhost I sometimes have:
59384 	During startup program exited with code 127.^M
59391 	Fix this by replacing "Exiting\r\n$" with "Exiting\r\n" in the regexps.
59405 	to address 0x62600000016c with insufficient space for an object of
59577 	TARGET_WAITKIND_THREAD_EXITED.  It also helps with the
59599 	destfile argument to gdb_remote_download, which doesn't work well with remotedir.
59624 	wouldn't work with installed testing.
59772 	Also declare the test-case unsupported with readnow.
59826 	Proc have_index is mostly used with $binfile, which gives problems
60006 	While trying to use gdb_can_simple_compile with a d program, I ran into:
60013 	The d compiler has a problem with the filename can_compile_d-105856.d, which
60031 	Simon pointed out that with gdb.dap/*.exp and target board
60043 	Likewise with target board native-extended-gdbserver.
60049 	  "set auto-connect-native-target off".
60082 	Note that some gdb commands probably will not work correctly with the
60091 	Since commit 6d263fe46e0 ("Avoid bad breakpoints with --gc-sections"), there
60123 	     which contain only variables (i.e. no code with associated
60171 	libctf: fix assertion failure with no system qsort_r
60174 	the comparison function with two identical arguments. The comparison
60177 	can-never-happen condition) and fails with an assertion failure.
60206 	inferior_thread ()/get_current_regcache () on a system with
60298 	bits of pointers, but wasn't immediately detected because systems with native
60308 	types of situation where we don't have a register cache. The problem with that
60364 	The following patch implements this idea with safety checks to make sure we
60368 	I discussed with Pedro the possibility of caching the mask register values
60379 	with threads running).  Thus gdb will attempt to remove non-address bits
60481 	Tested on x86_64-linux, both on openSUSE Leap 15.4 and Ubuntu 20.04, both with
60554 	Don't insert a second stub if the target is already compatible with
60570 	with BTI disabled is unchanged.
60601 	indirect operands, all of which appear to be working fine with this
60656 	    FAIL: gdb.dwarf2/dw2-out-of-range-end-of-seq.exp: END with address 1 eliminated
60672 	When running test-cases gdb.cp/annota{2,3}.exp with target board
60674 	trying to match inferior output together with gdb output.
60718 	information with a DWARF info dump.
60878 	I don't see a relevant difference with the implementation of standard_file
60936 	consistency with other architectures.
60974 	that I did not notice.  The bug is that, with these patches,
60990 	while assuming remote target user remote-target with homedir
61027 	function when handling a rust symbol.  That's due to GDB's auto
61041 	As an msymbol this is initially created with language auto, then GDB
61073 	eventually we consider our problematic symbol, and we end up with a
61119 	character, which doesn't match with the 'pars' the user supplied, so
61240 	commit doesn't address the issue in the C++ code which was fixed with
61310 	encoding variants, we can finally do away with this concept as well. Of
61328 	in line with the SDM long having dropped the NDS/NDD/DDS concept of
61463 	Regen ld/po/BLD-POTFILES.in
61483 		* elf.c (is_contained_by): Replace "bed" param with "use_vaddr".
61492 		stab sections with size less than 12 bytes.
61621 	This removes init_type, replacing all uses with the new type
61629 	This removes arch_type, replacing all uses with the new type
61645 	This removes alloc_type, replacing all uses with the new type
61653 	This removes alloc_type_copy, replacing all uses with the new type
61661 	This removes alloc_type_arch, replacing all uses with the new type
61720 	line table with an ordinary CORE_ADDR.
61803 	bp_loc_other, with that logic.  They also can't be
61807 	type describes that the way to insert these locations is with
61864 	The patch has been tested on Power 10 and X86 processor with no new
61874 	the new repeat_cmd_until procedure with the command set to "step" and an
61876 	with the existing uses of procedure gdb_step_until.
61989 	Fix this using '#include "precise-aligned-alloc.c"' and making that work with
62062 	implication is that md_operator(,1,) would need to deal with arch-
62074 	Yet again with the removal of gasp about 20 years ago this extra level
62083 	Again with the removal of gasp about 20 years ago the extra level of
62088 	This removes a leftover from i960 support; with that nothing is left
62172 	However, when buidling --with-pkgversion=XXX, we get
62176 	This small patch replaces "GNU Binutils" with ".*" instead.
62189 	The documentation for the Python Unwinders API could do with some
62207 	I've removed the incorrect code and replaced it with more generic
62284 	-zstack-size is added in order to ensure compatibility with previously
62351 	  * bfd/bpf-reloc.def: Created file with BPF_HOWTO macro entries.
62375 		* scripttempl/ft32.sc: Fix breakages from last edit.
62470 	In test-case gdb.arch/ftrace-insn-reloc.exp we generate two executables with
62489 	due to compiling two executables with the same name, and when uploading the
62520 	When running test-case gdb.arch/i386-pkru.exp with host board
62522 	Tumbleweed (with DEBUGINFOD_URLS set), I run into:
62524 	This GDB supports auto-downloading debuginfo from the following URLs:^M
62544 	[gdb/testsuite] Fix gdb.arch/amd64*.exp with local-remote-host-native.exp
62545 	There's a number of gdb.arch/amd64*.exp test-cases that fail with host+target
62567 	Tested on x86_64-linux, with host+target board local-remote-host-native.
62573 … * scripttempl/arclinux.sc: Remove stabs and comment sections and replace with inclusion of misc-s…
62595 	sub-structure.  This also interfaces with the gdb pretty-printer API,
62643 	Fix DAP frame bug with older versions of Python
62670 	Tested on x86_64-linux, with all relevant gdb/testsuite/boards/*.exp boards.
62673 	with the return value of proc ${board}_file for delete, so fix this.
62717 		(read_a_source_file): Make last_eol an auto var.
62823 	common than 'invalid=True'.  But I don't see a huge problem with this,
62974 	with plenty of other getters that also have a similar comment.  Plenty
63010 	Previously the postdefault handling was bundled together with the
63048 	There are a bunch of components that are declared with both a
63064 	First, the rust compiler still uses the C++-like _Z mangling, but with
63099 	When running gdb.python/tui-window.exp with host board
63115 	When running gdb.python/tui-window.exp with host board
63129 	When running test-case gdb.tui/completion.exp with host board
63137 	readline, which is unavailable with host board local-remote-host-notty.
63146 	When running test-case gdb.tui/tui-layout.exp with host board
63163 	When running test-case gdb.tui/tui-nl-filtered-output.exp with host board
63179 	When running test-case gdb.tui/corefile-run.exp with both host and target board
63184 	while this passes with USE_TUI=0.
63233 	So with target board native-gdbserver we get:
63237 	and with target board native-extended-gdbserver instead:
63429 	in build failures if the external binutils package is out of sync with
63459 	files compatible with older linkers (e.g.
63463 	with -fno-plt will lead to the `TLS transition from R_386_TLS_GD ...`
63490 	files compatible with older linkers (e.g.
63494 	with -fno-plt will lead to the `TLS transition from R_X86_64_TLSGD ...`
63588 	This also fixes the following warning with target board native-gdbserver:
63620 	In load_auto_scripts_for_objfile, gdb gives up trying to auto-load scripts
63623 	Fix this by declaring auto-load unsupported if sysroot starts with "target:".
63637 	Use require with test_compiler_info
63641 	More uses of require with istarget
63645 	Use require with gdb_skip_stdio_test
63648 	Use require with target_info
63727 	Logic exists to deal with prereqs or prereqs, and in many cases
63775 	ie. starting over testing another input file with rubbish left
63793 	Replace spaces with tabs in a bunch of places.
63803 	Then, fix the test-case for target board remote-stdio-gdbserver with
63879 	message which we do see with native testing:
63889 	to test has nothing to do with the message, so it should pass.  I only added
63910 	With test-case gdb.server/unittest.exp and a build with --disable-unit-tests I
63918 	but with target board remote-stdio-gdbserver I get instead:
63962 	Fix test-case gdb.server/sysroot.exp with target board
63973 	remote-gdbserver-on-localhost with REMOTE_TARGET_USERNAME=remote-target:
63975 	(gdb) PASS: gdb.server/multi-ui-errors.exp: interact with GDB's main UI
64026 	[gdb/testsuite] Fix gdb.server/connect-with-no-symbol-file.exp for remote target
64027 	Test-case gdb.server/connect-with-no-symbol-file.exp fails with target board
64064 		(lang_add_digest): Take etree_type* args.  Replace "illegal" with
64087 	The test fails on Power 10 with the RHEL9 distro.  It also fails on
64101 	Patch has been tested on Power 10 with RHEL 9, Power 10 with Ubuntu 22.04,
64102 	and Power 9 with Fedora 36 with no regression failures.
64162 	properly after rebasing and before pushing, we get this with the current
64174 	with this.
64454 	[gdb/testsuite] Fix gdb.cp/breakpoint-shlib-func.exp with remote-gdbserver-on-localhost
64455 	Test-case gdb.cp/breakpoint-shlib-func.exp fails with target board
64472 	[gdb/testsuite] Fix gdb.mi/*.exp with remote-gdbserver-on-localhost
64473 	When running test-cases gdb.mi/*.exp with target board
64485 	Tested on x86_64-linux, with and without target board
64491 	When building with clang 16, I see:
64519 	When building with clang 16, we get:
64535 	type with the appropriate signedness.  That is, with the same signedness
64547 	returns the right thing.  So I tried replacing all this with
64580 	      auto result = true ? A() : B();
64617 	- The cross-arch syscall number tests are all Linux-specific with
64659 	shut down" (9ae4519da90), a TUI-less build fails with:
64677 	gdb.testsuite/gdb-caching-proc-consistency.exp to not clash with
64708 	Note that gdb_caching_procs with args do not work with the
64718 	A regular tcl proc with no args looks like:
64788 	with a null sym_ptr_ptr.
64804 		* ecofflink.c (mk_fdrtab): Discard fdr with negative cpd.
64819 		* objdump.c (slurp_symtab): Replace bfd_fatal calls with calls
64822 		(disassemble_data): Replace fatal call with non_fatal call, and
64825 		(dump_ctf, dump_section_sframe): Replace bfd_fatal calls with
64842 		* nm.c (print_symdef_entry): Don't bomb with a fatal error
64858 	with a struct attached to the bfd.  Cleaner, and it avoids any concern
64912 	using the SIG prefix with kill does not work with dash's kill.  The
64916 	    The kill builtin does not accept signal names with a ‘SIG’ prefix.
64918 	Replace SIGINT with INT in that test.
64927 	    kill from util-linux 2.38.1 (with: sigqueue, pidfd)
64936 	SIG prefix (if it recognizes them with the SIG prefix, it's an
64980 	gdb/python: replace strlen call with std::string::size call
65007 	option was specified with an (optional!) argument. This rendered help
65008 	text inconsistent with actual behavior in certain configurations.
65025 	between "basic" types and any other type.  This patch dispenses with
65056 	with -O2, with g++ 11.3.0 on Ubuntu 22.04, I see:
65060 …inlined from ‘constexpr std::pair<_T1, _T2>::pair(_U1&&, _U2&&) [with _U1 = const char*&; _U2 = in…
65061 …r<typename std::decay<_Tp2>::type>::__type> std::make_pair(_T1&&, _T2&&) [with _T1 = const char*&;…
65068 	     1933 |   auto pair = internalvars.emplace (std::make_pair (name, internalvar (name)));
65198 	priority.  By reading the format with the most detail last, we ensure it has
65265 	leads to a segfault.  Fixed with the following patch, but I suppose
65288 	Fix typo with my email address
65378 	    $3 = htab_t with 3 elements = {0x6210003252a0, 0x62100032caa0, 0x62100033baa0}
65541 	breakpoint_deleted observer for any breakpoint with the number zero.
65643 	The problem was with the FinishBreakpoint.out_of_scope callback
65671 	associated with the breakpoint is released, so, when we get to the
65689 	Tested on x86-64/Linux with unix, native-gdbserver, and
65698 	gdb/testsuite: fix failure in gdb.mi/mi-pending.exp with extended-remote
65717 	failures with native-extended-remote anymore.
65747 	tests are going to be repeated once with the MI in the main UI, and
65748 	once with the MI on a separate UI.
65756 	The BODY will be run twice, once with VAR set to 'main' and once with
65763 	be run just once with VAR set to 'main'.
65768 	There should be no change to what is tested with this commit.
65806 	When creating a thread-specific breakpoint with a single location, the
65824 	always identical, that we might get away with removing one of the
65866 	which leaves us with "It's not clear that it's necessary...", which
65886 	Seen when building binutils with gcc -m32 on x86_64-linux.
65909 	This frees memory associated with the mips ecoff find_nearest_line.
65927 	most of the longs used in binutils with size_t, but that's more than I
65949 	During my audit of the use of gdb_exception with regard to QUIT
66009 	but with a throw following a check to see if 'reason' is
66074 	As with the Python updates, we don't want to permit this code to
66076 	with GDB receiving a SIGTERM.
66210 	for gdb.base/gdb-sigterm.exp when run on a machine with glibc-2.34.
66218 	identified.)  The rest of the patches in this series deal with this
66241 	GDB's state is out of sync with regard to the cleanup code's
66291 	In the future I think we should replace the use of raw "value *" with
66328 	However, with:
66350 	back to the unfollowed thread, follow it (stay with the parent), and
66353 	resume.  If following a vfork, however, stay with the vforking-thread
66358 	for a solo-thread resume (to collect the vfork_done event), with
66396 	resume it.  For example, with:
66407 	Or with:
66570 	have threads with the same ptid.
66572 	I decided to fix this by replacing previous_inferior_ptid with a
66598 	  Program terminated with signal SIGTRAP, Trace/breakpoint trap.
66786 	doesn't play well with static analysis.  When editing gdbarch.py, my
66798 	gdb: reformat Python files with black 23.1.0
66818 	Fix crash with "finish" in Rust
66825 	Note that the enclosed test case comes with an xfail.  This is needed
67244 	arrays, with entries like:
67255 	The column with TS|TP above is what defines each syscall's groups.  So
67304 	enums unless we find an enumerator with a non-flag like value.
67343 	I noticed that when a completion test will fail, it always fails with a
67352 	sometimes GDB would have printed a partial line before finishing with
67381 	gdb/amd64: replace xmalloc/alloca with gdb::byte_vector
67382 	Replace a couple of uses of xmalloc and alloc with a gdb::byte_vector
67453 	The new DWARF cooked indexer interacts poorly with the DWARF index
67456 	means that users with this setting enabled will see a slowdown.
67499 	On DOS systems, absolute paths start with the drive letter. This can
67543 	x86-64: don't permit LAHF/SAHF with "generic64"
67566 	these weren't used together anywhere). The issue was with
67575 	never sensible to use with 0xffffff90 operands. This should have been an
67594 	GDB: Fix out of bounds accesses with limited-length values
67600 	issue triggered with gdb.ada/limited-length.exp.
67611 	The segfault was a symptom of messing with the absolute section next
67681 	could be done with a bit more configure code.  However, I think we
67722 	Fix _bfd_elf_find_function so that it can cope with overlapping symbols
67932 	Commit f9c36cc99518 changed (and renamed) read_section_stabs with one
67969 	gdb: add --with-curses to --configuration output
67970 	'gdb --configuration' does not mention if GDB was built with curses.
67973 	built with curses independently of the availability of the TUI.
68079 	When running test-case gdb.dap/basic-dap.exp with a gdb without python
68092 	Tested on x86_64-linux, both with a gdb without and with python.
68103 	When dealing with case insensitive file systems, ".file line.s" and
68145 	When debugging a Linux Kernel built with pauth with an unpatched GDB, we get
68185 		continue on with rest of test past first fail.
68266 	     back end associated with the open BFD ABFD and translate the
68270 	That is, the function prototype runs together with the text in an ugly
68276 	     Call the back end associated with the open BFD ABFD and translate
68302 	the first ":". However, on Windows, a path can start with "C:". Adjust
68308 		(starting with C:).
68314 	/. This occurs when a file is concatened with the search path in
68344 	  2. Each MI command starts with a @subheading, and then the details
68357 	So the linker from producing an export data table when run with --exclude-all-symbols.
68374 	For a -g0 -fasynchronous-unwind-tables exec (without .debug_info but with
68400 	For a -g0 -fasynchronous-unwind-tables exec (without .debug_info but with
68527 	- replacing "while (1)" with "while (one)", where one is a volatile variable
68590 	foreach with the range iterator instead.
68771 	A regression in gdb.xml/maint_print_struct.exp was introduced with
68841 	for *one* process with GDB's list of threads for *all*
68865 	On SLE-11, with glibc 2.11.3, I run into:
68903 	But that already doesn't compile with say glibc 2.31, and regardless I think
68927 	compilation failure with target board unix/-fPIE/-pie.
69029 	I don't see much point in cluttering the source with the PROGRESS
69030 	macros, which of course do nothing at all with the definitions in
69084 	Convert it to an if() to deal with situations like this one found by
69230 	However, when the inferior is running on the background, say with
69247 	The idea is to set a breakpoint in the "foo" function with a condition
69265 	user typed Ctrl-C on the prompt a number of times with no inferior
69379 	 (gdb) with language ada -- ptype $_isvoid
69382 	while all other languages print it with a single <>, like:
69384 	 (gdb) with language c -- ptype $_isvoid
69435 	that haven't been handled, but that's not actually true, at least with
69448 	I tried to reach this code with TYPE_CODE_XMETHOD, but couldn't figure
69462 	with the error default case.
69469 	 (gdb) with language pascal -- ptype $_isvoid
69595 	by iterating on the frame chain, starting with the sentinel frame, like
69618 	When replaying with btrace, record_btrace_frame_sniffer insert entries
69812 	running with GDB_REVERSE_INIT_FUNCTIONS.
69839 	It becomes necessary to allocate internalvar with new instead of XNEW.
69950 	This fixes two failures in gdb.fortran/complex.exp with ifort.
69982 	lots of memory being requested, as the list is extended with a 16
70009 	functions) are specific to .gdb_index only, they are not shared with the
70087 	- openSUSE Leap 15.4 with linux kernel version 5.14.21
70088 	- openSUSE Tumbleweed with linux kernel version 6.1.8
70128 	the bump, but was too aggressive with this so far: It should only adjust
70175 	all uses with a call to value::lval.
70184 	of these set_* methods to be replaced with constructors; but I haven't
70604 	initialize_known_windows, and then replaces lots of '->' with '.'
70698 	Then GDB would replace the old 'my_window' factory with my new one,
70720 	Fix doc build dependencies for --with-system-readline
70721 	PR build/30108 concerns building gdb documentation with
70722 	--with-sytem-readline.  If the in-tree readline directory is
70731 	$BUILD/doc/GDBvn.texi with "@set SYSTEM_READLINE".  This surpresses the
70769 	32-bit number with no '.word' directive.  The above commit changed
70860 	One thing to note is that it is possible to have a hipcc installed with
70861 	a CUDA backend.  Compiling with this back-end will successfully result
70869 	is installed with the all ROCm installations (it is used by hipcc to
70898 	gdb: 'show config' shows --with[out]-amd-dbgapi
70900 	command line switch shows if GDB was built with the AMDGPU support or
71007 	    called 'foo' with type mst_solib_trampoline which also points at
71012 	    shared library.  This time GDB creates a msymbol called 'foo' with
71037 	strncmp_iw_with_mode with mode strncmp_iw_mode::MATCH_PARAMS and
71146 	it seems to me that in practice an Ada task maps 1:1 with a GDB
71160 	to the docs themselves.  Currently we document the commands with a
71352 	One possible fix would be to replace @srcdir@ with @abs_srcdir@, this
71357 	directories completely.  My hope is that, with more recent tools, the
71407 	Furthermore, there's a generic need to play around with enabling and disabling
71427 	Tested on x86_64-linux, -m64 and -m32.  Not tested with -mx32.
71436 	objdump -D of bss sections and -s with -j
71445 	This change does find some tests that used objdump -D with expected
71461 		sections with -j.
71473 		rather than objdump -D or objdump -d with tests checking for
71544 	Consider this GDB session with the current GDB:
71570 	Accesses with other languages work similarly, although for Ada only
71573 	inferior, bypassing the value history just as with C pointers.
71619 	GDB: Fix the mess with value byte/bit range types
71624 	terms of bits with these data types, e.g.:
71632 	Previously such accesses would be let through with unpredictable results
71637 	GDB: Ignore `max-value-size' setting with value history accesses
71698 	parameters -- it only makes sense to call them with keyword arguments.
71699 	This patch changes the few remaining cases to start with the special
71711 	    Continuing with signal SIGINT.
71718 		-re "^signal SIGINT\r\nContinuing with signal SIGINT.\r\nQuit\r\n.* $" {
71723 	The "Continuing with signal SIGINT" portion is printed by the top GDB,
71729 	expects the "Continuing with signal SIGINT" from the top GDB.  The
71732 	same as the top GDB's spawn id, but it's different when debugging with
71809 	List the frame unwinders currently in effect, starting with the highest \
71862 	performance while linking large programs (with many relocations).
71930 	The VPROT* forms with an immediate operand are entirely standard in the
71976 		with NULL sec->indirect_syms.
71985 	I've found that I often use dwarf-mode with relatively small test
72040 	"Cause GDB to print structures in an indented format with one member per line"
72098 	keep_contents is only used by the xcoff backend when dealing with
72099 	the .loader section, and it's easy enough to dispense with it there.
72205 	   argument), the auto-reinflation mechanism re-creates the user frame
72251 	   calls frame_find_by_id, to find the frame with the ID we saved.
72273 	   with frame_find_by_id.
72278 	Rergarding the first part of the change: with this patch, the sentinel
72281 	fields are now filled with the addresses used to create the user frame.
72284 	the user tries to create the same frame, with the same addresses,
72286 	So we won't end up with multiple user sentinels with the same ID.
72288 	Regular "target" sentinel frames remain with code_addr and stack_addr
72297 	 - Replace the sentinel_frame_id check in frame_find_by_id with a
72300 	   the one with addresses (0, 0).
72304 	 - Adjust create_new_frame to create a sentinel with the ID specific to
72311 	   specifically, since this function could be called with another
72446 	You won't see it with MI's "-interpreter-exec console" from a top
72455 	nor with MI's "-interpreter-exec mi" from a top level MI interpreter:
72467 	You won't see it either when running an MI command with the CLI's
72528 	never be called with a NULL objfile any more.
72649 	Finally, with glibc debuginfo present, we run into:
72663 	Tested on x86_64-linux, with and without glibc debuginfo installed.
72693 	If a breakpoint with multiple locations has a thread condition, then
72713 	with 'stop only in thread 1'.
72839 	ppc32 and "LOAD segment with RWX permissions"
72842 	want the warning when gcc is configured with --enable-secureplt.
72869 	  continue (with lock)
72874 	  stop all threads (with lock) (timeout)
72933 	error with an existing (I claim, badly written) GDB script.
72956 	number of .debug_info sections with relocations that included lo16 and
72965 	running with asan and under valgrind.  Under gdb with a non-asan
72967 	bug didn't show.)  Now I don't really care too much what happens with
73018 	The Texas Instruments SoCs with AARCH64 host processors have stricter
73019 	alignment requirements than ones with ARM32 host processors.  It's not
73063 	with the mainline Linux kernel expectation.  Since the mainline kernel
73174 	Like with segment overrides on LEA, optimize away such a redundant
73225 	Programs offloaded with the AMD ROCm platform can be written in the HIP
73262 	This program can be compiled with:
73266 	... where `hipcc` is the HIP compiler, shipped with ROCm releases.  This
73268 	ELF binary with the device code.  The ELF for the device can be
73269 	inspected with:
73276 …bit LSB shared object, *unknown arch 0xe0* version 1, dynamically linked, with debug_info, not str…
73288 	simultaneously.  Here's a sample session using a GDB with this patch
73309 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73310 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73311 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73322 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73323 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73324 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73327 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73328 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73329 …rror: `DW_OP_regx' operations must be used either alone or in conjunction with DW_OP_piece or DW_O…
73382 	    directly with `kfd`, but instead goes through the amd-dbgapi library
73425 	ptids of GPU threads are crafted with the following pattern:
73464 	the interaction with --target and --enable-targets:
73466 	 - if the user explicitly asks for amdgcn support with
73473 	 - if the user uses --enable-targets=all and --with-amd-dbgapi=yes,
73476 	 - if the user uses --enable-targets=all and --with-amd-dbgapi=no,
73517 	function pointer with our own, in which we call svr4_so_ops.handle_event
73524 	probe.  It then assumes this means there's a problem with the probes
73640 		* ld.texi: Replace the use of "unwind" with "stack trace".
73648 		* elf-bfd.h: Replace the use of "unwind" with "stack trace".
73662 		* as.c: Replace the use of "unwind" with "stack trace".
73762 	gdb/testsuite: fix fetch_src_and_symbols.exp with native-gdbserver board
73764 	doesn't work with the native-gdbserver board, I see this error:
73773 	This was introduced with this commit:
73781 	"run" command, which doesn't work with 'target remote' targets, as
73791 	delete_breakpoints proc with a dummy proc which does nothing.
73795 	with the fixes in commit 7dd38e31d67c, this test now passed using the
73814 	give a warning from an earlier attempt, and then succeed with a later
73838 	debug files. The test then replaces crc_mismatch-2.debug with
73845 	replacing the build-id based .debug file with the stripped binary and
73847 	with the correct debug file to download to make sure no warnings are
73852 	Fix compilation of the assembler with sanitization enabled.
73958 	    (gdb) mt print objfiles with-mf^M
73960 …Object file /home/smarchi/build/binutils-gdb/gdb/testsuite/outputs/gdb.base/with-mf/with-mf:  Objf…
73965 	    (gdb) FAIL: gdb.base/with-mf.exp: check if index present
74000 	Re: Another fix for EFI generation with LTO enabled
74028 	Along with the normal JAL alias, the C-extension one should have been
74068 	sh4-linux-gnu  XPASS: --gc-sections with __start_SECTIONNAME
74119 	gdb: Replace memcpy with std::copy to avoid some g++ warnings on sparc
74140 	As I am investigating a crash I see with the cooked index, I thought it
74142 	too familiar with it (that includes me), it can help get a feel of what
74222 	end up with:
74238 	that the range is sorted with respect to the comparison.
74244 	index, with the other always being the search string.
74295 	find and foreach virtual methods private and prefix them with "do_".
74352 	connection time is similar to a testrun with
74390 	of two connected remote targets with different support for the vCont
74460 	If we have for instance the following setup with inferior 2 being
74475 	The feature array of target with port :2345 which is currently selected
74478 	the configuration of target with port :2345.
74551 	changes with this commit.
74807 	The only downside I see with this change is if the tui_disable call
74875 	The hope with these new errors is that the user will have a better
74898 	Another fix for EFI generation with LTO enabled.
74904 	Ideally we'd do away with this somewhat questionable adjustment (leaving
74912 	All (there are just two) SSE2AVX templates with %xmm0 as first operand
74916 	x86: use ModR/M for FPU insns with operands
74945 	but with some code tidying in the pe/pep write_build_id functions.
75016 	This is a copy of the x86 gas -gcodeview test, with changes made for the
75021 	assembling aarch64-w64-mingw32 with the -gcodeview flag.
75119 	A number of tests end with "return".  However, this is unnecessary.
75137 	Entries are allocated with xmemdup0.
75153 	resolve gas shift expressions with large exponents to zero
75165 	Due to a GDB bug (visible when building with -D_GLIBCXX_DEBUG), GDB
75212 	meanwhile.  To help with this, make dap_wait_for_event_and_check and
75213 	_dap_dap_wait_for_event return a list with everything received before
75271 	is even more confusing.  At least, the lines are prefix with >>>, so
75279 	gdb/testsuite/dap: prefix some procs with _
75280 	Prefix some procs that are only used internally with an underscore, to
75310 	In order to work around this in gdb, epilogue unwinders were added with a
75418 	Use require with is_remote
75419 	This changes some tests to use require with 'is_remote', rather than
75436 	A few tests work on two different targets that can't be detected with
75445 	Use require with istarget
75495 	Test-case gdb.base/unwind-on-each-insn.exp compiles $srcfile with debug info, and
75498 	Occasionally, I try both files with debug info:
75514 	Test-case gdb.base/unwind-on-each-insn.exp compiles $srcfile with debug info, and
75517 	Occasionally, I try both files with debug info:
75631 	[ Note btw that we're seeing the effects of -momit-leaf-frame-pointer, with
75659 	On powerpc64le-linux, with gcc 7.5.0 I now run into PR tdep/30021:
75664 	but I saw the same failure before this commit with gcc 4.8.5.
75725 	focusable, which obviously, is not always true, so GDB fails with an
75809 	sets up our ANSI terminal emulator, so every layout command fails with
75830 	command both with a 'dumb' terminal and with the 'ansi' terminal.
75831 	When testing with the 'ansi' terminal, I have some limited validation
75847 	test script, this is more inline with how we name source files these
75854 	gdb_test with test_gdb_complete_unique, this will extend the
75914 	Fix seg-fault when generating an empty DLL with LTO enabled.
75917 	     with no assigned output section.
75930 	When building GDB with clang 16, I got this,
75946 	Tested by rebuilding on x86_64-linux with clang 16 and gcc 12.
75963 	2 (IMAGE_SUBSYSTEM_WINDOWS_GUI), which matches what happens with other
75973 	relocation to aarch64-w64-mingw32. As with x86, this is a two-byte LE
75974 	integer which gets filled in with the 1-based index of the output
75980 	The test is substantially the same as for amd64, but with changes made
76093 	compiled with nodebug, to prevent the dwarf unwinders from taking effect.
76161 	If objdump is used with both --disassemble=symbol and --reloc options
76195 	gdb: make frame_info_ptr auto-reinflatable
76226 	(frames created through create_new_frame, with the "select-frame view"
76376 	selected_frame_level for frames with level 0.  It leaves them at
76403 	The subsequent patches will need to call create_new_frame with an
76448 	ids for user-created frames (created with create_new_frame).  Add the
76502 	Move sect_offset with it too.  sect_offset is not a DWARF-specific
76582 	When running gdb.ada/arrayptr.exp (and others) on Ubuntu 22.04, with the
76583 	`gnat-11` package installed (not `gnat`), with UBSan activated, I get:
76628 	gdb/testsuite: add test for negative subrange bounds with unsigned form
76634 	     with GCC, for instance, where the ambiguous DW_FORM_dataN form
76652 	code above, the new test fails with:
76671 	to check a situation that once failed with the new section merging
76694 	* use better hash function (hashing 32bits at once and with better
76714 	allocation size worth of 3 pointers, with an increment worth of 2
76715 	pointers. Hence mnemonics with multiple templates can be stored more
76780 	ISA extension additions it would have been 12.5%), with a similar effect
76824 	with character strings such that they are executed twice, once with the
76826 	with the `set print elements' option, and then again with the limit
76827 	controlled with the `set print characters' option instead.  Similarly
76828 	with the `-elements' and `-characters' options for the `print' command.
76865 	to.  Using `set print characters' with any other value makes the limit
76867 	be restored to the default with the `set print characters elements'
76871 	with the same semantics, i.e. one can use `elements' to make a given
76872 	`print' invocation follow the limit of elements, be it set with the
76873 	`-elements' option also given with the same invocation or taken from the
76940 	user.  An optional value translation is possible with the structure to
76955 	which get translated to INT_MAX for the setting to be used with.
76992 	with their internal representation supplied.
77161 	size set to zero, but I would rather not edit lots of files when it
77166 		(HOWTO): Init new field with HOWTO_INSTALL_ADDEND.
77169 		code dealing with output_offset and output_section.  Just set
77239 	cleanliness, mostly auto-generated").
77356 	The patch has been tested on X86 and PowerPC with no regressions.
77409 	When testing with the native-extended-gdbserver, I get:
77417 	same spawn id, so it ends up working.  But with a gdbserver board,
77473 	update all testing accordingly.  This was done with a simple
77490 	Previously we had experienced issues with assembling a "VCVTNE" instruction
77513 	Similar errors were found with other type combinations and instruction
77590 	.word referencing foo, showing a problem with relocation handling.
77720 	We aren't affected by that bug with the current code, but as we move
77985 	This changes some tests to use "require" with !skip_avx_*.
78053 	    message beginning with _UNTESTED_, appending the `message' argument.
78068 	with "!" to indicate that the result should be inverted.
78079 	Don't use ensure_gdb_index with require
78101 	libsframe: replace an strncat with strcat
78102 	Calling strncat with the size of the src string is not so meaningful.
78157 	ELF_MAXPAGESIZE matters much more, with regards to layout of
78175 	sure there actually any such systems in use, again with
78177 	with all the warnings in the kernel config and requiring the
78225 	However, no compiler exists that emits a mixture of members with this
78226 	flag on and members with it off, and the linker always reserializes (and
78249 	executed anyway, and fails with a nasty-looking syntax error.  We can't
78303 		* bfd-in.h: Replace __FUNCTION__ with __func__.
78309 		* config/tc-cris.c: Replace __FUNCTION__ with __func__.
78313 		* dwp.h: Replace __FUNCTION__ with __func__.
78316 		* emultempl/pe.em: Replace __FUNCTION__ with __func__.
78336 	gdb/doc: fix install-html with Texinfo 7
78337 	Starting with Texinfo 7 (this commit [1]), the output directory for the
78370 	gdb: Update gdbarch.py with latest changes in gdbarch.c
78426 	On an x86_64 laptop running ubuntu 22.04.1 with unity desktop:
78454 	with LD_PRELOAD="" we have instead:
78484 	Tested on x86_64-linux, with and without LD_PRELOAD="".
78495 	Since 'a' is used as 1st operand only with J and JAL, and since JAL is
78560 	world" Windows program in asm, and (with GCC patches) a UEFI program in
78584 	      belongs to some class derived from `type', perhaps with other
78588 	    * If 'type' is a dynamic class (i.e. one with a vtable), then GDB
78642 	For consistency, replace tabs with spaces in all gdb.texinfo menus.
79205 	explicit_location_spec is used to lookup the symtabs associated with
79206 	the breakpoint being re-set.  This source_filename is compared with each
79298 		* po/SRC-POTFILES.in: Regenerate.
79302 	Fix crash with C++ qualified names
79330 	FAIL: Run pr18841 with libpr18841b.so
79331 	FAIL: Run pr18841 with libpr18841c.so
79332 	FAIL: Run pr18841 with libpr18841bn.so (-z now)
79333 	FAIL: Run pr18841 with libpr18841cn.so (-z now)
79407 	Starting with icc/icpc version 2021.7.0 and higher both compilers emit a
79490 	The function now keeps track of the bytes_flipped and then compares it with
79503 	Older bash looks to improperly deal with backslashes in here-documents,
79558 	behavior confusing to users, it is also not consistent with compiler
79561 	This commit makes GDB behavior consistent with compilers. it achieves
79563 	with the correct name, GDB continues searching through all include
79628 	I spotted a problem with scoped_debug_start_end's move constructor.
79650 	      auto res = scoped_debug_start_end<PT &> (pred, module, func, start_prefix,
79660 	built GDB with -fno-elide-constructors, and now I see it:
79753 	On openSUSE Leap 15.4 with python 3.6, the gdb.dap/basic-dap.exp test-case
79829 	PDP11 is a 16-bit processor with 16-bit logical addresses.  Therefore
79840 	depend on generate igen files, all with unknown names ahead of time.
79858 		./ld/ld-new: warning: test has a LOAD segment with RWX permissions
79924 	ends up calling gdb_breakpoint, which uses gdb_expect with a hard-coded
79956 	objcopy of archive, element containing an object with a fuzzed section
79975 	avoided with SHT_NOBITS sections.
80017 	when configuring with --disable-libbacktrace which causes the execinfo
80063 	with a 20-byte structure for each DLL, containing offsets into the rest
80070 	loader overwrites with the function pointers. Because there's no padding
80107 		(print_insn_xtensa): Replace fprintf_func with
80112 	Add test case for "finish" with variably-sized types
80113 	This adds a test case for "finish" with variably-sized types, and for
80123 	Fix inferior calls with variably-sized return type
80125 	to work correctly with variably-sized return types.
80138 	frame -- associated with _start.
80163 	because a call to the old-style method will not work with any
80203 	On a x86_64-linux machine with pkru register, I run into:
80349 	rules with cgen ports, so hopefully this should be correct.  These
80372 	to communicate with debuggers.  You can find more information here:
80436 	without checking to see if it starts with the "target:" prefix.  This
80443 	[gdb/testsuite] Fix gdb.python/py-breakpoint.exp with libstdc++ debug info
80483 	sim: replace -I$srcroot/bfd include with -I$srcroot
80488 	sim: replace -I$srcroot/opcodes include with -I$srcroot
80612 	sync libiberty sources with gcc mainline
80645 	Note that as with "disable probes", running simply "maint ignore-probes"
80675 	is seen when dealing with COM. I don't think LLVM emits this. Note that
80709 	- hit breakpoint, with call stack main.c:38 -> throw_exception_1
80712 	- hit the breakpoint again, with call stack main.c:48 -> throw_exception
80731 	[Inferior 1 (process 20046) exited with code 0236]^M
80769 	we get on x86_64-linux with target board unix/-m64:
80790 	Tested on x86_64-linux, with target boards unix/-m32.
80832 	On Ubuntu 22.04.1 x86_64, with glibc 2.35 I run into:
80848 	[gdb/testsuite] Fix gdb.base/corefile.exp with glibc 2.35
80849 	On Ubuntu 22.04.1 x86_64 (with glibc 2.35), I run into:
80926 	[gdb/testsuite] Fix gdb.reverse/step-indirect-call-thunk.exp with -fcf-protection
80942 	[gdb/testsuite] Fix gdb.cp/step-and-next-inline.exp with -fcf-protection
80974 	In contrast, with -fcf-protection=none, we get:
80998 	Tested on x86_64-linux, both with and without -fcf-protection=none.
81008 	Replace accessor function get_length with get_length_with_initial and
81150 	generate itable with everything else out of convenience.  This means
81252 	clean up some redundant -N0 setting with multirun mips.
81269 	This code loops over available cpus with "c", but then looks up the
81270 	cpu with "i".  Fix the typo so the code works correctly with smp.
81279 	This code loops over available cpus with "c", but then looks up the
81280 	cpu with "i".  Fix the typo so the code works correctly with smp.
81323 	Every file that igen outputs is then processed with the move-if-changed
81352 	associated with the dynamic linker was so long it would cause expect's
81366 	with common/ sim code, so move it all out to the existing or1k-sim.h.
81418 	The test fails to find --with-mpfr or --without-mpfr in the "show
81429 	with common/ sim code, so move it all out to the existing m32r-sim.h.
81437 	with common/ sim code, so drop the bfin.h include and move the remaining
81442 	with common/ sim code, so move it all out to a new header which only
81447 	with common/ sim code, so move it all out to a new header which only
81452 	with common/ sim code, so move it all out to a new header which only
81457 	with common/ sim code, so move it all out to a new header which only
81462 	with common/ sim code, so drop the pru.h include and move the remaining
81484 	with common/ sim code, so move it all out to a new header which only
81489 	with common/ sim code, so move it all out to a new header which only
81494 	with common/ sim code, so move it all out to a new header which only
81501 	with common/ sim code, so move it all out to a new header which only
81521 	with common/ sim code, so drop the msp430-sim.h include and move it to
81533 	with common/ sim code, so drop the ft32-sim.h include and move it to
81540 	with common/ sim code, so drop the d10v_sim.h include and move it to
81543 	Also rename the file to standardize it a bit better with other ports.
81549 	with common/ sim code, so drop the cr16_sim.h include and move it to
81552 	Also rename the file to standardize it a bit better with other ports.
81558 	with common/ sim code, so move it all out to a new header which only
81568 	with common/ sim code, so move it all out to a new header which only
81580 	with common/ sim code, so move it all out to a new header which only
81630 	This reduces the size of ld and is necessary with the following
81653 	sim-main.h to make some progress.  Things still build with just this.
81686 	sim: mcore: replace custom "word" type with int32_t
81687 	This is a 32-bit architecture with 32-bit registers, so replace the
81688 	custom "word" long int typedef with an explicit int32_t.  This is
81691 	sim: moxie: replace custom "word" type with int32_t
81692 	This is a 32-bit architecture with 32-bit registers, so replace the
81693 	custom "word" int typedef with an explicit int32_t.  Practically
81706 	sim: mips: merge mips64* with existing multi-run build
81711 	sim: mips: merge mips64vr5000 with existing multi-run build
81733 	1. prefixed extensions need to be seperated with `_'.
81747 	    (riscv_parse_std_ext): Removed, and merged with riscv_parse_prefixed_ext
81802 	Since SIM_ADDR is always 32-bit, it might truncate the address with
81812 	external_IMAGE_DEBUG_DIRECTORY, which was later overwritten with
81826 	sim: mips: merge mips64vr4300 with existing multi-run build
81860 	objdump/readelf: sframe: emit marker for SFrame FDE with B key
81900 	Note that the information in this bit will always be used along with the
81916 	their definition in listings with macro expansion enabled. Adjust this
81921 	Note that with the code movement the conditional operator isn't
81964 	In particular this hides issues with dependencies between features.
81981 	Features with prereqs as well as features with dependents cannot re-use
82065 	objects for each target.  To avoid duplicating the list with the
82076 	The testcase in the PR had a variable with both DW_AT_decl_file and
82108 	Also this allows building of GMP and MPFR with the toplevel
82114 	with GMP and MPFR in the toplevel (static library used at that point for both)
82162 	with the proposed change to gdb.cp/nsusing.exp, we get the following
82217 	for quite a while, with more such uses recently having been added.
82230 	belong there since the code is dealing with symbols.  Multiple symbols
82378 	with the dgen.py script, so we don't need this old tool anymore.
82421 	gdb executable is not installed with install-strip.
82436 	PR29915, bfdio.c does not compile with mingw.org's MinGW
82445 	Regen opcodes/po/POTFILES.in
82632 	ld bootstrap test in build dir with path containing symlinks
82672 	allocation done with sanity checking in bfd_get_full_section_contents,
82713 	Re: The problem with warning in elf_object_p
82733 		with print.
82776 	well (a non-empty SFrame section with valid SFrame FREs is generated).
82787 	objdump/readelf: sframe: emit marker for FREs with mangled RA
82795 		with "[s]" if RA is signed with authorization code.
82813 	DW_CFA_AARCH64_negate_ra_state in aarch64 is multiplexed with
82841 	the RA is signed/unsigned with PAC authorization code: this bit is named
82846 	unwinding, whenever an SFrame FRE with non-zero "mangled RA" bit is
82874 	To help with that, this patch delays the /proc/pid/mem check until we
82955 	address of the label into a value object with builtin_core_addr type.
82972 	We can then cast the new value to 'void *' type with a call to
82989 	Replace the use of struct buffer in linux-osdata.c with std::string.
83045 	This test needs run with ASan enabled in order to fail when it
83120 	problematic, as explained here [1].  In short, with this patch [2] that
83145 	So, it started with modifying command_line_input as described above, all
83151 	does not modify the input string, because I was able to change it (with
83235 	callers I realized it could be removed and replaced with calls to
83285 	[gdb/testsuite] Fix gdb.base/condbreak-multi-context.exp with gcc 4.8.5
83290 	  data member initializers only available with -std=c++11 or -std=gnu++11 \
83298 	Tested on x86_64-linux, with gcc 4.8.5, 7.5.0 and clang 13.0.1.
83413 	Connections are represented in Python with gdb.TargetConnection
83426 	fires, which we catch with connpy_connection_removed, this function
83485 	  auto ref = std::move (m_stack[stratum]);
83554 	Don't attempt to run gold tests with -z bndplt
83575 	bndplt (MPX prefix)", that some of my builds were failing with
83668 	    signed int, so no builtin type with that name will be found, GDB
83675 	    will be no partial symbols with that name, so GDB will not expand
83683 	    'signed int' is just 'int', GDB then looks for any symbols with
83688 	with C, now the initial builtin type lookup will succeed, and GDB
83719 	The testsuite checks if GDB was started with the -readnow flag by
83773 	(array[i], *s, len) == 0" in arg_lookup function passes with "strncmp ("e64",
83790 	As Alan points out, ASAN takes issue with these constructs, for
84047 	      gdb/testsuite: fix gdb.trace/unavailable-dwarf-piece.exp with Clang
84105 	Macros with just a single use site are a little pointless to have, and
84129 	Replace gdbpy_should_stop with gdbpy_breakpoint_cond_says_stop
84130 	In 2014, the function `gdbpy_should_stop' has been replaced with
84133 	This replaces `gdbpy_should_stop' with `gdbpy_breakpoint_cond_says_stop' in the
84148 	bfd.  It is possible when opening and closing bfds with mis-matched
84340 	Having templates with a suffix explicitly present has always been
84342 	anomaly from move-with-sign-extend is to consolidate the insn templates
84348 	The need for them on the operand-less string insns has gone away with
84364 	are also wrong to use with these relocations.
84366 	Further fold the remaining check (BFD_RELOC_386_GOT32) with the XRELEASE
84376 	all, isn't invalid with "XRELEASE").
84379 	type checks that were there were effectively redundant with other ones
84401 	was redundant with the exact same one a few lines up.
84406 	Having templates with a suffix explicitly present has always been
84414 	move-with-sign-extend be left as broken as it always was.
84417 	Note that with the dropped CMPSD and MOVSD Intel Syntax string insn
84419 	(with memory operands) cannot occur anymore. With that
84496 	declaration" warning with our choice of warning level and with at least
84535 	"static" in i386-gen (we may want to do away with i386_regtab_size
84563 	On s390x-linux with target board unix/-m31, I run into:
84607 	but with displaced stepping we have instead (note the 0x80000000 difference):
84630 	Tested on s390-linux, with native and target board unix/-m31.
84699 	Define constants in sframe.h for the various limits associated with the
84753 	existing gdb/features/aarch64-tls.c auto-generated file with a new file that
84794 	handles this situation.  _bfd_mips_reloc_offset_in_range with
84833 	(gdb) FAIL: gdb.guile/scm-symtab.exp: test find-pc-line with resume address
84861 	Fix this by replacing ">" with ">=".
84924 	When building GDB with the following CFLAGS and CXXFLAGS as part of
84991 	gdb: skip objfiles with no BFD in DWARF unwinder
84992 	While playing with JIT reader I experienced GDB to crash on null-pointer
85033 	PowerPC: Add support for RFC02656 - Enhanced Load Store with Length Instructions
85125 		test with abfd->flags test.
85140 		with config.compress_debug.
85350 		ELFCOMPRESS_ZLIB and ELFCOMPRESS_ZSTD with ch_compress_zlib and
85356 		uses of ELFCOMPRESS_ZLIB and ELFCOMPRESS_ZSTD with
85497 	Use as many tabs as possible for indentation and pad with spaces to keep
85518 	Before fiddling with the code let's put in place a test covering what
85531 	redundant with the one left in place from the original input line by all
85578 	with no assembler directive prefix (e.g. without .word or .short).
85582 	with what many of the other libopcode disassemblers do.
85653 	disassemble LAR and LSL with 16-bit source operand.
85708 	"set/show debug solib", with the solib_debug_printf macro.
85763 	The tests set a break point with the command break *func.  This sets a
85767 	r2 before reaching the LEP.  When the function is called with func() the
85777 	both PowerPC with a GEP and LEP as well as on other systems.  The GEP is
85788 	Patch tested on PowerPC and Intel X86-64 with no regressions.
85930 		* po/POTFILES.in: Likewise.
85937 	interfering with my hacking on gdb by making test runs extremely long,
86041 	When I run the gdb testsuite on a powerpc64le-linux system with (slow) nfs
86128 	First, reproduce this on x86_64-linux with --enable-targets=all, by replacing
86129 	the test for 'istarget "s390*-*-*"' with a test for 'get_set_option_choices
86148 	aren't called with the prefix tree.  Hence initialization of the latter
86205 	This lazy resolution introduces a problem with sections added late
86282 	slightly, bringing a piece of code out of sync with its comment, and
86291 	   being in need of dealing with the compiler anomaly, and hence the
86322 	For one FSUB{,R} and FDIV{,R} would better be tested with operands in
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
86503 	Define that structure and fill it with default parameter values
86518 		* elf32-xtensa.c (xtensa-config.h): Replace #include with
86529 		* config/tc-xtensa.c (xtensa-config.h): Replace #include with
86533 		* config/tc-xtensa.h (xtensa-config.h): Replace #include with
86535 		* config/xtensa-relax.c (xtensa-config.h): Replace #include with
86544 		with xtensa-dynconfig.h.
86770 	Don't use auto for lambda parameter
86771 	Older gcc versions (here 4.9.2) can't handle auto for a lambda parameter:
86774 …../../gdb/windows-nat.c:629:12: error: use of 'auto' in lambda parameter declaration only availabl…
86775 	        [=] (auto &th)
86789 	  444 |   auto fn = [] (LPVOID self) -> DWORD
86842 	Will compile just fine for C++11 and C++14 with GCC.  Clang on the
86881 	code, will not be compiled with support for handling exceptions.  As
86916 	Bug gdb/29712 identifies a problem with the Python disassembler API.
86994 	compiled with exception support.
87005 	failed (with one special case described below), then, when we
87018 	My thinking here is that should the first call fail with some unknown
87019 	error, GDB should not keep trying with any additional calls.  This
87085 	action associated with this probe inside GDB is DO_NOTHING, this means
87168 	On powerpc64le-linux, with test-case gdb.ada/out_of_line_in_inlined.exp I run
87229 	Doing so caused some failures with the native-gdbserver board.  Some
87231 	with that board to just return with "untested".  Change them to add an
87234 	Some gdb.pascal tests also failed with native-gdbserver, because they
87322 	the kill command, when the target is left with no threads, its
87324 	working with the assumption that a target with no threads (and therefore
87330 	even if the target has another inferior with stopped threads,
87373 	with a -ex switch, the bug doesn't trigger.
87379 	GDBserver crashes with a segfault here:
87583 	instead of declaring global variables with the `global` keyword.
87590 	[gdb/testsuite] Fix gdb.arch/altivec-regs.exp with gcc 4.8.5
87681 	This issue is found while building OpenSBI with 'H' extension (resulting
87701 		sequence with correct instruction bits.
87710 	instructions with .insn") tried to start supporting long instructions but
87714 	2.  It generates "value conflicts with instruction length" even if a big
87740 	instructions with .insn") tried to start supporting long instructions but
87956 	If we instrument cc-with-tweaks.sh to remove the .gnu_debugaltlink file after
87957 	dwz has created it, with test-case
87958 	gdb.threads/access-mem-running-thread-exit.exp and target board cc-with-dwz-m
88118 	Also align node name with section title where possible.
88180 	breakpoints that have been set before, starting with the "silent"
88249 	affected all templates with one memory-only operand and one or more
88299 	gas: Disable --gcodeview on PE targets with no O_secrel
88459 	This is needed to permit using the helpers for register sets with a
88535 		(many functions): Replace uses of "unsigned long" with
88541 	Replace the macros with a small wrapper function that verifies the fseek
88544 		* readelf.c (FSEEK_FUNC): Delete, replace uses with..
88590 	with our choice of wanring level and with at least some gcc versions.
88617 		against symbols with a NULL section.
88631 	When getting the locno of a bpstat, handle the case of bp with null locations.
88636 	Note: GDB crashes on this problem with an internal error,
88702 	bfd	* cpu-arm.c (scan): Accept machine names prefixed with "arm:".
88703 		* cpu-aarch64.c (scan): Accept machine names prefixed with "aarch64:".
88711 	For targets with secext, msp and psp can be seen as an alias for one
88717 	For targets with secext, msp and psp can be seen as an alias for one
88725 	tdesc-xml and only send bitsize="128", gdb can't deal with a reg
88726 	with default type int with bitsize==128. So Just return csky_vector_type()
88740 	gdbsupport compilation badly fails with GCC 12 on Solaris, with errors
88788 	sparc-sun-solaris2.11, and sparcv9-sun-solaris2.11 (together with
88846 	   for a breakpoint with a single location.
88863 	  - Use @kbd instead of examples with only one command.
88915 		* opcode/riscv-opc.h: Update DECLARE_CSR declarations with
88950 	with a current process but no current thread.  This tripped on ps_getpid
89010 	When building on Ubuntu 22.04, gcc 12, x86-64 with -m32 and -O2, I get:
89042 	gdb/testsuite: rewrite gdb.cp/call-method-register.exp with dwarf assembler
89049 	This means that the test will only work with Clang, and, as we have to
89054 	By switching to the DWARF assembler, the test will work with gcc and
89069 	Additionally, on x86-64, I've tested with Clang and gcc, and the test
89070 	runs and passed with both compilers.
89076 	gdb/testsuite: fix gdb.debuginfod/fetch_src_and_symbols.exp with Clang
89078 	failure when run with some older versions of Clang, e.g. 9.0.1.
89080 	The problem appears to be with Clang's generated line table.  The test
89094 	However, with Clang 9.0.2, I see GDB stop on the 'asm' line.
89121 	This commit just renames the source file inline with the test script,
89127 	with some other test (it isn't).
89135 	failing when run with Clang as the compiler.
89141 	When compiling with Clang though, the default is for no build-id.
89152 	now (mostly) passes with Clang 9.0.1 and 15.0.2, and still passes with
89160 	gdb/testsuite: fix gdb.compile/compile-ops.exp with clang
89162 	run with Clang as the compiler.
89205 	inline with what other DWARF assembler tests do.
89221 	starts failing, we can add the lines back, along with an explanation
89231 	gdb/testsuite: fix gdb.trace/unavailable-dwarf-piece.exp with Clang
89233 	failing when run with Clang.  Or rather, the test was not running as
89244 	with the '.S' extension.  However, this particular test uses a '.s'
89262 	With these changes the test now passes with Clang 9.0.1 and 15.0.2,
89263 	and also still passes with gcc.
89269 	gdb/testsuite: don't avoid DWARF assembler tests with Clang
89275 	fine with Clang.
89277 	The two tests that I modify in this commit both work fine with Clang,
89278 	at least, I've tested with Clang 9.0.1 and 15.0.2, and don't see any
89280 	tests from running with Clang.
89310 	guarded with OBJ_ELF consistently.
89315 		  with OBJ_ELF.
89335 		Replace No_bSuf|No_wSuf|No_lSuf|No_sSuf|No_qSuf|No_ldSuf with
89364 	The test just needs to be compiled with -fvar-tracking to enable GDB to
89373 	Try compiling with -fvar-tracking.
89384 	Patch tested on Power 10 with no regressions.
89397 	infrun.c.  This patch replaces the various uses of NULL with nullptr in
89402 	The patch has been tested on PowerPC and Intel X86_64 with no new unexpected
89534 	new with GCC 12), which are fixed by this patch:
89576 	* find_memory_regions_callback fails with
89605 	With those changes, procfs.c compiles again.  Together with the hack
89838 	I've tried making output redirection work with remote_exec, but that seems to
89847 	Tested on x86_64-linux, without and with bzip2 installed.
90046 	with their error message strings are also defined.
90053 		* Makefile.def: Add libsframe as new module with its
90141 	".cfi_sections" with ".sframe" in it.  The newly added command line
90198 	functions for .sframe generation.  These provide gas with architecture
90326 	for them with an autoconf macro resulting in an addition to LIBS.
90346 	- Configure --with-system-zlib and --without-system-zlib.
90347 	- Check link dependencies of installed GDB with both --enable-shared
90370 	        (md_assemble): Expand comment before swap_operands() with rmpquery.
90399 	reproduced with:
90454 	- setting jit_libname with the name as returned by gdb_load_shlib
90455 	- allowing the libraries to be prefixed with the remote target directory.
90490 	When running test-case gdb.base/solib-vanish.exp with target board
90503 	When running test-case gdb.base/infcall-exec.exp with target board
90534 	When running test-case gdb.base/print-file-var.exp with target board
90560 	number of test-cases fails with a remote target setup, for instance test-case
90563 	So, why don't we see these fails with our remote target boards in
90579 	Make these problems visible with remote-gdbserver-on-localhost.exp by
90617 	When running test-case gdb.base/foll-exec.exp with target board
90640 	On aarch64-linux, with a gdb build without libexpat, so without xml support, I
90726 	This patch has been tested on Power 10 and x86-64 with no regressions.
90759 	With this patch, the five test cases still fail but with the message "Value
90822 	I don't see any difference in testsuite results with or without this
90838 	directive ".pacspval" and encodes this directives with opcode
90874 	-   Compiled with Clang
90891 	block with DIAGNOSTIC_IGNORE_USER_DEFINED_WARNINGS to disable Gnulib-
90930 	supported, which is the case if we've build gdb with --enable-targets=all.
90947 	The target architecture is set to "auto" (currently "i386").^M
90961 	(gdb) set arch set to "auto" (currently "i386")^M
90995 	Re: objcopy renaming section with explicit flags
91003 	objcopy renaming section with explicit flags
91005 	with objcopy when renaming sections.
91054 	If the counter for LOOP instruction is provided by a register with
91066 	disassembled with -Mpower10 results in
91070 	but with -Mpower10 -Mraw
91076 	extract_pcrel0 in order to disassemble paddi with RA0=0 and R=1 as
91098 	manually with explicit additions to LDFLAGS and LIBS.
91139 	language.  But the goal is to replace all this with proper
91207 	In some situations, we can reach the end of the inferior process with
91213 	the linked list with poor performances.
91235 	GDB 10, but it started failing with GDB 11 onwards. I tracked it down to
91271 	When running the test with the latest Intel compiler:
91306 	expecting it to be included with libraries' informations, gdb.cp/typeid.exp
91349 	actually wrong with this output, so these tests were changed to test
91358 	failure when printing the type of a class with an internal typedef. This
91361 	for more info). To help with Clang testing, an XFAIL was added to this
91370 	one with a single parameter (this) and the other with 2 parameters (this
91373 	GCC's compilation makes it so either the version with 1
91374 	parameter or the one with 2 parameters is called, depending on whether
91390 	gdb/testsuite: enable running gdb.cp/classes.exp with clang
91392 	test fails to prepare with -Wnon-c-typedef-for-linkage like the
91434 	prepare with the following error:
91463 	11 or later.  The test shows no failures with this change.
91476 	The need for IsString on the PadLock insns went away with the
91521 	This option compresses output debug sections with zstd and sets ch_type
91526 	    error: --compress-debug-sections=zstd: gold is not built with zstd support
91555 	sim: v850: rename v850.dc to align with other ports
91565 	sim: igen: mark output funcs with printf attribute
91571 	To make it clear this is an input to the igen tool, rename it with an
91580 	only be used with input/output instructions.  Update i386_att_operand to
91582 	is used with non-input/output instructions.
91587 		used with non-input/output instructions.
91638 	 1. We start inferior 2 with "run&", it runs very slowly, takes time to
91662 	 - start inferior 2 with the "start" command, which also sleeps before
91688 	If the download size is known, a progress bar is displayed along with
91695 	with a ticker ("###") that moves across the screen at a rate of 1 tick
91732 	which with my ROCm GDB patch fails.  An exception is thrown and the
91736 	will be possible to unwind with subsequent patches), we want to avoid
91767 	This patch should not have user-visible changes with upstream GDB.  But
91803 	Replace the comparison with a call to frame_id_p.
91834 	`fi` gets properly filled with the cached frame id.  But when this
91941 	that it couldn't resolve the method or function, with no extra
91959 	gdb/testsuite: allowed for function_range to deal with mangled functions
91962 	patch fixes this by allowing for mangled names along with the current
91987 	systems that allow malloc overcommit) except when compiled with asan.
92025 	Tested on Ubuntu-22.04 x86_64, with and without libc6-dbg.
92192 	it.  Otherwise GDB would query the server with btrace-related packets
92202 	This patch replaces this list with a method on 'language_defn'
92208 	itself, but this doesn't work very well with the feature that disables
92217 	sim: ppc: add missing parens with e500 macro
92234 	way EXTRQ / INSERTQ would have been accepted also with kind-of-AT&T
92300 	with no core value, and the regexp in the test doesn't match (it
92338 	return an std::string, and because strtok doesn't play well with
92372 	After that, we can for instance quit with confirmation:
92383 	Or, kill with confirmation and quit:
92392 	Or, monitor exit, kill with confirmation, and quit:
92402 	But when doing monitor exit followed by quit with confirmation, we get the gdb
92486 	Continuing with signal SIGABRT.^M
92488 	Program terminated with signal SIGABRT, Aborted.^M
92530 	This hasn't been used by gdb in decades, and doesn't make sense with
92586 	The switch to linking with libtool now shows a very long link line
92624 	based on the $target.  We can easily merge this with the top-level
92629 	gdb: link executables with libtool
92649 	NOTE3: For regenerating configure I used an environment with Autoconf
92654 	       libctf.so are used by gdb if binutils is installed with
92660 	  as expected: the linked executables link with the archive or shared
92703 	  "Flags are inherited by new tracees created and "auto-attached" via
92729 	gas uses ZSTD_compressStream2 which is only available with libzstd >=
92768 	versions beginning with the version 20190608-Base-Ratified removed this
92772 	Note that, because RV32E is only used with a soft-float calling convention,
92774 	a program with -march=rv32ef -mabi=ilp32e, floating-point registers are kept
92778 	an ISA string and/or disassembling, not to allow hard-float with RVE.
92837 	not run in parallel with anything else.  When we have to link ~32 ports,
92854 	arch-specific files with an arch prefix in their name, but we can at
92862 	This matches what we do with targets already.
92959 	Patch has been tested on Power 10 with no regressions.
92998 	This patch updates file gdb.arch/powerpc-power10.exp with the new expected
93001 	with the new name.   There are no functional changes in file
93027 	with .long following the blr instruction need to be ignored.
93030 	test to ignore the lines with the .long.
93042 	Update release documentation with regard to uploading gprofng docs
93064 	Some people were seeing their builds failing with complaints about a
93081 	As with the previous commit, I don't believe we could really ever get
93100 	care of dependency tracking for us with the object files.
93149 	            * i386-opc.tbl: Rename <xy> template for VEX insn with x/y suffix to <Vxy>.
93150 		    Rename <xy> for EVEX insn with x/y suffix to <Exy>.
93213 	with -j1, the output object dir is the sim builddir itself.
93296 	gdb: Fix issue with Clang CLI macros
93353 	us harmonize paths with the top-level Makefile more easily, which
93362 	arm: PR 29739 Fix typo where ';' should not have been replaced with '@'
93365 	instances of ';' with '@' in expected diagnostics, leading to tests
93376 	add more host flags to CPPFLAGS, and that conflicts with our current
93377 	use with build-time tools.  So split them apart like we do with all
93387 	align a bit with standard C library read/write functions, and to avoid
93422 	static variables, with a 3rd drop requiring two more minor adjustments
93637 	Intel AVX IFMA instructions are marked with CpuVEX_PREFIX, which is
93639 	are encoded with EVEX prefix.  {vex} pseudo prefix will turn on VEX
93743 	prefixed with a '%'.  Here's an example of a very simple instruction
93776 	Here, the '%d' escape is used with a bitfield modifier, '%12-15d' in
93806 	   with an instruction mnemonic.  When we encounter the first '\t'
93819 	    with the correct style.  This will cover a large number of the
93820 	    operands, and is the most consistent with how styling has been
93830 	    Here are the two examples from above that use '%d', updated with
93843 	    style group, this ensures that these characters are printed with
93868 	with a ';' character, so I assumed this was the correct character to
93941 	three addresses.  However, update_watchpoints is not called again with
93949 	The following descibes the situation in detail that occurs on Power 10 with
93965 	in breakpoint.c with REPARSE set to 1.  The function update_watchpoint
94010 	update_breakpoint was called with REPARSE equal to  0.
94042 	The patch has been tested on Power 10 with no regression failures.
94068 	align a bit with standard C library read/write functions, and to avoid
94153 	gdb/testsuite: fix gdb.cp/converts.exp to run with clang
94166 	failure when printing the type of a class with an internal typedef. This
94169 	for more info). To help with Clang testing, an XFAIL was added to this
94233 	with zero arguments.  Such declarations/definitions without a prototype (an
94283 	with zero arguments.  Such declarations/definitions without a prototype (an
94288 	This commit replaces () with (void) to avoid this warning.
94317 	[gdb/testsuite] Fix gdb.server/multi-ui-errors.exp with local-remote-host-notty
94321 	(gdb) PASS: gdb.server/multi-ui-errors.exp: interact with GDB's main UI
94330 	In contrast, with local-remote-host (so, everything the same but editing off):
94332 	(gdb) PASS: gdb.server/multi-ui-errors.exp: interact with GDB's main UI
94408 	1.  If HAVE_DECL_GETOPT is defined (getopt declaration with known prototype
94411 	    The author started to define HAVE_DECL_GETOPT in sim with the commit
94413 	2.  GNU libc (2.25 or earlier)'s <unistd.h> includes <getopt.h> with a
94423 	replaces getopt with getopt_long under sim/.
94452 	Before figuring out the suppress rule of mapping symbol with architecture
94510 	RISC-V/gas: fix build with certain gcc versions
94519 	Commit 40f1a1a4564b ("RISC-V: Output mapping symbols with ISA string.")
94542 		buff with NULL to avoid build failure caused by a GCC's false
94566 	to assume GCC >= 4.6 (with "GCC diagnostic push/pop").
94575 	RISC-V: Output mapping symbols with ISA string.
94749 	[gdb/testsuite] Fix silent timeouts in gdb.mi/mi-exec-run.exp with remote host
94750 	I noticed that running test-case gdb.mi/mi-exec-run.exp with host board
94823 	(gdb) PASS: gdb.server/connect-with-no-symbol-file.exp: sysroot=: \
94825 	builtin_spawn gdbserver --once localhost:2385 /connect-with-no-symbol-file^M
94826 	/bin/bash: connect-with-no-symbol-file: Permission denied^M
94827 	/bin/bash: line 0: exec: connect-with-no-symbol-file: cannot execute: \
94829 	During startup program exited with code 126.^M
94832 	`connect-with-no-symbol-file' has disappeared; keeping its symbols.^M
94834 	(gdb) FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: \
94842 	- gdbserver start with $exec
94847 	- gdbserver start with $exec
94862 	start with $exec".
94887 	Given a fuzzed object file in an archive with section size exceeding
94908 	Fix these fails due to the target padding out sections with nops.
94921 	two fail with
94962 	with guile 3.0").
94994 	RPLHM "In a PE with the Security Extension, on taking an exception,
95015 	Test with GNU gdb (GDB) 13.0.50.20221016-git.
95187 		(som_hppa_howto_table): Update with sizes.
95213 	Fix some whitespace issues introduced with the frame_info_ptr patch.
95223 	alignment (with a short interval, from 31b4d3a ("PR28824, relro
95228 	But that means that a linker configured with --disable-separate-code
95229 	behaves different from one configured with --enable-separate-code
95232 	configuring with --disable-separate-code the linker will produce
95234 	executables for a hello world (and even 6MB when linked with
95241 	So, do away with that, make the default MAXPAGESIZE be 4k (as is default
95242 	for most x86-64 configs anyway, as most people won't configure with
95244 	"-z max-page-size" (with would have been required right now for a
95314 	("gdb/testsuite/gdb.dwarf2: Replace @ with % for ARM compatability"), so
95315 	hand-edit gdb/testsuite/gdb.arch/arm-disp-step.S to use %progbits instead.
95385 	replace the unused relocation with R_RISCV_DELETE for the deleted bytes, and
95450 	Makefile.in, this allows lm32 to build with -Werror.
95462 	with a comment and an empty statement.
95594 	For *avx512*_vpclmulqdq-wig1 share source with *avx512*_vpclmulqdq.
95605 	For *avx512*_vaes-wig1 share source with *avx512*_vaes. This in
95645 	Make sure we invoke runtest with the same exp filenames when running in
95648 	`find .` with the %p option, it produces "./aarch64/allinsn.exp".  Switch
95718 	When building GDB with clang and --enable-ubsan, I get:
95729 	I found this to happen with ld-linux on at least Arch Linux and Ubuntu
95754 	Fix incorrect .gdb_index with new DWARF scanner
95756 	scanner when the cc-with-gdb-index target board is used.
95781 	Regression tested on x86-64 using the cc-with-gdb-index board.
95797 	The new function includes a hack to avoid problems with some existing
95810 	latter, only the innermost array will end up with a stride.
95887 		* po/hu.po: Updated Hungarian translation.
95893 	`gdb.parameter' accept `None' for `unlimited' with parameters of the
95926 	when initialization with a number is attempted.  Instead assert that it
95948 	Tested on x86_64-linux, with:
95950 	- gcc 12.2.1 with static glibc not installed: UNTESTED
95951 	- gcc 12.2.1 with static glibc installed: PASS
96010 	operands to avoid vector Disp8 with VEX encoding.
96025 	calls with a more generic mechanism.
96041 	breakpoint_object_type must have been initialized with a call to
96062 	calls with a more generic mechanism.
96073 	This commit removes the first dependency issue, with this and the next
96149 	Reapply "Don't build readline/libreadline.a, when --with-system-readline is supplied"
96152 	readline/libreadline.a, when --with-system-readline is supplied").
96168 	[gdb/testsuite] Fix gdb.debuginfod/fetch_src_and_symbols.exp with check-read1
96180 	is matched using regexp "Enable debuginfod?.*" with matches only the first two
96190 	[gdb/testsuite] Fix gdb.mi/mi-disassemble.exp with check-read1
96239 	It's also been tested (and found to be working) with
96279 	commit has been tested on x86-64 linux with no regressions.
96306 	Regen ld/po/BLD-POTFILES.in
96311 	With the cc-with-tweaks.sh patch submitted here (
96313 	with:
96317 	    --target_board cc-with-gnu-debuglink"
96360 	with a perl/sed script.
96427 	terminate with the device_error call.
96439 	where commit 182421c9d2ee addressed issues with printf format
96449 	I see an uninitialized variable warning (with gcc 9.3.1) from
96470 	There should be no change in behaviour with this commit.
96482 	Update MAINTAINERS file with details about accepting DCO signed contributions.
96597 	is no situation where dropping symbol value bits with the right shift
96602 	gdb: check for groups with duplicate names in reggroups:add
96604 	groups with duplicate names.  While it did not really hurt, it certainly
96644 	The issue is the PowerPC processors support hardware watchpoints with the
96651 	Test gdb.base/watch-vfork.exp runs with can-use-hw-watchpoints set to
96652 	true and false.  When the test is run with can-use-hw-watchpoints set to
96655 	only runs once with can-use-hw-watchpoints set to false.
96657 	Test gdb.mi/mi-watch.exp runs the test with argument hw and sw.  If the
96659 	The number of expected passes is cut in half with the patch as it now only
96664 	The following tests run the same with and without the patch.  The tests
96693 	[gdb/testsuite] Handle header files with local-remote-host.exp
96694 	With test-case gdb.base/included.exp and host board local-remote-host.exp with
96711 	[gdb/testsuite] Fix gdb.server/no-thread-db.exp with local-remote-host.exp
96713 	with a tentative fix for PR29697 I run into:
96731 	[gdb/testsuite] Fix gdb.base/return-nodebug.exp with local-remote-host.exp
96749 	[gdb/testsuite] Fix gdb.server/file-transfer.exp with local-remote-host.exp
96750 	When running test-case gdb.server/file-transfer.exp with host
96778 	means the board now uses a pseudo-tty, but with editing disabled.
96816 	    be seen, for example, with gdb.base/dlmopen.exp when compiled with
96841 	where we may have multiple instances of global symbols with the same name
96852 	I stumbled over this while reviewing all objfiles traversals with regards
96897 	unlink the first objfile with the same name as the one we compiled.
96903 	This further avoids potential issues when an objfile with the same name is
96913 	to be used together with start and prev to provide the namespace of start
96957 	with one additional field:
96978 	To remain backwards compatible with older gdbserver, we reserve the
97033 	I tested this with GCC 11, 12, and 13.  I'm going to check it in.
97072 	because, although a certain symbol was present in the index, with the
97109 	Fix regression in c-linkage-name.exp with gdb index
97110 	c-linkage-name.exp started failing with the gdb-index target board due
97125 	When building with clang 15 on Ubuntu 20.04, I get:
97174 	ld/testsuite: consistently add board_ldflags when linking with GCC
97184 		linking with GCC.
97195 	And the disasembly is with the specifier with this patch.
97247 	x86: fold AVX512-VNNI disassembler entries with AVX-VNNI ones
97278 	PowerPC se_rfmci and VLE, SPE2 and LSP insns with -many
97284 	Also, VLE, SPE2 and LSP insns were not accepted by the assembler with
97285 	-many nor were SPE2 and LSP being disassembled with -Many.
97306 	So we had a zlib-gabi .debug_info section that increased in size with
97310 	uncompressed size.  So you get the zlib section again with some
97356 	[gdb/contrib] Handle STRIP_ARGS_{STRIP,KEEP}_DEBUG in cc-with-tweaks.sh
97358 	--strip-debug in gdb/contrib/cc-with-tweaks.sh, such that we can easily
97363 	    --target_board cc-with-gnu-debuglink"
97370 	Script checked with shellcheck, no new warnings added.
97404 	[gdb/testsuite] Fix gdb.server/unittest.exp with host board local-remote-host.exp
97518 	so let's go with that for now.
97555 	Example session with this patch:
97592 	with get_powerpc_dialect.  I don't think there is.  Decoding of a VLE
97595 	section with SHF_PPC_VLE for decoding when disassembling.
97608 	e200z2 cpu entry with LSP support, removing LSP from -me200z4 and from
97622 		* testsuite/gas/ppc/lsp-checks.d: Assemble with -me200z2.
97677 	[gdb/testsuite] Fix gdb.base/infoline-reloc-main-from-zero.exp with PIE
97686 	When running with native, I find that the executable is static:
97690 	  version 1 (SYSV), statically linked, BuildID[sha1]=$hex, with debug_info, \
97693 	despite not having been compiled with -static.
97701 	[gdb/testsuite] Fix gdb.base/infoline-reloc-main-from-zero.exp with clang
97726 	[gdb/testsuite] Fix nopie test-cases with target board unix/-fPIE/-pie
97729 	In order to test PIE executables with a compiler that produces non-PIE by
97733 	Likewise, we can use target board unix/-fno-PIE/-no-pie with a compiler that
97738 	gdb_compile_shlib to compile with -fPIC.  This is taken care of by running the
97741 	The target board unix/-fPIE/-pie has a problem with nopie compilations.  The
97744 	out with the standard error message "nopie failed to prevent PIE executable".
97750 	  used when making a PIE object; recompile with -fPIE^M
97779 	with the shorter:
97802 	RISC-V: Imply 'Zicsr' from privileged extensions with CSRs
97803 	'H', 'Smstateen', 'Sscofpmf' and 'Sstc' are four privileged extensions with
97804 	their CSR definitions and 'Smepmp' is a privileged extension with additional
97861 	This commit replaces uses of int with bool whenever possible.
97872 	opcodes/riscv-dis.c: Tidying with spacing
97880 		* riscv-dis.c (riscv_disassemble_insn): Tidying with spacing.
97884 	opcodes/riscv-dis.c: Tidying with comments/clarity
97959 	The PowerPC processors support hardware watchpoints with the
97965 	with the skip_hw_watchpoint_tests_p check.  With the patch, the test runs
97966 	on Power 9 with hardware watchpoint force-disabled.  The test runs on
97967 	all other PowerPC processors with and without hardware watchpoints
97970 	The patch has been tested on Power 9 to verify the test only runs with
97971 	hardware breakpoints disabled.  The patch has been tested on X86-64 with
97978 	[gdb/testsuite] Fix gdb.dwarf2/macro-source-path.exp with -m32
97998 	("[gdb/testsuite] Fix 64-bit dwarf test-cases with -m32") for for instance
98003 	Tested on x86_64-linux with native and target board unix/-m32.
98007 	[gdb/testsuite] Fix gdb.dwarf2/entry-value-typedef.exp with -m32
98031 	[gdb/testsuite] Fix gdb.mi/mi-disassemble.exp with -m32
98043 	The test-case passes with native.
98047 	Longest instruction at 0x0000000000400549 with bytes '48 8b 05 20 01 00 00'
98054 	But with unix/-m32 we have longest_insn_byte:
98056 	Longest instruction at 0x08048481 with bytes '8d 4c 24 04        '
98065 	Fix this by stripping the whitespace, which makes us end up with a different
98068 	Longest instruction at 0x08048492 with bytes 'dd 05 98 85 04 08'
98071 	Tested on x86_64-linux, with native and target board unix/-m32.
98086 	The PowerPC processors support hardware watchpoints with the
98092 	with the skip_hw_watchpoint_tests_p check.  With the patch, the test is
98095 	The patch has been tested on Power 9, Power 10 and X86-64 with no
98114 	When running test-case gdb.base/ctf-constvars.exp on openSUSE Tumbleweed (with
98142 	When running test-case gdb.base/gdbindex-stabs.exp on openSUSE Tumbleweed (with
98154 	[gdb/testsuite] Replace remaining -gt with -gctf
98163 	additional_flags=-gt with additional_flags=-gctf in gdb.ctf/*.exp and
98172 	[gdb/testsuite] Fix gdb.base/infoline-reloc-main-from-zero.exp with recent ld
98173 	On openSUSE Tumbleweed (with ld 2.39) and test-case
98177 	  segment with RWX permissions
98182 	Fix this by compiling with -Wl,--no-warn-rwx-segments.
98188 	[gdb/testsuite] Fix gdb.base/nested-subp{2,3}.exp with recent ld
98189 	On openSUSE Tumbleweed (with ld 2.39) I get for test-case
98196 	Fix this by compiling with -Wl,--no-warn-execstack.
98232 	implementation-defined manner, the result with format string containing
98237 	This commit replaces "0x%p" with "%p" to prevent unpredictable behavior.
98243 	simulator with ATTRIBUTE_PRINTF, there were some build failures in the
98244 	ppc sim due, in some cases, to bugs with the arguments being passed,
98245 	and in other cases, the issues were (maybe) less serious, with
98255 	as it does currently, which is my goal with this commit.
98259 	[gdb/contrib] Use OBJCOPY everywhere in cc-with-tweaks.sh
98260 	I noticed that the $want_gnu_debuglink code in gdb/contrib/cc-with-tweaks.sh
98263 	Script checked with shellcheck, no new warnings added.
98305 	In summary, when loading an AArch64 core file with MTE support by
98311 	    Program terminated with signal SIGSEGV, Segmentation fault
98322 	    Program terminated with signal SIGSEGV, Segmentation fault.
98326 	The problem with the latter is that auxv data gets improperly cached
98426 	   the passed-in target and call the linux_get_hwcap{,2} function with
98441 	[gdb/testsuite] Fix gdb.debuginfod/fetch_src_and_symbols.exp with native-gdbserver
98442 	When running test-case gdb.debuginfod/fetch_src_and_symbols.exp with target
98458 	Fix this by replacing gdb_test "start" with runto_main.
98487 	with zero arguments.  Such declarations/definitions without a prototype (an
98496 	In really old environments, this getopt definition with no arguments is
98519 	message and pass the message to sim_engine_abort function with another
98753 	The problem is easy to spot with an example.  First consider:
98774 	because the gdb_test_multiple is called with an empty message argument.
98826 	It can be reliably reproduced on a recent enough GNU/Linux with this
98841 	"recent enough" means a system where libpthread.so was merged with
98862 	pattern that ends with "$gdb_prompt", but not a trailing $.  I think
98885 	escapes, and gdb always prints these with "%.3o".  Second, though,
98924 	The frame_info_ptr patches broke the build with Guile.  This patch
98927 	lifetime did not interact with Guile's longjmp-based exception scheme.
98941 	[gdb/testsuite] Fix error message for cmd with trailing newline
98975 	replaced with the base address for where the in-memory symbol file was
99080 	As for performance concerns, my personal testing with `time make
99084 	This commit also adds a testcase that exercises the python/28856 bug with
99098 	The substitution was done with multiple sequential `sed` commands:
99129 	This replaces frame_id_eq with operator== and operator!=.  I wrote
99160 	To merge with gcc's copy of configure.ac we need to revert changes to
99191 	[gdb/testsuite] Fix silent fail in gdb.server/connect-with-no-symbol-file.exp
99193 	remote-stdio-gdbserver I have for gdb.server/connect-with-no-symbol-file.exp:
99197 	but with native-extended-gdbserver I have instead:
99208 	(gdb) FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: \
99244 	On ubuntu 22.04 with the libc6-dbg package installed, I have the
99254 	The regex for this test accounts for different situations (with /
99261 	Tested on Ubuntu-22.04 x86_64 with and without libc6-dbg debug symbols
99269 	When running test-case gdb.server/abspath.exp with host board
99299 	When running test-case gdb.base/default.exp with target board
99307 	Tested on x86_64-linux with native and target board native-gdbserver.
99311 	[gdb/testsuite] Fix have_mpx with remote-gdbserver-on-localhost
99329 	which does match the captured output with native:
99337 	Tested on x86_64-linux, with native and target board
99342 	[gdb/testsuite] Fix DUPLICATEs with remote-gdbserver-on-localhost
99343 	Fix some DUPLICATEs that we run into with target board
99346 	Tested on x86_64-linux, with native and target board
99352 	When running test-case gdb.server/solib-list.exp with target board
99369 	Tested on x86_64-linux, with native and target boards
99382 	This patch tidies pe_bfd_object_p with the above in mind, and
99409 	with FPCAR to identify if lazy FPU state preservation is active for
99413 	Cortex-M cores with FPU.
99487 	This commit prints "Xl(...)" operand with dis_style_immediate style,
99501 	1.  A signed type must be specified when printing with %i.
99515 	printed with another word with another style.
99518 	with the "text" style.
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.
99593 	Fuzzed input with this in .debug_line
99607 		sections with no contents.
99611 	gprofng: fix build with --enable-pgo-build=lto
99687 	The complaints are about foo, with DW_AT_inline == DW_INL_inlined:
99695 	and foo2, with DW_AT_inline == DW_INL_declared_inlined:
99793 		* elf.c (elf_fake_sections): Replace "." with ".z" in debug
99804 	debug info in sections starting with .gnu.debuglto_ prefix and are
99809 	are compressed with zlib:
99834 	RISC-V/gas: allow generating up to 176-bit instructions with .insn
99845 	It's fully redundant with the subset_list member of riscv_rps_as.
99854 	ignore DWARF debug information for -gsplit-dwarf with dwarf-5
99899 	When using AArch64 GDB with the QEMU debugging stub (in user mode), we get
99938 	Improve GDB's baseclass detection with typedefs
100030 	the make command did exit with an error, but DejaGnu appeared to
100058 	In my case, with the invalid test name, DejaGnu fails, but the
100078 	      sum-file       A test summary file with the format of those
100092 	      sum-file       A test summary file with the format of those
100143 	gdb/disasm: better intel flavour disassembly styling with Pygments
100163 	underlined, and could be confused with a combined +/- symbol.
100210 	treats '#' as an error, which means, with the addition of the
100217 	looks for an Error token with the value '#', we then change this into
100242 	correctly (with no underline).  The existing style tests check that
100250 	Clearly, the 'asm' lexer is OK with att style x86-64, but not OK with
100263 	This is combined with the fact that many architectures are now moving
100296 	recreate the buffer with styling support.
100298 	The problem is that we should only recreate the buffer with styling
100390 	them with a return of the empty string.
100433 	interact with one copy of the register.
100510 	compliance with the API I set out here, but I believe that most are.
100512 	I think architectures that don't comply with the API laid out here
100515 	The claims in the comment are I feel, best demonstrated with the
100536 	Subsequent commits will fix all targets to be in compliance with this
100641 	There is one slight oddity with the current implementation, which I
100665 	example above we now return 'output here' with no '\r'.
100703 	The two new options are only valid for mode 0, if they are used with
100706 	The --opcodes option can add opcodes to the result, with 'bytes' being
100769 	things start to get confusing with the original syntax.
100866 	behaviour or /r.  I could have added /b with the new behaviour and
100887 	gdb/disasm: read opcodes bytes with a single read_code call
100892 	gdb_pretty_print_disassembler class, in line with all the other
100894 	then resized as needed, and filled with a single read_code call for
100958 		Add tests for instruction with rounding mode.  Change march
100981 	which is undefined when combined with passing an address of the accessed
100984 	triggering compiler diagnostics (which are fatal with -Werror).
100988 	triggers a "shadows a global declaration" warning with some gcc versions.
100992 	presently they aren't. This fixes disassembly of these insns with
101001 	with the same name needing to stay next to each other.
101057 	IgnoreSize needs to remain on legacy encoded SIMD insns with GPR
101065 	and Q suffixes there, despite the inconsistency with VCVT{,T}S{S,D}2SI.
101166 	for ppc64le"), the test-case fails with target board cc-with-debug-names, due
101191 	and with clang++ (13.0.1):
101266 	architecture vector."), I think that the name prefixed with target is a
101310 	with a rawhide scratch build containing this patch.]
101399 	with array-indexes enabled.  This turned out to be caused by the array
101416 	ld/testsuite: force warnings when dealing with execstack tests
101433 		* embedspu.sh: Replace multi-line grep with sed.
101435 		* testsuite/ld-elfvers/vers.exp: Replace multi-line grep with sed.
101469 	flag may not be available with older versions of grep.
101472 	it with the autoconf $EGREP or with grep.
101480 		* embedspu.sh: Replace egrep with grep.
101483 		Replace egrep with grep.
101485 		* testsuite/bnd_ifunc_1.sh: Replace egrep with $EGREP.
101502 		* testsuite/ld-elfvers/vers.exp (test_ar): Replace egrep with grep.
101511 	The segv was on "info->strs[strsize - 1] = 0;" with strsize zero.  OK,
101558 	PR29397 PR29563: Add new configure option --with-zstd which defaults to
101559 	auto.  If pkgconfig/libzstd.pc is found, define HAVE_ZSTD and support
101576 …ld/ld-new: a.o: section .debug_abbrev is compressed with zstd, but BFD is not built with zstd supp…
101580 	ld/ld-new: --compress-debug-sections=zstd: ld is not built with zstd support
101583 	binutils/objcopy: --compress-debug-sections=zstd: binutils is not built with zstd support
101586 …binutils/objcopy: zstd.o: section .debug_abbrev is compressed with zstd, but BFD is not built with…
101646 	Since debugging GDB with GDB is (unfortunately) a bit slow, bump the
101681 	[gdb/testsuite] Fix gdb.dwarf2/dw2-unspecified-type-foo.c with -m32
101682 	When running test-case gdb.dwarf2/dw2-unspecified-type-foo.c with target board
101755 	with std::string::back, which results in undefined behaviour. A typical
101790 	The problem with warning in elf_object_p
101793 	and "program header with invalid alignment".  The problem with doing
101796 	object file with 6144 program headers, 5316 of which had invalid
101817 	bfd_target with a writable field.  I've made per_xvec_warn one larger
101869 	gdb/testsuite/tui: start GDB with "set filename-display basename"
101880 	with a name similar to the one shown above.
101893 	When running gdb.tui/tui-missing-src.exp in a directory with a shorter
101929 	window gets redrawn with the contents of the f2.c file.  Then, GDB
101992 	completion of the "step" command.  The subsequent tests now run with a
102076 	On systems with dejagnu-1.6.3, if GDB's overrides is needed to support
102088 	    gdb compile failed, default_target_compile: No compiler to compile with
102090 	    gdb compile failed, default_target_compile: No compiler to compile with
102092 	    gdb compile failed, default_target_compile: No compiler to compile with
102095 	We are observing this error with ROCgdb[2], a downstream port of GDB
102105 	Using board files provided with dejagnu <=1.6.2 is still supported: if
102237 	encoding formats. The formats have the form "XsN@S" and "XuN@S" with N
102303 	* Introduce a section with a table in the documentation where vendor
102353 	the code is auto-generated and we have no ways to deal with it.
102409 	names with spaces in would mean we'd need to audit all the places a
102421 	a window name with '-'?  We already support a '-horizontal' option,
102434 	with the addition of this change, but hopefully adapting to the new
102445 	this from other tests and have them working with clang.
102487 	a different location, it registers as a failure.  Seeing as along with
102526 	fix gdb.base/jit-elf.exp when testing with clang
102529 	inferior was only showing up as with a relative path, like so:
102569 	gdb/testsuite: fix gdb.base/msym-bp-shl when running with Clang
102576 	gdb/testsuite: fix testing gdb.base/skip-inline.exp with clang
102591 	Change gdb.base/skip-solib.exp deal with lack of epilogue information
102592 	When running gdb.base/skip-solib.exp, the backtrace tests could fail with
102593 	compilers that associated epilogue instructions with the last statement
102594 	line of the function, instead of associating it with the closing brace,
102633 	by the testsuite in tmpdir/ld will point to nothing. Thus, even with the
102640 		* testsuite/config/default.exp: Allow to change -B flag with
102674 		     enough to implement a new instruction with this operand type.
102684 	On such cases, we should vacate this room for the new operand type with
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).
102773 	Rename it fileio_error_to_host, for symmetry with host_to_fileio_error.
102790 	remote side replies with an error and omits the errno value, we'll get
102794 	behavior (there is no intended change in behavior with this patch).
102798 	with a nonsensical value here.  It's not good, but out of the scope of
102823 	When a GDB built with -D_GLIBCXX_DEBUG=1 reads a binary with a single
102827 …pe& std::basic_string_view<_CharT, _Traits>::operator[](size_type) const [with _CharT = char; _Tra…
102875 	Remove the macro, replace all uses with calls to type::length.
102912 	This is because "()" possibly means a function prototype with indeterminate
102955 	file symbols, but that comes with its own set of problems:
103001 	problem of relocatable object files with the fix for PR2338, so this
103108 		(alpha_vms_write_exec): Exclude sections with contents NULL due
103148 	retained the copyright date range on the new library), with some minor
103208 	sections, we cannot access something in b with "a->contents + (offset
103232 	I see this error when building with clang,
103242 	Tested on x86_64-linux with gcc 12 and clang 14.
103260 	(gdb) FAIL: gdb.dwarf2/dw2-no-code-cu.exp: p var with no complaints
103263 	This is a regression since commit 6d263fe46e0 ("Avoid bad breakpoints with
103271 	The change intends to avoid a problem with a check in
103331 	command, could be added to print out each message along with the
103356 	Tested on x86_64-linux, with gcc 7.5.0 and clang 13.0.
103363 	On a powerpc system with gcc 12 built to default to 128-bit IEEE long double,
103389 	When running the test-case gdb.dwarf2/dw2-dir-file-name.exp with
103413 	In contrast, for x86_64-linux, we have the breakpoint printed with instruction
103471 	The fix is only available for readline 8.x, if --with-system-readline provides
103483 	be loaded directly with pla, the following:
103525 	thereafter) variables.  By the default configuration (with "-Werror"), it
103592 	Binutils: Readelf testcase failing with clang
103600 	fuzzers to create an archive with mach_o_fat_archentry headers that
103604 	will get stuck.  This patch rejects such archives, and any with
103617 	bfd: Stop using -Wstack-usage=262144 when built with Clang
103634 		compiled with Clang.
103666 		* testsuite/ld-ctf/diag-ctf-version-0.s: Replace @progbits with
103705 	We are way off in the weeds with this one, and will be printing
103756 	generically deal with unknown number of steps until leaving that
103800 	Resubmitted with changes in
103896 	that could be replaced with checked_static_cast.  This patch is the
103922 	add xfails to gdb.base/complex-parts.exp when testing with clang
103930 	Fix gdb.base/call-ar-st to work with Clang
103945 	The difference is that with Clang we get:
103975 	update gdb.base/info-program.exp to not fail with clang
103980 	patch the test works even with clang.
103984 	gdb/testsuite: change gdb.base/nodebug.exp to not fail with clang
104035 	(while the previous implementation was done with a linked list,
104038 	When linking object files with excluded symbols, there can potentially
104039 	be very large numbers of excluded symbols (just like builds with
104042 	This improves the link performance somewhat, when linking with large
104050 	[gdb] Fix abort in selftest run_on_main_thread with ^C
104100 	[gdb/symtab] Support .gdb_index section with TUs in .debug_info
104102 	.debug_names section with TUs in .debug_info").
104131 	[gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp with clang
104132 	When running test-case gdb.dwarf2/dw2-dir-file-name.exp with clang, we run
104148 	to cause problem with clang, as documented in the comment for proc
104153 	Tested on x86_64-linux, with both gcc 7.5.0 and clang 13.0.0.
104161 	performance gain in my testing (with debug builds of objdump, libbfd,
104188 	riscv: Fix incorrect jal with HIDDEN_JUMPTARGET
104192 …setjmp' which may bind externally can not be used when making a shared object; recompile with -fPIC
104193 … `exit' which may bind externally can not be used when making a shared object; recompile with -fPIC
104257 	Re: PR29466, APP/NO_APP with linefile
104269 	Support debuginfo files with empty group sections.
104307 	This test generates 48 failures on Power 9 when testing with HW watchpoints
104313 	with the skip_hw_watchpoint_tests check.
104315 	This patch was tested on Power 9, Power 10 and X86-64 with no regressions.
104346 	It also regenerates corresponding files with the maintainer mode.
104372 	On aarch64-linux, with gcc 7.5.0, we run into:
104489 	little-endian by default, so running this test with a GDB built with
104503 	read. This way we avoid having to deal with the endianness conversion, and use
104586 	bfd_find_nearest_line_with_alt functions like bfd_find_nearest_line with
104607 	This is paired with "opcodes: Add non-enum disassembler options".
104644 	[gdb/symtab] Support .debug_names section with TUs in .debug_info
104646 	cc-with-debug-names/gdb:debug_flags=-gdwarf-5, we get an executable with
104691 	to specify a .debug_names index with the TU list referring to a TU from the
104705 	This is paired with "gdb: Add non-enum disassembler options".
104752 	sim/riscv: Complete tidying up with SBREAK
104766 	sim/erc32: fix gdb with simulator build
104777 	Unfortunately, these changes broke building GDB with the erc32 (sparc)
104818 	definition issues with this function.  The functions themselves are
104862 	output so that section symbols without a name as shown with their
104933 	RISC-V: Add address printer tests with ADDIW
104942 		computation with sign extension as used in ADDIW/C.ADDIW.
104975 		* dllwrap.c: Replace uses of choose_temp_base() with
104989 	When running the gdb/configure script on ubuntu 22.04 with
105041 	Fix "source" with interpreter-exec
105066 	can be removed -- with the exception of the assignment to gdb_stdtarg,
105107 	not be registered with the event loop.  This is useful for the DAP
105235 	registers, $fflags, $frm, and $fcsr, with the last of these being the
105278 	Next, I spotted that the text that goes along with the 'FRM' field was
105322 	slight oddity with this test - for the fflags and frm registers, the
105353 	   entry with the tag DW_TAG_template_type_parameter.  A template value
105354 	   parameter is represented by a debugging information entry with the tag
105379 	'<unnamedNUMBER>' where NUMBER is its position.  This way we end up with
105398 	The forward declaration for 'Foo' with the missing template type names
105429 	  type = class Foo<double, int, float> [with B = int] {
105433 	After this patch GDB does generate symbols from the DWARF (with their
105437 	  type = class Foo<double, int, float> [with <unnamed0> = double, B = int,
105445 	not emit a '[with...]' list and their name generation also does not
105461 	However, the macro failed as GDB prints the C++ 'main' with its
105482 	which is legal in both languages, C and C++, and compiling it with
105506 	Note, that main is emitted with its arguments while for foo the linkage
105552 	To make the macro and proc work with C++ as well, an optional argument
105565 	In some cases original_name is prefixed with gdb's working directory
105577 	ld: pe: Fix linking against Microsoft import libraries with multiple DLLs
105586 	(in 2003) to allow for Microsoft import libraries with intermixed
105590 	allow members with any name if it precedes the first one named *.dll.)
105603 	intermixed with other static object files (regardless of their
105607 	seem to bundle up multiple import libraries together with some
105609 	them with ld.bfd.
105614 	When building with Clang 14 (using gcc 12 libstdc++ headers), I get:
105642 	to remove the wrapper in the future, just replace gdb:: with std::.
105644 	Tested by building with gcc 12 in -std=c++11 and -std=c++17 mode, and
105645 	clang in -std=c++17 mode (I did not test fully with clang in -std=c++11
105737 		(RV32 + Zmmul but with no M).
105740 		(RV64 + Zmmul but with no M).
105883 	gdbsupport: fix gdb::optional compilation with C++11 && _GLIBCXX_DEBUG
105884 	Similar to 911438f9f4 ("gdbsupport: fix array-view compilation with
105887 	I get this error when building with Clang 14 and -std=c++11:
105914 	gdb, gdbsupport: configure: factor out yes/no/auto value checking
105915 	Factor out the code that checks that a value is yes/no or yes/no/auto.
105956 	However, GDB alias command allows to define aliases with arguments
105962 	nested 'with' followed by a last command to launch, such as:
105963 	  (gdb) alias pp10 = with print pretty -- with print elements 10 -- print
105964 	Asking 'help pp10' shows the help of the 'with' command, which is
105967 	  with, pp10, w
105968 	    alias pp10 = with print pretty -- with print elements 10 -- print
105970 	  Usage: with SETTING [VALUE] [-- COMMAND]
105980 	    alias pp10 = with print pretty -- with print elements 10 -- print
105993 	indicating that pp10 is an alias of the 'with' command is confusing.
105998 	Noticed while doing mass builds with a very recent GCC:
106006 …cpustate.h:310:20: note: previous declaration of 'aarch64_get_CPSR_bits' with type 'uint32_t(sim_c…
106029 	will silently generate executable with incorrect run-time behavior on
106082 	Don't overload bfd_reloc_outofrange with what is really a domain error
106102 	PR10372, SH: ld test with sim/sh/run fails always
106123 	with libraries that may contain members with uppercase file names, we
106127 	Also make the check for .def consistent with the other ones, fixing
106134 	target-specific directives did not correctly handle lines with
106166 	  when linking a undefined function with cmodel=medium.
106184 	symbol table with sh_link.  SHT_RELR relocations don't use symbols.
106252 	Avoid crash with Ravenscar tasks
106378 	gdb/testsuite: re-compile entry-value-typedef .S files with -fPIE
106384 …XX_3.4' which may bind externally can not be used when making a shared object; recompile with -fPIC
106391 	same system as the original one, but with -fPIE this time.  Do the same
106414 	This patch disables those warnings with -Wno-deprecated-non-prototype.
106423 	options to disable some warning.  That is OK with GCC, because
106514 	dwarf_expr_context::fetch_result with a typedef type that has never been
106518 	As a fallback, I made a gdb.dwarf2 test with compiler-generated .S
106539 	included with the original aarch64 port.  It might've been an oversight.
106551 	linked list with a vector and removing some ALL_* iterator macros.
106606 	with the previous gdbarch.  This patch makes it do that.
106632 	This timeout cannot be implemented externally with a gdb timer, because
106637 	with a 0 timeout quite often.
106684 		unexpected, fill out section with zeros.
106690 	call with a read error but on subsequent calls too.
106736 	___lc_codepage_func to allow a sucessful build with MinGW-w64.
106742 	due to additional styling characters.  Each style is encoded with 3
106758 		(obuf): Replace 100 with MAX_OPERAND_BUFFER_SIZE.
106839 	1) Replaces some macros with inline functions.
106870 	Many of the vector conversion insns come with X/Y/Z suffixed forms, for
106917 	  insns with multiple forms (i.e. the same Cpu64 attributes on {,V}MOVQ,
106933 	eliminate an unhelpful (lost information) diagnostic combined with a use
106990 	with uninitialised garbage.
107087 	This replaces dwarf_vma, dwarf_size_type and dwarf_signed_vma with
107089 	DWARF_VMA_FMT since we can't use that with uint64_t, and all of the
107091 	dwarf_vmatoa also disappears, replacing most uses with one of
107100 	This replaces bfd_vma with uint64_t in readelf, defines BFD64
107105 	Replacing bfd_size_type with dwarf_size_type or uint64_t is mostly
107110 	Replace elf_vma with uint64_t
107111 	This patch replaces all uses of elf_vma with uint64_t, removes
107161 	the address does not fall at an actual line, so the breakpoint is shown with
107164 	when running the test-case with aarch64-linux, we have similarly:
107211 	of varobj_invalidate" to deal with use a after free issue.  However
107278 	misnamed since they deal with re-creating invalid objects and do not do
107356 	PR29466, APP/NO_APP with .linefile
107368 	fail of gas/testsuite/macros/dot with an extra warning: "end of file
107398 	The "script" field, output whenever information about a breakpoint with
107516 	local syms with plt entries were local ifunc symbols.  There shouldn't
107524 		not used with inline plt sequences against local symbols, only
107540 	However this target is not valid for use with gas but only with objcopy.
107641 	to the above commit printing with /x and /d would first extract the
107761 	replaces 0 with RISCV_ZERO_REGNUM and 32 with RISCV_PC_REGNUM in a few
107787 	x86: allow use of broadcast with X/Y/Z-suffixed AVX512-FP16 insns
107831 	I managed to reproduce the bug with a riscv-elf build and then
107840 	dissably call with source code involved. E.g.
107870 	The following scan can be replaced with search in a splay tree and with
107949 		string literals within with gettext macro.
107988 	[gdb/build] Fix build with gcc 4.8.5
107989 	When building with gcc 4.8.5, I run into:
108053 	- compiling with -nostartfiles (so the test-case contains _start rather than
108096 		* coffgen.c (build_debug_section): Terminate the section with
108110 	Catches fuzzed input with unterminated strings that later run off the
108116 		strings with one extra byte.
108167 	Like commit b82817674f, this replaces BFD_VMA_FMT "x" in sim/ with
108174 	[gdb/build] Fix build breaker in language.c with gcc 7.5.0
108255 	and with the patch:
108282 	and with the patch:
108311 	    auto lambda = [&] (int) { ... };
108312 	    auto fv = gdb::make_function_view (lambda);
108316 	    auto lambda = [&] (int) { ... };
108319 	It is particularly useful if you have a template function with an
108329 	    auto lambda = [&] (int) { ... };
108334 	    auto lambda = [&] (int) { ... };
108339 	Tested by building with GCC 9.4, Clang 10, and GCC 4.8.5, on x86_64
108351 	Fuzzed input files with sizes of .dynamic not a multiple of dynamic
108352 	tag size can result in reading past the end of the buffer with the
108392 	Using SHF_LINK_ORDER (with possibly sh_link == 0) is an idea by Jan Beulich.
108402 	When gas/read.c calls mbstowcs with a NULL destination, it should set size to 0
108505 	this changes with the gdbarch change.  This patch arranges to let the
108629 	spaces to line up output due to the original %V printing hex vmas with
108649 		with printing to a buffer in order to properly format output.
108742 	When building with clang 15, I got this,
108759 	Tested by rebuilding on x86_64-linux with clang 15 and gcc 12.
108805 	  variants with it being other than None.
108850 	absolute values), a symbol table (with just the first placeholder entry)
108905 	   seen accessed with an initial exec access sequence.
108910 	tests are now only available on targets with that.
108928 	We get this warning when testing aarch64-none-elf with -mcmodel=tiny.
108936 	This is done particularly with CFI directives in mind, allowing for
108958 	comply with register ordering on push statements, being that registers
108959 	are stored on the stack in numerical order, with the lowest numbered
108972 	as was the case with previous implementation, now produces:
109017 	ld: Support the -exclude-symbols option via COFF def files, with the EXCLUDE_SYMBOLS keyword
109043 	- replacing the current implementation of the warning with an
109054 	x86: SKINIT with operand needs IgnoreSize
109085 	Replace them in most cases with code that prints a bfd_vma using
109118 		* od-macho.c: Replace all uses of printf_vma with bfd_printf_vma.
109161 		uses of sprintf_vma with bfd_sprintf_vma.
109176 	There is a problem with my commit 0e3c1eebb2, which replaced
109177 	bfd_uint64_t with uint64_t: Some hosts typedef int64_t to long long
109207 	[gdb/testsuite] Fix gdb.ada/literals.exp with aarch64
109324 	with:
109329 	and DWARF v2 line table with:
109338 	Because the main symtab was created with only DW_AT_name, it was named
109451 	the main subfile has no symbols but there exists another subfile with
109454 	subfile with that other subfile.  I think that heuristic is useful as a
109469 	path.  In theory, we should end up with the same path in all cases.
109544 …[symtab-create] start_subfile: found existing symtab with name_for_id /home/simark/build/binutils-…
109547 	As we can see, there are two forms used for "test.c", one with a "." and
109568 	Similarly, with DWARF 5:
109639 	generate a DW_AT_name with a full path ("/dir/d/dw2-compdir-oldgcc42.S")
109640 	and no DW_AT_comp_dir.  The line table has one entry with filename
109659 	Prior to my patch, a subfile would get created with filename
109661 	created with filename "dw2-compdir-oldgcc42.S" from the line table's
109668 …[symtab-create] start_subfile: found existing symtab with name dw2-compdir-oldgcc42.S (dw2-compdir…
109676 	start a subfile with the same filename_for_id, and there was no need for
109681 …[symtab-create] start_subfile: found existing symtab with name_for_id /dir/d/dw2-compdir-oldgcc42.…
109683 …[symtab-create] start_subfile: found existing symtab with name_for_id /dir/d/dw2-compdir-oldgcc42.…
109685 	But since the one with name == "/dir/d/dw2-compdir-oldgcc42.S", coming
109687 	with "/dir/d/dw2-compdir-oldgcc42.S" as the name, "info source" shows
109694 	least with GCC) "/an/absolute/path.c" and GDB tells you that the source
109696 	behavior fairly easily with a little change in find_file_and_directory.
109698 	modify the name to just keep the file part.  The result is coherent with
109772 	[gdb/testsuite] Fix gdb.ada/convvar_comp.exp with broken debug info
109773 	On aarch64-linux I run into this failure with gcc 7.5.0:
109797 	Re: PR16005, avr linker crash on a particular instruction sequence with --relax
109837 	multiple operands separated with a ','.
109855 	callback returns a string with special embedded markers that indicate
109897 	PR16005, avr linker crash on a particular instruction sequence with --relax
109898 	It's possible for relax_delete_bytes to be called with section
109953 		[...] has a LOAD segment with RWX permissions
109982 	Program terminated with signal SIGKILL, Killed.^M
110034 	with relatively ordinary template classes.  The result is less code
110035 	than the previous setup.  It replaces large macros with a relatively
110038 	The existing type-safe "key" class is replaced with the equivalent
110047 	The old "save/free" two-phase process is removed, and replaced with a
110111 	impossible with the safe call.
110125 	as per request by Pedro with the argument that it more resembles the
110141 	- Replaced manual INCREF/DECREF calls with
110215 	with runtime overhead when the Python user wants to use them.
110326 	back to writing to inferior memory with ptrace if /proc/pid/mem _is_
110364 	[gdb/testsuite] Fix gdb.opt/inline-small-func.exp with clang
110365 	When running test-case gdb.opt/inline-small-func.exp with clang 12.0.1, I run
110370 	clang-12.0: error: linker command failed with exit code 1 \
110381 	PowerPC32 ld test fails with --enable-targets=all
110392 		* testsuite/ld-powerpc/tlsexe32.r: Pass with .data section present.
110494 	fine.  Note that the above commit compiles just fine with later
110502 	with g++ 4.8.
110561 	command) or after the shared library is unloaded (with a call to dlclose
110583 	to initialize the python context with default gdbarch and language_defn
110601 	That is currently not possible with MI's mi_runto, however.  This
110606 	breakpoint with a location, so the regexp returned by
110679 	is "auto".  Simon noticed that GDB's implementation doesn't
110720 	had compiled GDB with the undefined behaviour sanitizer, GDB crashed
110735 	was spotted when GDB was built with the undefined behaviour sanitizer,
110762 	ld: Compile 2 CTF tests with -O2
110763 	When GCC 12 is used to build binutils with -O0, the following 2 tests
110766 	FAIL: Conflicted data syms, partially indexed, stripped, with variables
110769 	Compile 2 tests with -O2 to avoid test failures.
110772 		* testsuite/ld-ctf/data-func-conflicted-vars.d: Compile with -O2.
110781 	I ran the testsuite on x86_64 GNU/Linux with this implementation
110812 …../gdbsupport/packed.h: In instantiation of 'packed<T, Bytes>::packed(T) [with T = dwarf_unit_type…
110842 	          whitespace = space-before-tab,indent-with-non-tab,trailing-space
110870 	issues any time you edit a line.  For GDB we're usually pretty good,
110877 	gdb/arm: Sync sp with other *sp registers
110878 	For Arm Cortex-M33 with security extensions, there are 4 different
110883 	With this patch, sp will always be in sync with one of the real stack
110892 	switch statements with regular if-else if statements
111087 	  opcodes: Replace old insns with news and generate new relocate types
111119 	order, with .got before .plt in the section headers but .got is laid
111125 	and does cope with a missing bfd section by returning zero for its
111132 		with alignment larger than 8 bytes.
111176 	When running test-case gdb.cp/cpexprs-debug-types.exp with target board
111177 	cc-with-debug-names on a system with gcc 12.1.1 (defaulting to dwarf 5), I
111194 	elements in all_comp_units, so we end up with duplicates in all_comp_units,
111211 	Some Ada tests repeat their test sequence with different gnat-encodings,
111215 	manually with the test artifacts.  Change those tests to use unique
111232 	Add a unit test that verifies that we can call gdb::parallel_for_each with an
111310 		* testsuite/ld-i386/pr27998a.d: Replace -shared with -e bar.
111314 		* testsuite/ld-ifunc/ifunc-2-i386.s: Replace @GOTOFF with @GOT.
111379 	  The target architecture is set to "auto" (currently "i386").
111383 	  The target architecture is set to "auto" (currently "riscv:rv32").
111394 	When we "run", GDB does a fork & exec, with the inferior being
111467 	Consider a GDB session with multiple inferiors.  One inferior might be
111554 	  Zeroing of upper 32 bits of 64-bit addresses is auto.
111591 	    Zeroing of upper 32 bits of 64-bit addresses is "auto" (current architecture is not MIPS).
111601 	  Zeroing of upper 32 bits of 64-bit addresses is "auto" (currently "off").
111617 	The problem with the current code is that the functions in question
111655 	with the ARM_SP_REGNUM case being handled separately.
111662 	Tested by running the selftest on x86_64-linux with python 3.11.
111666 	[gdb/python] Fix python selftest with python 3.11
111725 	the complaint somehow.  We start out by creating an exec with .debug_types and
111753 	is called with per_cu == nullptr.
111763 	Tested on x86_64-linux, with native and target board cc-with-debug-names.
111807 	The PR29370 testcase is a fuzzed object file with multiple
111818 		abbrev_offset with raw field.
111822 		(find_and_process_abbrev_set): Replace abbrev list lookup with
111831 	silly to cache empty lists of decoded abbrevs (happens with zero
111876 	Wrap python_write_bytecode with HAVE_PYTHON ifdef
111949 	Building GDB currently fails to build with libc++, because libc++ is
111974 	the 2nd and subsequent steps, the command was running with
111977 	This can be observed with the testcase added by this commit, which
112018 	thread_fsm object and associates it with the stepping thread.  For the
112030 	mode, with the target in non-stop mode.  When a step finishes,
112116 	Call _bfd_elf_symbol_refs_local_p with local_protected==true.  This has
112144 	address taken operation in the executable doesn't work with protected
112153 	Reformat to make sure we have a clean file with no deviations
112176 	Build-tested with --enable-targets=all and regression tested on aarch64-linux
112194 	data. There can be multiple such sections with the same name, and they are not
112213 	ld: Pass -nostdlib to compiler with -r
112214 	Pass -nostdlib to compiler with -r to avoid unnecessary .o file and
112218 		* testsuite/ld-elf/linux-x86.exp: Pass -nostdlib with -r.
112292 	whole point of the testcase is to crash GDB with a signal.
112336 	it, replacing it with uses of 'new' instead.
112338 	Replace input_interactive_p with a method
112339 	This replaces the global input_interactive_p function with a new
112344 	ui_unregister_input_event_handler, replacing them with methods on
112372 		* tc-arc.c (md_assembly): Update strspn string with the
112379 	step-indirect-call-thunk.exp with gcc 7") I accidentally committed a duplicate
112402 	user needs to configure using --with-python=/usr/bin/python3.
112413 	scratch.  GDB with this patch has python support.
112426 	"extension_opcode" field now only requires a (signed) right shift, with
112480 	Tested on x86_64-linux, by building with -fsanitize=address and running
112481 	test-case gdb.dwarf2/gdb-add-index.exp with and without
112486 	[gdb/testsuite] Fix regression in step-indirect-call-thunk.exp with gcc 7
112500 	Tested on x86_64-linux, with gcc 7.5.0, 8.2.1 and 12.1.1.
112524 	With an a.out compiled from hello world, we get with
112559 	gdb-add-index runs gdb with -iex 'set debuginfod enabled off'.  If gdb
112561 	message to be printed to stderr indicating that gdb was not built with
112565 	no-op when gdb isn't built with libdebuginfod.
112595 	made the default starting with GCC 12.  The floating point format
112620 	if it is being called in a backtrace with 'set print frame-arguments'
112678 	When building gdb with -fsanitize-threads and running test-case
112718 	[gdb/build] Fix gdb build with gcc 4.8.5
112719 	When building gdb with gcc 4.8.5, we run into:
112727 	  ‘_Tp std::atomic<_Tp>::load(std::memory_order) const [with _Tp = \
112738 	Tested on x86_64-linux, with gdb build with gcc 4.8.5.
112743 	When building gdb with -fsanitize=thread and running test-case
112766 	With gdb with -fsanitize=thread and test-case gdb.ada/array_bounds.exp, I run
112792 	with a gdb build with -fsanitize=thread I run into a data race:
112831 		* gas/config/tc-ppc.c (REG_NAME_CNT): Delete, replace uses with
112925 	test gdb.base/step-indirect-call-thunk.exp fails on Intel X86-64 with the
112950 	with no regressions.
112991 	and then with "start" followed by "until 10", GDB currently
113045 	When building with clang 15, I got this error:
113053 	Tested by rebuilding on x86_64-linux with clang 15.
113072 	Tested on x86_64-linux, with native and target board cc-with-dwz-m.
113107 	cu->per_cu->lang () with cu->lang ().
113115 	LTO plugin: sync header file with GCC
113118 		* plugin-api.h (enum ld_plugin_tag): Sync with GCC.
113125 	Tested on x86_64-linux with native and target board unix/-m32.
113139 	[gdb/testsuite] Run two test-cases with ASAN_OPTIONS=verify_asan_link_order=0
113140 	When building gdb with -fsanitize=address we run into:
113145 	  should either link runtime to your application or manually preload it with \
113169 	[gdb/build] Fix build with gcc 4.8.5
113170 	When building gdb with gcc 4.8.5, we run into problems due to unconditionally
113177 	Fix this by guarding the usage with HAVE_IS_TRIVIALLY_COPYABLE.
113179 	Tested by doing a full gdb build with gcc 4.8.5.
113184 	When building gdb with -fsanitize=thread and gcc 12, and running test-case
113231 	gdb.dwarf2/dw2-dir-file-name.exp and target board cc-with-dwz-m.
113262 	When building gdb with -fsanitize=thread and gcc 12, and running test-case
113306 	specified type of their fields.  We can fix that with
113321 	defined in include/, and shared with other projects, some of those
113353 	It is not possible to build GDB with MSVC today, but if it could, that
113381 	PR29355, ld segfaults with -r/-q and custom-named section .rela*
113385 	section reloc_count is ignored, with the justification that reloc
113480 	to unload the core file.  That unfortunately regressed starting with
113481 	GDB 11, with these commits:
113484 	 408f66864a1a - detach in all-stop with threads running
113524 	getting rid of the core and exiting the inferior.  The problem with
113620 	setting 'libopcodes-styling enabled' has an "auto-off" type behaviour.
113624 	  The target architecture is set to "auto" (currently "i386:x86-64").
113656 	  (gdb) set architecture auto
113657 	  The target architecture is set to "auto" (currently "i386:x86-64").
113719 	With gdb build with -fsanitize=thread and test-case
113720 	gdb.dwarf2/dw4-sig-types.exp and target board cc-with-dwz-m we run into a data
113795 	gdbserver: LoongArch: Simplify code with register number macros
113817 		(subsym_proc_entry): Move earlier, make proc a union, merge with..
113889 	done with a purpose built hashtab del_f.
113931 	that these functions are usable with different memory allocation
113947 	makes it possible to find them all with "grep md_finish",
114020 	That will be fixed with a later patch.
114042 	being that macro->format_hash was created with 7 entries vs. str_hash
114043 	with 16 entries.
114084 	This is mostly a tidy with the aim of being able to free
114113 	doesn't because the str_hash_find added with commit 629310abec88
114125 	Regenerate with automake-1.15.1
114127 	should be regenerated with automake-1.15.1 and autoconf-2.69.  That's
114130 	configury files without trouble, and if someone regenerates files with
114136 	configure.ac:26: aclocal.m4 with aclocal and run automake again.
114153 	but those seemed relatively unlikely to be useful with a gdb.Value, so
114175 	When building gdb with guile 3.0.8, we run into:
114205 	lib with 3.0.5.
114216 	When running test-case gdb.dwarf2/dw2-symtab-includes.exp with target board
114217 	cc-with-debug-names, I run into:
114234 	    /* We're importing a C++ compilation unit with tag DW_TAG_compile_unit
114261 	When running test-case gdb.cp/cpexprs-debug-types.exp with target board
114262 	cc-with-debug-names, I run into:
114299 	with CUs first.
114313 	On a machine with gcc 12, I get this warning:
114328 	Tested by rebuilding on x86_64 openSUSE Tumbleweed with gcc 12.
114349 	Update release README with new version numbers
114447 		  /* Claim it exited with unknown signal.  */
114452 	We therefore return a "signalled" status with a null_ptid (again,
114454 	target returns a "signalled" status, it should be coupled with a ptid
114459 	we know the event process.  If there is no inferior with that pid, we
114512 	gdb.trace/unavailable-dwarf-piece.exp emits decl_line with
114529 	line numbers with signed forms as "0" instead of crashing.  Here's the
114530 	before/after fix for gdb.trace/unavailable-dwarf-piece.exp with that
114621 		subsets.  Zfh->Zicsr is not needed and Zfh->F is replaced with
114623 		Zhinx->Zfinx is replaced with Zhinx->Zhinxmin and
114677 	RISC-V: Fix disassembling Zfinx with -M numeric
114727 	experiment directories as input, a new directory with html files is created.
114794 	causing an internal error. Alongside dealing with this also drop a
114796 	introduction of 3-operand patterns with D set (and which perhaps never
114830 	x86: permit "default" with .arch
114832 	start with in the absence of any overrides (command line or directives).
114854 	When running the test-case included with this patch, we run into:
114904 	then the upstream GDB will work with the upstream kernel.
114908 	earlier kernels (notably, the product kernel with version 4.19 used in
114950 	together with "len".
114980 		closing.  Call subsegs_end with the array of obstacks.
115000 	Synchronize libbierty sources with gcc.
115075 	when dealing with 32-bit addressing mode in 64-bit code.
115109 	When building gdb with -fsanitize=thread and gcc 12, and running test-case
115148 	read_comp_units_from_section is not used (run the test-case with say, target
115149 	board cc-with-gdb-index).
115167 	[gdb/testsuite] Fix gdb.base/early-init-file.exp with -fsanitize=thread
115168 	When building gdb with -fsanitize=thread, I run into:
115186 	("gdb.debuginfod/fetch_src_and_symbols.exp: fix when GDB is built with
115189 	In that commit, the problem was fixed by starting gdb with -quiet, but using
115206 	"  Completion will in some cases guide you with a suggestion of what
115260 	Fix a completion consistency issue with `set' commands accepting integer
115275 	which also means if you strike <Tab> with `set print elements ' input,
115309 	With gdb build with gcc-12 and -fsanitize=thread, and test-case
115345 	Tested on x86_64-linux, with and without -fsanitize=thread.
115367 	reading shell registers caused a GDBserver regression, caught with
115422 	the missing part first, and second with an upcoming change the part in
115479 	would be separated from the instruction operands with a tab character,
115480 	while in other cases the comment was separated with two single spaces.
115531 	The problem with this is that skip_hw_watchpoint_tests, includes this:
115563 	when adding the RTM insns. But with No_qSuf the attribute has no effect.
115590 	Re: ld/x86: skip p_align-1 tests with unsuitable compiler
115635 	[gdb/build] Fix gdb build with -fsanitize=thread and gcc 7
115636 	When building gdb with system gcc 7.5.0, I run into:
115661 	        * bfdio.c (_bfd_real_fopen): Retrieve codepage with
115691 	ld/x86: skip p_align-1 tests with unsuitable compiler
115800 	RISC-V: Add 'Sscofpmf' extension with its CSRs
115915 	[gdb/build] Fix build breaker with --enable-shared
115916 	When building gdb with --enable-shared, I run into:
115919 	  `.rodata' can not be used when making a shared object; recompile with -fPIC
115927 	build with -fsanitize=thread").
115935 	Build on x86_64-linux, with and without --enable-shared.
115948 	Currently, if GDBserver hits some internal assertion, it exits with
115955 	potentially littering the filesystem of smaller embedded targets with
115982 	up with:
115996 	Replace a run-time assertion failure with a warning message when parsing corrupt DWARF data.
115998 		* dwarf.c (display_debug_names): Replace assert with a warning
116045 	while with python 3.6 this works fine.
116066 	Tested on x86_64-linux, with python 3.4 and 3.6, and a backported version was
116067 	tested on the gdb-12-branch in combination with python 2.7.
116072 	When running test-case gdb.reverse/i387-env-reverse.exp for x86_64-linux with
116085 	Tested on x86_64-linux with target boards unix/-m32 and unix/-m32/-fPIE/-pie.
116091 	with target board unix/-m32, it's skipped.
116099 	Tested on x86_64-linux with target boards unix/-m32.
116103 	[gdb/testsuite] Workaround unnecessary .s file with gfortran 4.8
116104 	After running test-case gdb.fortran/namelist.exp with gfortran 4.8.5, I'm left
116105 	with:
116109 	Your branch is up to date with 'origin/master'.
116139 	Tested on x86_64-linux, with gfortran 4.8.5, 7.5.0, and 12.1.1.
116144 	When running test-case gdb.dwarf2/fission-mix.exp with target board dwarf64
116154 	it's own header, with initial length and version:
116184 	which doesn't in look in agreement with the standard.
116203 	[gdb/build] Fix gdbserver build with -fsanitize=thread
116204 	[ Copied from gcc commit 153689603fd ("[gdb/build] Fix gdbserver build with
116207 	When building gdbserver with -fsanitize=thread (added to CFLAGS/CXXFLAGS) we
116214 	  recompile with -fPIC
116220 	Fix gdbserver build with -fsanitize=address").
116265 	Note that I didn't touch */po/*.po{,t} on the assumption that these
116271 	For clang compiled objects with dwarf-5, location list offset address dump
116457 	For Arm Cortex-M33 with security extensions, there are 4 different
116514 	proper GDB testing), you'll end up with an unexpected core file in the
116522 	For example, here's what I get on x86-64 Ubuntu 20.04, with this
116551 	 testsuite/core.connect-with-no.216191.nelson.1656002431
116552 	 testsuite/core.connect-with-no.217729.nelson.1656002431
116569 	may end up with just a single core file in testsuite/.  Still, that is
116572 	Above, we see a couple cores for "connect-with-no", which are the
116573 	result of gdb.server/connect-with-no-symbol-file.exp.  This is a case
116578 	 $ make check TESTS="gdb.server/connect-with-no-symbol-file.exp"
116592 	 testsuite/core.connect-with-no.941561.nelson.1656003317
116593 	 testsuite/core.connect-with-no.941682.nelson.1656003317
116600 	and note that when GDBserver hits an assertion failure, it exits with
116601 	error, instead of crashing with SIGABRT.  I think that should be
116614 	finished, with a shell script that is invoked by the Makefile.  It is
116644 	gdb.sum file, with a side effect being that if you look at the
116647 	printed, and then another with.  IMO, this isn't an issue; when
116692 	  Program terminated with signal SIGABRT, Aborted.
116704 	that searches core files in a way that works with my core pattern as
116716 	Another change is that the directory changing is now done with "set
116717 	cwd" instead of with "cd".  "set cwd" only affects the inferior cwd,
116730 	I think these could all be replaced with a RAII style scoped_restore
116741 	Tested on x86-64/Linux passes with no regressions.
116768 	PowerPC64: fix assertion in ppc_build_one_stub with -Os code
116799 	gcc -fpic -shared -fuse-ld=bfd fails with the confusing diagnostic:
116801 …l `foo' which may bind externally can not be used when making a shared object; recompile with -fPIC
116803 	Call _bfd_elf_symbol_refs_local_p with local_protected==true to suppress
116851 	with assumptions (a) the compiler emits GOT-generating relocations (b)
116864 	PIE with copy reloc" which started to use direct access relocations for
116867 	GCC's aarch64 port does not have the change.  Nowadays with most builds
116913 	    * elfxx-riscv.c (riscv_supported_std_ext): Added h with version 1.0 after v.
116964 	This commit wraps such strings with the gettext macro (_) for
116970 		strings with the gettext macro to prepare future i18n.
116976 	funct<n> fields.  In specific, funct6 had an error message with range
116977 	0..2^<n> ("0..64") unlike other funct<n> fields with 0..2^<n>-1
116978 	(e.g. funct4 with "0..15").
116986 	readelf: replace xmalloc with malloc in slurp_relr_relocs
116996 	previous stub.  The difficulty with debugging these issues is that
116997 	it's not a problem with the stub that triggers the assertion, but the
117055 	Right now, if you compile the same .c input repeatedly with CTF enabled
117061 	it tries to produce multiple per-CU outputs with the same name
117066 	differentiated in the hashtables libctf keeps them in: inputs with the
117085 	.a's can contain many members with the same name, all of which
117087 	distinct dictionaries with distinct types in them, and at least this way
117110 		(ctf_new_per_cu_name): New, come up with a consistent
117114 		ctf_link_in_out properly.  Don't overwrite per-CU dicts with
117267 	The new feature displays binary values by group, with four bits per
117339 	Fix GDB build with GCC 4.8 & 4.9
117484 	with stop events.  E.g., "list" works with location specs.
117489 	e.g., "location" -> "locspec".  Similarly, functions that work with
117497 	gprofng: fix build with -Werror=format-truncation
117576 	Commit 94585d6d4495 resulted in readelf -wF failing with
117650 	For Arm Cortex-M33 with security extensions, there are 4 different
117652 	with earlier Cortex-M derivates, the msp and psp registers are
117678 	For Arm Cortex-M33 with security extensions, there are 4 different
117688 	up with two identical class static functions, both called
117689 	dis_asm_read_memory, with identical implementations.
117696 	that I loose the encapsulation of the method with the corresponding
117704 	difference with this approach, but I think this better reflects how
117725 	we don't use gdb_buffered_insn_length with ARM, so maybe it isn't
117847 	extension_language_ops', which is then filled in with nullptr for Python
117871 	constructor the ui_file* that is passed in is replaced with a member
117911 	coming, I've gone with the above class hierarchy now.
117939 	When building trunk on openSUSE Leap 15.3 with system gcc 7.5.0, I run into:
117963 	diagnostics.c with '#if __GNUC__ >= 11'.
117971 	SW_AT_str_offsets_base.  In this case we left u.str with garbage (from
117986 	Just like on s390x with g++ 11.2.1 and ppc64le with g++ 11.3.1 g++ 11
118019 	gprofng: fix build with -Werror=format-security
118033 	When running test-case gdb.python/py-mi-cmd.exp on openSUSE Leap 42.3 with
118164 	while with target board unix we have instead:
118170 	the variable is not yet initialized, and with target board unix we
118171 	accidentally hit a valid address, but with target board unix/-m32 that's not
118194 	> > Program terminated with signal SIGABRT, Aborted.^M
118228 	> that added these lines in elfcode.h (along with several other changes) need to
118240 	Starting with (future) Clang 15 (since
118249 	testcase with current git Clang.  This testcase is also updated to
118317 		(dwarf2_init): ..do so here, along with most other static vars.
118336 	[gdb/testsuite] Fix gdb.reverse/test_ioctl_TCSETSW.exp with libc debuginfo
118337 	When running test-case gdb.reverse/test_ioctl_TCSETSW.exp with glibc debuginfo
118385 	gdb: LoongArch: Deal with atomic sequence
118396 	checking whether to use babeltrace... auto
118418 	4 with index 14 will has a default name cp4cr14).
118422 	r0~r31 with 0~31
118423 	hi, lo with 36, 37
118424 	fpu/vpu with 40~71
118430 	including those with fixed names and those with default register names.
118434 	struct include name with regnum via index.
118446 	On openSUSE Leap 42.3 with python 3.4, I run into:
118473 	With its movement to the stack, and with the subsequent desire to
118480 	operand displacements with inconsistent style, print_displacement() is
118509 	Somewhat similarly with last_*_prefix representing offsets into the
118518 	taking issue with the loop inverting the order of operands, where
118531 	member to just an array of pointers, with the actual arrays living
118533 	with nul).
118666 	This patch has been tested on Power 10 and Intel with no test failures.
118750 	[gdb/testsuite] Fix XPASS with gcc-12 in gdb.base/vla-struct-fields.exp
118766 	On openSUSE Tumbleweed with gcc-12, I run into a timeout:
118784 	Fix this by prefixing value (as well as the other printed values) with the
118810 	fails with a timeout.
118822 	The problems always start with a line similar to this:
118827 	The problem with this line is that if 'inf->gdbarch' is an ARM
118839 	returns false we then proceed with this code:
118849 	There are similar problems, with similar undefined behaviour, in the
118925 	gdb/testsuite: solve problems with compiler_info caching
118937 	The problem is associated with how compiler_info variable is cached
118956 	However, if the user starting playing with CC_FOR_TARGET or
118964 	scripts, this is done with the help of the two procs
119030 	get_compiler_info with the language 'c'.  Without making this change
119126 	While running the gdb.threads/tls.exp test with a GDB configured
119228 	operand we would loop over the parts and print each part with the
119236 	with the existing infrastructure.
119245 	chunks at the style marker boundaries, with each chunk being printed
119246 	with the correct style.
119289 	any significant slow down in disassembler speed with this change.
119314 	       mask, only with the different offset.
119318 	               (BC): Define new field, with the same definition as CRB field,
119319 	               but with the PPC_OPERAND_CR_BIT flag present.
119338 	This patch updates the regression test gdb.arch/powerpc-power7.exp with
119527 	oss-fuzz hits a flaky crash with a double-free.  I think this is due
119529 	with oss-fuzz not gas.  Anyway, this patch should avoid the problem.
119719 	When running the print_one_insn selftests with -v, I get:
119817 	Tested on x86_64-linux, with a build with --enable-targets=all.
119828 	Tested on x86_64-linux, with a build with --enable-targets=all.
119842 	Tested on x86_64-linux, with a build with --enable-targets=all.
119854 	Tested on x86_64-linux, with a build with --enable-targets=all.
119866 	Tested on x86_64-linux, with a build with --enable-targets=all.
119923 	available in gdb, so the strict response here would be erroring out with
119926 	Older gcc without __int128 support, as well as clang use an unsigned type, but with
119936 	Tested on x86_64-linux with --enable-targets=all.
119954 	combination, while keeping the possibility intact to run with all
119964 	Running the test-case with a gdb build with -fsanitize=undefined, we trigger
119967 	Tested on x86_64-linux with --enable-targets=all.
119972 	On openSUSE Tumbleweed (with gcc-12, enabling ctf tests) I run into:
119993 	[gdb/testsuite] Fix gdb.threads/manythreads.exp with check-read1
119994 	When running test-case gdb.threads/manythreads.exp with check-read1, I ran
120065 	configuration of GDB.  Attempting to continue with the default aarch64:ilp32
120100 	The problem is that with osabi linux we trigger:
120108 	but with osabi none:
120181 	On openSUSE Tumbleweed with target board unix/-m32, I run into:
120227 	"main" is redeclared with a different type in maint.c.  I think this
120472 	Seen with .file 4294967289 "xxx.c"
120481 	that match a unit with errors, since ranges are added to a trie while
120504 	configuration of GDB.  Attempting to continue with the default aarch64:ilp32
120525 	the current language without (1) ever having the value "auto" or (2)
120549 	Only the first 8 registers have been confirmed fixed with this patch
120553 	The test consisted of running a program compiled with float-abi=hard.
120568 	manual terminology and keep coherency with the rest of the code.
120586 	vdsp_version: to check if a function is returned with CSKY_VRET_REGNUM
120639 	FAIL: Build ifunc-1a with -z ibtplt
120640 	FAIL: Build ifunc-1a with PIE -z ibtplt
120698 	with a printed pointer while the gnu stack does not.  This leads to
120699 	failures in the test when running the test with CC_FOR_TARGET='clang'
120751 	  ==2503051== For lists of detected and suppressed errors, rerun with: -s
120779 	will get displayed, while gfortran's symbol starts with "__" and thus will
120780 	be ignored (it cannot be a completion of a word starting with "m").
120845 	Many of the displayed symbols do not actually work with print:
120883 	do not appear in the output of complete.  Still, with a poor enough
120915 	(compiled with gcc/g++ and breaking at main).
120988 	check for this character type was chagened to optional with the
121025 	check once the scoping issue is resolved (and it starts to fail with
121038 	info symbols command.  The test, however was written with gfortran as a
121039 	basis and some of the tests are not fair with e.g. ifx and ifort as
121105 	running the testsuite with F90_FOR_TARGET set, was detected via its
121124 	existed for C/CXX.  We let GDB preprocess a file with the compilers
121144 	Classic and LLVM flang were each tested with their latest releases on
121170 	to check whether or not it was called in with the option
121171 	getting_compiler_info.  If it was called with this option it would
121221 	Gfortran in this case is backwards compatible with most f77 code as
121229 	seems deprecated.  So, with this commit we remove the remaining lines for
121241 	Clarify why we unit test matching symbol names with 0xff characters
121243 	why we test symbols with \377 / 0xff characters (Latin1 'ÿ').
121277 	elf32-v850.h but defined with enum c850_notes note in elf32-v850.c.
121328 	  202be274a41a ("opcodes/i386: remove trailing whitespace from insns with zero operands")
121343 	The current "Specify Location" section of the GDB manual starts with:
121355 	 @item edit @var{location}
121376 	"location", actually end up working with multiple locations, and the
121378 	will work with all the resolved locations.  In other cases, the
121379 	command aborts with an error if the location specification resolves to
121385 	with shorthand "locaction spec", when we're talking about the user
121398 	- It then introduces the term "Location Specification", with
121433 	Doing a 32-bit build with "--enable-targets=all --disable-sim" fails to link
121457 	This patch accomplishes this and enables a 32-bit build with
121464 	make a 32-bit build with "--enable-targets=all" complete correctly
121496 		(init_string_with_size, nextword): Replace malloc with xmalloc.
121498 		(catchar, catbuf): Replace realloc with xrealloc.
121499 		(add_intrinsic): Replace strdup with xstrdup.
121515 	variables, and add_var used push_number inconsistent with its use
121649 	string even though the command would remain registered with GDB, which
121663 	gprofng: fix build with -mx32
121682 	Fix crash with "maint print arc"
121690 	opcodes/i386: remove trailing whitespace from insns with zero operands
121712 	whitespace with '_' so that the issue is clearer:
121782 	Replace bfd_hostptr_t with uintptr_t
121787 	comparison with include/coff/external.h and other code reveals that
121789 	pointer.  That should mean replacing with uintptr_t is OK.
121796 	Requiring C99 means that uses of bfd_uint64_t can be replaced with
121803 	gprofng: fix build with --disable-shared
121818 	modifier is on the last register operand (with a possible immediate
121833 	providing more meaningful diagnostics), this means doing away with a few
121853 	conversions with shrinking element sizes. I have no insight (yet) into
121866 	For VFPCLASSP{S,D,H} and vector conversions with shrinking element sizes
121873 	gprofng: fix build with -mx32
121879 		__collector_getpc): Adapt for build with -mx32
121961 	When debugging such program with the following options:
122054 	was no debug info associated with it, but there is.  Later, if we try to
122087 	    for (auto *iter : qf)
122090 	This patch proposes to wrap the access of the `qf` field with an accessor
122193 	Finally, with the rewrite we can also simplify the caller of this
122262 	Show enabled locations with disabled breakpoint parent as "y-"
122264 	breakpoint is disabled are displayed with "y" in the Enb colum of
122285 	left side of the source window, with "b-" for a disabled breakpoint.
122318 	we would now end up with an empty message in gdb.sum, due to a
122333 	see zero PATH cases now.  I get zero DUPLICATEs with native testing
122334 	now.  I still see some DUPLICATEs with native-extended-gdbserver, but
122363 	the old way of supressing PASS with an empty message, this has the
122402 	mask, only with the different offset.
122406 	        (BC): Define new field, with the same definition as CRB field,
122407 	        but with the PPC_OPERAND_CR_BIT flag present.
122433 		(md_apply_fix): Likewise.  Mask fx_pcrel_adjust with PPC_OPINDEX_MAX.
122447 	[gdb/testsuite] Fix gdb.opt/clobbered-registers-O2.exp with clang
122448 	When running test-case gdb.opt/clobbered-registers-O2.exp with clang 12.0.1, I
122482 	[gdb/testsuite] Fix gdb.opt/clobbered-registers-O2.exp with gcc-12
122483 	When running test-case gdb.opt/clobbered-registers-O2.exp with gcc-12, I run
122510 	doesn't interfere with that.
122530 	  Program terminated with signal SIGABRT, Aborted.
122543 	Tested on aarch64-linux-gnu, with a GCC with DFP support in the PATH,
122590 	version with the following error:
122600 	and use this with register_size to compute the size of the
122631 	By the way, with this patch, the failed testcases in gdb.base/corefile.exp
122659 	When building gdb with -fsanitize=undefined, I run into:
122676 	The problem is here in int_string, where we negate a val with type LONGEST:
122688 	When building gdb with -fsanitize=undefined, I run into:
122702 	[gdb/ada] Fix gdb.ada/dynamic-iface.exp with gcc 7
122703 	This test in test-case gdb.ada/dynamic-iface.exp passes with gcc 8:
122709 	but fails with gcc 7:
122720 	type = <ref> new concrete.intermediate with record
122724 	and with gcc 7:
122757 	There's some code right after the code quoted above that deals with this
122763 		 from the base address.  This was however incompatible with
122776 	Tested on x86_64-linux, with gcc 7.5.0.
122786 	[gdb/testsuite] Skip language auto in gdb.base/parse_number.exp
122787 	In test-case gdb.base/parse_number.exp, we skip architecture auto in the
122790 	Likewise, skip language auto and its alias local in the $::all_languages
122793 	Tested on x86_64-linux, with a build with --enable-targets=all.
122801 	Accept functions with DW_AT_linkage_name present
122802 	Currently GDB is not able to debug (Binary generated with Clang) variables
122865 	nicely with a watchpoint also being typically known as a "data
122897 	multiple breakpoints, I ran the whole testsuite with this hack:
122911 	The way to get to create_breakpoints_sal with multiple lsals is to use
122950 	This adds a new ctor to momentary_breakpoints with a few parameters
123030 	init_raw_breakpoint uses add_location under the hood, and with a dummy
123056 	returns false for bp_loc_other, which is in accordance with we
123077 	exception_catchpoint is really a code breakpoint, with locations set
123177 	Make a few functions work with base_breakpoint instead of breakpoint
123249 	associates the prefix word incorrectly with the following 32-bits as the
123258 	  2      prefix inst A   <- GDB uses this prefix with
123303 	RISC-V: Update zfinx implement with zicsr.
123304 	Update zfinx implement with zicsr, fix missing fcsr use by zfinx.
123370 	between 2–3 GB for a medium-size profile); for smaller binaries with few
123378 	"extended" boolean, with 0 meaning no warning, 1 meaning warn, other
123381 	Yes, this patch introduces fails on arm/aarch64.  Not a problem with
123391 		1, 2 consistent with link_info.warn_execstack.
123422 	page-break, with the page-break falling part way through some example
123469 	with this patch on LoongArch, there is no failed testcases.
123493 	gdbsupport: fix path_join crash with -std=c++17 and -D_GLIBCXX_DEBUG
123494 	When building GDB with -std=c++17 and -D_GLIBCXX_DEBUG=1, I get:
123497 …s>::operator[](std::basic_string_view<_CharT, _Traits>::size_type) const [with _CharT = char; _Tra…
123503 	The reason this is not seen with -std less than c++17 is that our local
123504 	copy of string_view (used with C++ < 17) does not have the assert in
123509 	IS_ABSOLUTE_PATH is normally used with null-terminated string.  It's
123511 	because index 0 in such a string is valid.  But not with an empty
123533 	(observed with PE/COFF ones) even if really there's no change. Doing so
123549 	Instead of re-arranging the present if(), fold this logic with that of
123555 	So far this option had no effect when used together with e.g.
123559 	statements with identical code.
123583 	reason. (Similarly stripping a binary linked with a linker pre-dating
123610 	Replace the sve bool member of aarch64_features with a vq member that
123614 	can be used as a key with std::unordered_map<>.
123621 	target descriptions with unordered_maps indexed by aarch64_feature.
123644 	Fix compile time warning building gold with Clang-14.
123674 	that is causing regression test on x86_64-linux with taskset -c 0.
123715 	The option parsing is done with parse_args.
123831 	do_repeat_with_expander() already deals with the "no expander" case
123833 	lacks compared with do_repeat() is a call to sb_build(), which can
123834 	simply be moved (and the then redundant sb_new() be avoided). Along with
123858 	syscall with "int 0x80".  This causes a segfault on kernels with
123876 	Fix gdb.python/py-connection.exp with remote targets
123886 	The problem is that "disconnect" when debugging with the native target
123887 	asks the user whether to kill the program, while with remote targets,
123892 	Tested with --target_board unix, native-gdbserver, and native-extended-gdbserver.
123900 	errors out e.g. on a recording with only gaps.
123961 	Avoid having to unload file in gdb.server/connect-with-no-symbol-file.exp
123962 	gdb.server/connect-with-no-symbol-file.exp's connect_no_symbol_file
123992 	   response!  With the enforcing patch, this was caught with:
124011 	So if 'scope0.c' doesn't work, we try again with
124209 	Fix "gdb --write" with core files
124210 	If you load a core file into GDB with the --write option, or "set
124219 	 Program terminated with signal SIGTRAP, Trace/breakpoint trap.
124291 	simply removed the unnecessary (in C) cast rather than replacing with
124306 	[gdb/testsuite] Fix gdb.cp/break-f-std-string.cc with older gcc
124308 	with system gcc 7.5.0, I run into:
124315 	The same for gcc 8.2.1, but it passes with gcc 9.3.1.
124317 	At source level (as we can observe in the .ii file with -save-temps) we have
124326 	while with gcc 9.3.1, we have instead:
124341 	Tested on x86_64-linux, with:
124350 		* pe-dll.c (dll_name): Delete, replacing with..
124361 	Just like on s390x with g++ 11.2.1, ppc64le with g++ 11.3.1 produces a
124391 	different architectures and so it works with different long double
124415 	On aarch64-linux, with test-case gdb.dwarf2/dw2-out-of-range-end-of-seq.exp I
124455 	PR29142, segv in ar with empty archive and libdeps specified
124477 	[gdb/testsuite] Fix gdb.base/catch-syscall.exp with --with-expat=no
124478 	When doing a gdb build with --with-expat=no, I run into:
124506 	nm: use -U as an alias for --defines-only, in line with llvm-nm
124556 	Regenerate syscalls/{ppc64,ppc}-linux.xml on a system with 5.14 kernel.
124570 	but the tests excercised there can all be executed if gdb is configured with
124576 	Tested on x86_64-linux, with:
124577 	- a gdb build with --enable-targets=all, and
124578 	- a gdb build build with my usual --enable-targets setting (too long to
124584 	When running test-case gdb.reverse/fstatat-reverse.exp with target board
124598 	The problems is that while with native we're trying to record these syscalls
124604 	with unix/-m32 we have instead:
124622 	Note that opcodes is regenerated with cgen commit d1dd5fcc38e reverted,
124623 	due to failure of bpf to compile with that patch applied.
124631 		forward declarations.  Replace PTR with void *.
124697 	While looking into this, I found that the configuring with
124809 	you need to compile with -D_GLIBCXX_USE_CXX11_ABI=0 to use the old
124814 	ABI with -D_GLIBCXX_USE_CXX11_ABI=0, then it passes cleanly.
124816 	So why is it that setting a breakpoint at "f(std::string)" fails with
124817 	modern ABI, but passes with old ABI?
124850 	GDB has code in place to let users set a breakpoint at a function with
124864 	with old pre-C++11 ABI is "_Z1fSs".  That uses the abbreviation "Ss",
124870 	while with DMGL_VERBOSE you'd get:
124888 	And here lies the problem when you try to do "b f(std::string)" with a
124889 	program compiled with the C++11 ABI.  In that case, std::string
124915 	with the C++11 ABI.
124940 	DMGL_VERBOSE.  So the patch replaces gdb.cp/no-dmgl-verbose.exp with a
124957 	behavior when compiling/running the test with the -m32 board.  This
124963 	parameters with GDB implemented Fortran intrinsic functions.  If these
124968 	would then be used with the LBOUND/UBOUND/SIZE intrinsics.
124971 	running on targets with 64 bit.  For this, the compiled tests evaluate the
124987 	With this patch both test run fine with the unix/-m32 board and
124992 	with Fortran 2008 and removing tests would have decreased coverage.
124994 	A last change that happened with this patch was due to gfortran's and
125009 	does not work with ifx (or flang for that matter, they behave similarly
125017 	on the other hand fail to compile with gfortran (9.4.0) as the compiler
125018 	identifies an Integer overflow here.  Finally, to make this work with
125083 	Fix compiling binutils/resbin.c with Clang version 14
125096 		* basic_blocks.c: Replace uses of PTR with void * throughout.
125111 		* cr16-dis.c (print_arg): Replace PTR with void *.
125126 		PTR with void *.
125132 		* hashtab.h (HTAB_EMPTY_ENTRY): Replace PTR with void *.
125143 	of two problems with the generic overflow check:
125307 	Tested on x86_64-linux with native and unix/-m32.
125333 	- openSUSE Tumbleweed (with glibc 2.35), and
125334 	- openSUSE Leap 15.3 (with glibc 2.31).
125371 	- openSUSE Tumbleweed (with glibc 2.35), and
125372 	- openSUSE Leap 15.3 (with glibc 2.31).
125382 	[gdb/testsuite] Fix gdb.tui/scroll.exp with read1
125396 	but with check-read1 I get instead:
125412 	- matches the line with "(gdb) p 19", and
125423 	Tested on x86_64-linux with make targets check and check-read1.
125427 	[gdb/testsuite] Fix gdb.cp/casts.exp with -m32
125428 	When running test-case gdb.cp/casts.exp with target board unix/-m32, I run
125463 	Tested on x86_64-linux with native and target board unix/-m32.
125468 	In OBS, on aarch64-linux, with a gdb 11.1 based package, I run into:
125481 	with many more UNRESOLVED following.
125500 	[gdb/testsuite] Fix gdb.ada/catch_ex_std.exp with remote-gdbserver-on-localhost
125506 	[Inferior 1 (process 15656) exited with code 0177]^M
125516 	Tested on x86_64-linux with native and target board
125521 	[gdb/testsuite] Fix gdb.threads/fork-plus-threads.exp with check-readmore
125522 	When running test-case gdb.threads/fork-plus-threads.exp with check-readmore,
125536 	Fix this by adopting a line-by-line approach, which deals with those messages
125539 	Tested on x86_64-linux with native, check-read1 and check-readmore.
125613 	with a 32-bit libbfd.  Revert those changes.
125675 	This removes init_raw_breakpoint_without_location, replacing it with a
125742 	On PowerPC with a Linux 5.9 kernel or latter, the address where gdb stops
125754 	The bp-permanent.exp and kill-after-signal tests run fine on PowerPC with an
125771 	user/kernel/vdso cycle is balanced with the addition of the "brctl"
125784 	I do not have access to a system with the first patch but not the second.  I did
125785 	test on Power 9 with the Linux 5.15.0-27-generic kernel.  Both tests fail on
125786 	this Power 9 system.  The two tests also fail on Power 10 with the Linux
125793 	the Power 9 and Power 10 systems with out any failures.
125798 	I hit this just now with a make -j build after touching config.bfd.
125812 	[gdb/testsuite] Fix gdb.dwarf2/locexpr-data-member-location.exp with nopie
125813 	When running test-case gdb.dwarf2/locexpr-data-member-location.exp with
125827 	but this doesn't work with the target board setting, because we end up doing:
125869 	gdb: make regcache's cooked_write_test selftest work with native-extended-gdbserver board
125915 	using `ld -r -b binary` or `objcopy`, with no elf header flags set.  But
125917 	with all ABIs.
125998 	using the cc-with-debug-names.exp target board.
126066 	     with so it can pick the right breakpoint kind, so it wants to
126136 	disconnecting from GDBserver (with the disconnect command), and
126169 	gdb.threads/fork-plus-threads.exp") broke some tests with the
126279 	   observer (with a nullptr objfile, to indicate that the previously
126329 	remote_check_symbols, replace it with an assert.  All callers must
126337 	As before, on sufficiently old glibc this conflicts with a global
126343 	LTO plugin: sync header file with GCC
126346 		* plugin-api.h (enum ld_plugin_tag): Sync with GCC.
126420 	ld: Regenerate aclocal.m4 with automake 1.15.1
126421 		* aclocal.m4: Regenerate with automake 1.15.1.
126428 	gdb.threads/access-mem-running-thread-exit.exp with gdbserver, which I
126435 	The problem starts with GDB telling GDBserver to select a thread, via
126436 	the Hg packet, which GDBserver complies with, then that thread exits,
126442 	the thread that GDB has selected with the Hg packet.  Since the thread
126464 	When testing gdb.threads/access-mem-running-thread-exit.exp with
126477 	The problem is that the testcase spawns a second inferior with
126485 	auto-connect-native-target off", to prevent testcases from mistakenly
126486 	running programs with the native target, which would exactly be the
126538 	with a call to 'mi_gdb_start' - just for consistency.
126584 	gdb/testsuite: fix mi-exec-run.exp with native-extended-gdbserver board
126585 	When running with the native-extended-gdbserver board, I currently see
126600 	with argument passing within the test script.
126622 	the default mi_gdb_start with its own version.
126628 	time we get to default_mi_gdb_start, we end up with the args list
126648 	gdb: fix failures in gdb.mi/mi-exec-run.exp with native-extended-gdbserver
126674 	crashing, which is bad), so we have an eof pattern associated with
126705 	[gdb/testsuite] Fix gdb.cp/align.exp with gcc 12.1 / 11.3
126706 	Starting with gcc 12.1 / gcc 11.3, for test-case gdb.cp/align.exp we run into:
126715 	Tested on x86_64-linux, with gcc 7.5.0, gcc 12.1 and clang 12.0.1.
126743 	  - GDB build with clang + glibc < 2.33.
126806 	[gdb/testsuite] Fix gdb.multi/attach-no-multi-process.exp with check-readmore
126807 	When running test-case gdb.multi/attach-no-multi-process.exp with
126829 	Fix this by using a gdb_test_multiple instead with a '$gdb_prompt ' regexp, so
126832 	Tested on x86_64-linux with native, check-read1 and check-readmore.
127000 	signature to a corresponding function in breakpoint_ops, with the
127006 	with functions that simply forward a call from breakpoint_ops to the
127007 	corresponding virtual method.  These are all done with lambdas,
127017 	with a real method.
127061 	fixes the size issue with the new index writer.
127067 	Fix .debug_names regression with new indexer
127126 	The issue can be reproduced by hand with:
127383 	s390: Add DT_JMPREL pointing to .rela.[i]plt with static-pie
127417 	(say, two arrays of different sizes with the same name in two different
127427 	runs of ld with the same inputs can produce different outputs!
127433 	which should be impossible, pick the type with the lowest type ID).
127481 	Replace with equivalent methods.
127497 	Replace with calls to blockvector::blocks, and the appropriate method
127505 	Replace with equivalent method.
127512 	Replace with an equivalent method.
127519 	Replace with access through the block::ranges method.
127526 	Replace with range for loops.
127533 	Replace with an equivalent method on struct block.
127540 	Replace with equivalent methods on blockrange.
127547 	Replace with equivalent methods.
127554 	Replace with equivalent methods.
127561 	Replace with equivalent methods.
127568 	Replace with equivalent methods.
127575 	Replace with equivalent methods.
127585 	x86: Disable 2 tests with large memory requirement
127605 	 FAIL: gdb.base/parse_number.exp: lang=auto: ptype 0xffffffffffffffff
127679 	out that if I configure with:
127684 	but maybe the gnulib update helped with this.
127705 	It has been tested using an STM32L5 board (with cortex-m33) and the
127706 	sample applications shipped with the STM32Cube development
127721 	Armv8-M architecture with Security extension features four stack pointers
127725 	unwinding, and replaces all updates of cache->prev_sp with calls to
127737 	arm_m_exception_cache() and relies on the definition with the XML
127760 	Then, I reproduced the same fail with Ubuntu 20.04 as Simon said, and I
127866 	I noticed that these files failed to format with Black, because they use
127898 	patch also fixes a formatting isue with the decimal_vector expected value
127911 	This fixes build breakage using clang with libc++ on FreeBSD where
127944 	variable is treated as an array with rank zero.  GDB currently does
128028 	Issues were reported with some MS-Windows hosts, see the thread
128080 	 - Connect to a remote target with inferior 2, continue and stop on the
128082 	 - Connect to a separate remote target / GDBserver instance with inferior 1,
128097 	   for (auto *target : all_non_exited_process_targets ())
128140 	with ASan while /proc/sys/kernel/yama/ptrace_scope is set to 1 (prevents
128236 	with older versions of readline.  GDB can be built against the system
128273 	            with history-search-backward; fix a display problem with \
128291 	replaced with the latest upstream readline code, as I have not changed
128347 	'--with-system-readline' flag, and build GDB on a system that uses
128461 	Pedro pointed out that gdb-add-index is much slower with the new DWARF
128495 	with the ifdef RIGHT compiler directive.
128519 	(gdb) PASS: gdb.base/solib-search.exp: backtrace (with wrong libs) (data collection)
128521 	The backtrace on Intel with the good libraries is:
128530 	(gdb) PASS: gdb.base/solib-search.exp: backtrace (with right libs) (data collection)
128531 	PASS: gdb.base/solib-search.exp: backtrace (with right libs)
128536 	believe it has to do with the default size of the data and code
128557 	Now with the patch the backtrace for the bad library on PowerPC looks
128574 	(gdb) PASS: gdb.base/solib-search.exp: backtrace (with right libs) (data collection)
128575 	PASS: gdb.base/solib-search.exp: backtrace (with right libs)
128590 	actually my original fix for the program until I spoke with Doug Evans
128619 	follow the code with the standard on the side when we use the same
128639 	name.  Add a "with_test_prefix" with that name, so that all tests
128683 	  Support for the `p' packet is auto-detected, currently unknown.
128696 	  Support for the `X' packet is auto-detected, currently unknown.
128718 	  if (first_path ends with a slash)
128728 	components together (along with unit tests).
128734 	(for example, when the right hand side is a Windows path with a drive
128786 	  This GDB supports auto-downloading debuginfo from the following URLs:
128792 …(gdb) with confirm off -- file testsuite/outputs/gdb.debuginfod/fetch_src_and_symbols/fetch_src_an…
128795 	  This GDB supports auto-downloading debuginfo from the following URLs:
128874 	Replace symbol_symtab with symbol::symtab
128876 	symbol_set_symtab with a method.
128878 	Replace symbol_arch with symbol::arch
128881 	Replace symbol_objfile with symbol::objfile
128894 	For a series I'm experimenting with, it was handy to hide a symbol's
129127 	with the following:
129163 	gdbsupport/selftest: Replace for_each_selftest with an iterator_range
129196 	the insns (with the embedded rounding specifier not last) were used.
129201 	It's not just REX.W which is ignored with opcode 0x90. The same goes for
129225 	table with just a single file and a single directory.
129289 	if you managed to construct a pointer-to-derived with an embedded
129319 	stopped at an unexpected location.  But it starts failing with this
129481 	[gdb/testsuite] Fix gdb.ada/float-bits.exp with -m32
129488 	but with target board unix/-m32 we have instead:
129506 	Tested on x86_64-linux with native and unix/-m32.
129521 	[gdb/testsuite] Fix gdb.go/methods.exp with check-readmore
129522 	When running test-case gdb.go/methods.exp with make check we have:
129529 	but with make check-readmore the XFAIL fails to trigger:
129638 	that target_write_memory is called with LEN==0, due to this in
129688 	--gc-sections, and winds up with an entry in the middle of a
129735 	Share handle_ms_vc_exception with gdbserver
129752 	This makes it more consistent for the eventual merger with gdbserver.
129822 	Fix regression on Windows with WOW64
129824 	debugging 32-bit processes.  This failed with gdb head, but not with
129881 	Building with clang++-14, I see:
129934 	gdb: fix build errors in gdbsupport/thread-pool.h used with old gcc
129935 	When I build gdb with gcc 8.3, there exist the following build errors,
129970 	Tested on x86_64-linux with target boards unix and unix/-m32.
129978 	each label. Worst affected files are the ones built with debugging
130008 	Fix this error when building with clang++-14:
130020 	Building with clang++-14, I see:
130023 …/home/smarchi/src/binutils-gdb/gdb/mips-tdep.c:453:12: error: use of bitwise '|' with boolean oper…
130087 	Reading a simple file compiled with :
130119 	read last->line.  It works with the manually-maintained array, but since
130136 	   then assign the result to the current subfile, obtained with
130163 	currently, replace them with empty checks, I think it ends up
130172 	gdb: allocate subfile with new
130173 	Allocate struct subfile with new, initialize its fields instead of
130187 	When building with -std=c++11, I get:
130203 	When building with -std=c++11, I get:
130238 	However, if you experiment with the series, this patch can be moved
130249 	This updates the .debug_names writer to work with the new DWARF
130255 	This updates the .gdb_index writer to work with the new DWARF scanner.
130286 	simpler to reuse this code with the new indexer.
130391 	with the existing DWARF indices.  However, because names are stored
130600 	[gdb/testsuite] Fix gdb.base/stap-probe.exp with read1
130601 	When running test-case gdb.base/stap-probe.exp with make target check-read1, I
130623 	with the more generic max-value-size:
130638 	tests to detect this situation and stop with "untested".
130666 	and alike blocks"), while dealing okay with actual assembly source files
130671 	expansion associated with the line invoking the macro. However, as soon
130692 	and alike blocks"), while dealing okay with actual assembly source files
130699 	Diagnostics (and debug info) would be associated with the directive
130700 	terminating the iteration construct, rather than with the actual lines.
130719 	gprofng doesn't build with gcc 5.5
130752 	Replace with equivalent getter/setter macros.
130760 	with equivalent methods.
130792 	Replace them with equivalent methods on the appropriate objects.
130816 	(some only with Fortran 2003) the optional parameter KIND.  This
130828 	is called with a certain amount of arguments (1/2/3). The helper methods
130835 	intrinsic function.  This patch also introduces intrinsic functions with
130890 	wrong.  Consider debugging Fortran code compiled with GNU and e.g. the
130902 	compiled with "-fdefault-integer-8" a user will always see the actual
131011 	adapted GDB's behavior to be in line with
131060 	[gdb/testsuite] Fix gdb.base/annota1.exp with pie
131062 	robust") we see this fail with target board unix/-fPIE/-pie:
131088 	As reported in PR29043, when running test-case gdb.dwarf2/dw2-lines.exp with
131111 	Tested on x86_64-linux with target boards unix, unix/-m32, unix/-fPIE/-pie and
131189 	I noticed that a build of GDB with GCC + --enable-ubsan, testing
131196 	  GDB process exited with wait status 269549 exp9 0 1
131202 	you compile with "g++ -std=c++20 -Wall", you'll see that GCC no longer
131327 	(max 64-bit) in all languages, which crashes a GDB built with UBsan
131334 	used with "maintenance set" commands as well in future.
131356 	    $ PKG_CONFIG_PATH=/opt/debuginfod/lib/pkg-config ./configure --with-debuginfod
131361 	    $ ./configure --with-debuginfod PKG_CONFIG_PATH=/opt/debuginfod/lib/pkg-config
131370 	    configure: error: "--with-debuginfod was given, but libdebuginfod is missing or unusable."
131380 	   @PKG_CONFIG_PATH@ gets replaced with the actual PKG_CONFIG_PATH value
131432 	intermediary binary with symbols.  Change the test to output the
131448 	gdb/fortran: print fortran extended types with ptype
131489 	and running this with GDB and setting a BP at 17:
131634 	  starting with \r\n\032\032 and ending with \r\n
131695 	nothing to do with the symtab's filename.
131739 	gdb: convert reggroup to a C++ class with constructor, etc
131740 	Convert the 'struct reggroup' into a real class, with a constructor
131793 	Replace manual linked list with a std::vector.  This commit doesn't
131826 	The problem with this is that what usually happens is that the target
131856 	  command I'm less concerned with the output changing here.
131884 	The same happens with 'tui reg prev' (but the error message is
131905 	gdb/tui: avoid theoretical bug with 'tui reg' command
131983 	couple of issues with GDB.
132005 	configured GDB with --enable-ubsan, I suspect that without this the
132123 	when dealing with e.g. PE/COFF binaries (linked from ELF objects), where
132129 	- I realize this is a layering violation; I don't see how to deal with
132140 	be added here then (with, as necessary, expecations suitably relaxed to
132147 	number info associated with them.
132151 	number info associated with them.
132214 	 FAIL: gdb.base/callfuncs.exp: call inferior func with struct - returns float _Complex
132290 	contents (through the various_contents* accessors) are all fine with
132366 	Interpreters should be registered with GDB, not by calling interp_add,
132367 	but with a call to interp_factory_register.  I've checked the insight
132426 	- Decorates backtraces with the "[PAC]" identifier when a frame has signed
132585 	replace the barrier with an array of flags (one per child thread).  Each
132590 	made modifications to that, to avoid interfering with
132615 	The test introduced by this patch would fail in this configuration, with
132618 …fork-other-thread.exp: fork_func=fork: target-non-stop=auto: non-stop=off: displaced-stepping=auto…
132647 	In the first snippet, we resume the stepping thread with the range-stepping (r)
132723 …xp: fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=auto: i=14: next to for …
132729 	failure in gdb.threads/forking-threads-plus-breakpoint.exp with the
132734 	target to stop a thread and wait() reports that this thread stopped with
132780 	to stop a thread, but wait() reports that it stopped with another signal
132795 	      /* A thread that has been requested to stop by GDB with vCont;t,
132818 	There is a problem with how GDB handles a vfork happening in a
132845 	shared with the child, that would re-insert breakpoints in the child
132872 	The problem is present with all-stop and non-stop targets.  The only
132873 	difference is that with an all-stop targets, the other threads are
132902 	   the event thread (this is already the case, with a non-stop target).
132907 	In the same scenario, but with an all-stop target:
132938 	This helped me, it shows which ptid we actually call target_resume with.
132947 	restart them after.  To help with this, add inferior parameters to
132959 	gdb: replace inferior::waiting_for_vfork_done with inferior::thread_waiting_for_vfork_done
132964 	Replace the boolean flag (waiting_for_vfork_done) with a thread_info
132971 	could end up with inferior::waiting_for_vfork_done without a thread
133033 	with erroneous debug information, the overall debugging experience will
133053 	the first instruction with this marker (if any) to be the place where a
133059 	foo begins with a call to an inlined function, covering from 0xa800 to
133116 	Testcases have been compiled with both gcc/g++ (verison 9.4.0) and
133118 	set the prologue_end marker.  Tests done with GCC 11.2.0 (not over the
133121 	No regression have been observed with GCC or Clang.  Note that when
133130 	Currently when recording a line entry (with
133154 	logging statements in auto-load.c to output style filenames.  You can
133155 	see it in action by setting "set debug auto-load 1" and running a
133170 	built with -gctf:
133245 	with its clients (gdb and gdbserver).  However, if we ever want the
133294 …UNRESOLVED: gdb.guile/scm-breakpoint.exp: test_watchpoints: create a breakpoint with an invalid ty…
133394 	However, with -gnata, they will be preserved.  In this situation, it's
133403 	"end_symtab", which actually deal with compunit_symtabs.  I believe this
133462 	with gcc -fno-toplevel-reorder (previously -fno-unit-at-a-time).
133488 	This commit replaces this with gdb_vprintf instead.
133584 	name, these are now printed with styling information, and so will have
133681 	As arrays with dynamic ranks make use of a single
133686 	we can resolve an array type with dynamic rank.  To do this the
133704 	range isn't part of an array with dynamic rank, and so the range
133819 	This allows for a small cleanup, replacing an if/then/else with an
134010 	needed, with these adjustments removed all the existing tui tests
134017 	When this layout is selected with current master, gdb will leave a 4
134034 	was fixed), but with this commit, the above layout now correctly fills
134064 	What you end up with is a full width cmd window with the status bar
134074 	Something weird has gone on, gdb has overlapped the cmd window with
134123 	a series of 'V' or 'H' characters, ending with a single 'C'
134182 	Notice that gdb has assigned 27 lines of screen space, even with the
134267 	steps with current master:
134280 	problem is that, with rounding, both the regs and src windows are
134315 	After this, with current master, gdb crashes with a floating-point
134408 	has nothing directly to do with tui debug, but it is worth mentioning
134448 	the screen.  However, with custom layouts, this might not be true, so
134524 	old command names, with the new name being mentioned first.
134529 	This caused a build failure with !CXX_STD_THREAD.
134564 	Regen bfd po/SRC-POTFILES.in
134809 	Sample output with the new field:
134857 	the current uses.  Something seems odd with this use of
134898 	I built a random project with -gctf, in order to test the CTF support in
134918 	buildsym_compunit.  But if the field was purposely filled with random
134920 	and we'll continue with ccx->builder equal to 0xbebebebebebebebe.
134931 	... where /opt/gcc/git/bin/gcc is a gcc with CTF support, given my
134961 	When debugging multiple inferiors with the Linux native target and
135060 	We can see that we resume the inferior with vCont;c, but got NO_RESUMED.
135110 	 - resume_one_lwp checks with check_ptrace_stopped_lwp_gone that the
135133 	The fix I came up with is to mark the secondary thread as !stopped (or
135137 	exit event for it.  Here's the GDBserver logs with the fix applied:
135175 	      [threads] wait_1: ret = LWP 724597.724598, exited with retcode 0
135308 	reality it's a problem with the testsuite's terminal implementation.
135606 	  $ # First, spawn a process with PID 26253 to attach to later.
135642 	Running the same scenario with "debug infrun on" reveals more details.
135746 	Was not written with readline 7 in mind, only readline 8+.  Between
135759 	still KFAIL with readline 7.
135761 	It's a little unfortunate that the test is KFAILing with readline 7,
135768 	PASS with readline 7.
135812 	the expected output patterns, with this change the tests pass even
135864 	function->is_linkage. Yet with the flag set, we should then also return
135884 	with the D extension ought to extend to the ignoring of a meaningless
135889 	Note that to avoid breaking existing code the forms with a 3rd operand
135927 	might have gdb_stdout==gdb_stdlog and so, conceivably, wind up with
135967 	This patch simplifies it, with an eye toward changing it to use RAII
136076 	libtool.m4: fix the NM="/nm/over/here -B/option/with/path" case
136079 	detection tries to run nm against a copy of nm with the options in it:
136113 	--with-build-config=bootstrap-lto, because the lto plugin is now using
136116 	with the GCC just built.)
136120 		* libtool.m4 (LT_PATH_NM): Handle user-specified NM with
136177 	This test was added without a corresponding fix, with some setup_kfails.
136178 	However, it results in UNRESOLVED results when GDB is built with ASan.
136181 	  GDB process exited with wait status 1946871 exp7 0 1
136244 	In this case, the output of the first command will be mixed in with
136254 	Now, we look for the first command output with no regard to what is
136283 	for ctf_write_mem, with thresholding, and once each for
136286 	with thresholds of 0 or (size_t) -1, respectively.
136375 	contains all static function symbols too (if it is emitted at all), with
136385 	it, we do the same with data symbols: this is redundant right now
136439 	work with both Python 2 and 3.  Remove them and adjust the code to use
136450 	   the user passes --with-python=python2, this will cause a configure
136457 	the author and reviewer of the patch even remember to test with Python
136480 	supported.  Otherwise (with this patch), things will only fail at
136541 	other if() and clarifies that subsequently only entry 0 is dealt with
136587 	ELF32, but this would require .rel relocations, i.e. with the addend
136599 	pair of quotes counts as the escaping of a quote, with the pair being
136602 	deals with \" sequences, but it _retains_ the escaping \. Hence only the
136618 	section. I'm afraid the only way that I see to deal with this would be
136700 	This shares aarch64-nat.c and nat/aarch64-hw-point.c with the Linux
136820 	This method takes an address, and returns a string with the format:
136825 	SYMBOL is a symbol with an address lower than ADDRESS, and OFFSET is
136837 	with the SYMBOL name, the gdb.format_address function ensures that the
136854 	gdb.Architecture object, but, with this commit, this might not be the
136857 	So, with this commit I've made it a requirement that the PyObject be a
136858 	gdb.Architecture, and this is checked with the assert.  And in order
136983 	replaces most calls to bpstat_stop_status with calls to
137006 	While playing with adding a new event kind, I noticed that
137025 	On x86 machines with xmm register, and with recent versions of
137029 	I notice this happening on a current Fedora Rawhide install with the
137157 	The benefit of this approach is that it would work with the expression
137160 	sub-field size with an xmm register.  If other architectures started
137166 	different target description, with different field names for xmm
137197 	guarded the new function with an appropriate GCC define.  In the exp
137210 	I found that on a Fedora 35 install, with these packages installed, I
137239 	  End with a line saying just "end".
137305 	However, that example isn't fully correct, because with that command
137320 	This commit improves the status quo with the following two changes:
137323 	   don't start GDB with the -data-directory command line option.
137344 	 # Test the built GDB with some alternative data directory, e.g., the
137381 	I've also removed the assertion.  Nothing much goes wrong with gas if
137511 	  bfd(elfnn-loongarch.c) with the functions defined in
137541 	with Python 2, due to PyDict_GetItemWithError being a Python 3-only
137559 	My first idea was to replace it with a C++ map
137578 	   with that name.  But we can already tell if there's a non-Python
137579 	   command registered with that name.  Return an error if that happens,
137598 	commands would be backed with a stale PyObject or simply nothing.
137611 	Fix crash with stepi, no debug info, and "set debug infrun 1"
137612 	A stepi in a function without debug info with "set debug infrun 1"
137657 	As usual with this sort of patch, it has passed internal testing, but
137658 	I don't have a good way to try it with dejagnu.  So, I don't know
137687 	can fold the vector shift insns with an XMM source as well. While
137689 	not enough (both operands could have multiple sizes with just a single
137792 	gprofng: Skip jsynprog with a broken javac
137797 …2.b06-6.fc35.x86_64/jre/lib/amd64/server/libjvm.so: rebuild shared object with SHSTK support enabl…
137799 	Set GPROFNG_BROKEN_JAVAC to "yes" only with a broken javac and skip the
137800 	jsynprog test with a broken javac.
137806 		with a broken javac.
137809 		* testsuite/gprofng.display/display.exp: Skip jsynprog with a
137818 	aren't present.  Return with TARGET_XFER_E_IO if the gdbarch method
137841 	... but that it failed with the distro GNAT.  Further investigation
137883 	example, someone configuring with --target=x86_64-linux will match
137920 		* po/SRC-POTFILES.in: Regenerate.
137936 	two objects which had the bit set, or ANDNing together an object with
137937 	the field set and one with the field clear.
137961 	Now that {L,K}1OM support is gone, and with it the brokenness in
137983 	  regress with the planned removal).
138075 	rl_deprep_terminal, however, if we replace this with a new function,
138258 	Consider GDB debugging a multi-threaded inferior with both CLI and GDB/MI
138380 		and -Wno-switch with GPROFNG_NO_FORMAT_TRUNCATION_CFLAGS and
138391 		-Wno-nonnull-compare with GPROFNG_NO_NONNULL_COMPARE_CFLAGS.
138407 		/* FALLTHROUGH */ with ATTRIBUTE_FALLTHROUGH.
138458 	[2].  Add There is a new --with{,out}-msgpack configure flag, and the actual
138482 	with notes that are not handled in a special way.  This allows one to
138496 		* configure.ac: Add --with-msgpack flag and check for msgpack
138578 	For a binary with the HSA OS ABI, the change looks like:
138682 	recently disabled unless testing with the native target, because they
138698 	subroutines end with advance=yes, except this one.  Fix it by using
138829 	structure with the new value.
138837 	gprofng didn't build with gcc 6.3 due to the usage of __attribute__
138851 	is not guaranteed to be run with the current buffer set to the process
139043 	object can't be reinitialised with a different command name, so:
139047 	  can't reinitialize object with a different command name
139049 	This feels like a pretty weird edge case, and I'm happy to live with
139100 	checked against 0, with 0 indicating that the field is invalid (was
139185 	Upon target_wait entry, target_pre_wait is notified with the ptid
139186 	passed to target_wait. Upon exit, target_post_wait is notified with
139201 	This code isn't often exercised, I think, because languages with real
139227 	The problem only shows up with the "finish" command. The "call" command
139272 	also works with nightly.  I also tested stable and 1.48.
139280 	Avoid crash with cross-linux core file
139282 	gdb with that core.  When run with a cross-linux gdb (in this case,
139283 	x86-64 host with ppc64-linux target), the test fails:
139287 …| warning: `/lib64/libc.so.6': Shared library architecture unknown is not compatible with target a…
139310 …| `/lib64/libc.so.6': Shared library architecture unknown is not compatible with target architectu…
139354 	gdb/auto-load: Remove repeating "auto-load" from debug message
139355 	Remove "auto-load:" from a format string passed to auto_load_debug_printf.
139356 	It is unnecessary since this function will prefix the string with "[auto-load]"
139412 	process exit with a different exit code, and ensures that GDB reports
139472 	exiting, as opposed to just the leader (with pthread_exit(), for
139502 	the non-leader threads.  Then, if we are left with only the zombie
139513 	stopped and then resume just one thread with scheduler-locking or
139514 	non-stop, and that thread exits the process.  I also played with
139517 	difference compared to looking at /proc/PID/status, with respect to
139521 	deal with it.  Which means, going back to approach #1.  That is the
139530 	linux_process_target::check_zombie_leaders, which will help with
139531 	keeping its comments in sync with the gdb/linux-nat.c counterpart.
139541 	messages have also been tweaked to have them synchronized with the GDB
139553 	with the gdbserver counterpart.
139594 	turns out they were necessary, we can link the testcase with "-z now"
139656 …[threads] wait_1: LWP 3273770: extended event with waitstatus status->kind = EXECD, execd_pathname…
139781 	The idea here is to replace expressions like v + 1 + 1 + 1 with v + 3.
139797 	gdb: Try searching for auto-load script using .gnu_debuglink
139798 	If an auto-load script cannot be found and objfile is a separate
139801 	parent's filename where the last component is replaced with the
139806 	if no auto-load script is otherwise found the search will be
139807 	repeated with the filename "/usr/lib/libxyz.so.debug".
139809 	This helps gdb locate auto-load scripts when debuginfo files do not have
139833 	Fix for PR gdb/20684.  When invoking MI commands with --thread and/or
139921 	the flags a compiler was invoked with), a 'char' will be either signed
139927 	There's no change to GDB with this commit, this is just adding a new
139960 	CLI version of add-inferior; the new inferior is created with no
140040 	In C, you can do this by combining the "{}" cast with an array
140056 	I chose not to allow this extension to work with based integer
140057 	literals with exponents.  That didn't seem very useful.
140061 	Fix Ada integer literals with exponents
140063 	with exponents did not work.  For example, with one form you get an
140069 	And with another form you get an incorrect value:
140079 	PR ada/28115 points out that gdb.ada/arrayptr.exp works with GNAT 12,
140080 	but fails with minimal encodings in earlier versions.
140083 	tried this with the Fedora 34 system gcc (GCC 11) and with a GCC 12
140154 	sizeof_l parameter.  The only such case seems to be correct with this
140160 	Currently, ada_decode pre-sizes the output string, filling it with 'X'
140176 	Correct issues with INSN2_ALIAS annotation for branch instructions:
140179 	  BEQ/L and BNE/L respectively with the `rs' operand equal to $0,
140182 	  BEQ and BNE respectively with the `rt' operand equal to $0,
140302 	this because, when playing with debuginfod, I saw:
140416 	with x86 cross builds I'm observing:
140418 	Error: value conflicts with instruction length `8,0x0000003f'
140438 	Avoid conflict with gnulib open/close macros.
140441 	interferes with using those names in C++ class or namespace scopes.
140630 	Fix linker tests to compile with gcc-12.
140639 …Prevent an assertion from being triggered when linking an ARM object file with incorrectly set bui…
140673 	Additionally, handle the other cases when test with RUNTESTFLAGS=
140727 	                -re "\\^error,msg=\"During startup program exited with code 127" {
140742 	message for the "During startup..." error message when running with gdbserver.
140752 	assume that it was intentionally written this way, and I've modified the code with
140906 	on a machine with a pre-release version of glib-2.34 installed:
140929 	I don't have a problem with the latter ERROR nor the UNRESOLVED
140962 	invokes gdb with -nx which ignores .gdbinit.
141042 	has "fails" that are unmatched with passes.  This patch cleans this up
141574 	fails with EBUSY.  This meant that 'info threads' would fail if any of
141603 	Asynchronous mode registers an event pipe with the core as a file
141615 	  the exit of the last child process, waitpid() will fail with ECHILD
141705 	Currently there are two problems with the detection of
141794 	In this test I send multiple commands from dejagnu to gdb with a
141804 	to write the output.  Now, mixed in with the first command output, the
141809 	This mixing of command echoing with the first command output was
141833 	the output of the first command followed by the prompt with nothing
141857 	format, with only limited support in GDB.
141869 	some symbol information that is not associated with any source file.
141958 	Notwithstanding the debatable value of conserving bug compatibility with
141961 	cursory investigation with `git blame` pinpoints commits bb00b29d7802
141976 	failure with clang that Simon pointed out.
142066 	There are quite a few ubsan warnings in gas.  This one disappears with
142086 	and because bfd_log2 rounds up, we can end up with alignment_power
142180 		(OP_E_memory): Replace havesib with ins->has_sib.
142189 	attribute with the value DW_CC_nocall to tell the debugger that it is
142200 	the following operations on a function with marked with DW_CC_nocall:
142208 	prints an appropriate message to the user and does not proceed with the
142217 	Tested on x86_64-Linux, with no regression observed.
142282 	them as "unresolved".  It also harmonizes behavior with that of
142307 	The interaction of calling with the full program-path vs.
142392 	avoiding littering the code with "#if WITH_HW".
142405 	This allows a clean test-suite-run for a build with
142427 	predicate to use together with it; checking whether a
142433 	predicates (with parameters), to be used as a conjunction.
142444 	this test fails randomly, with two different sets of common
142457 	Commit a39487c6685f "sim: cris: use -sim with C tests for cris-elf
142481 		with " -sim3", but do it conditionally for newlib targets.  Save
142539 	 program stopped with signal 6 (Aborted).
142543 	The bug behavior was with memory allocation.  With an
142622 	One possibly odd choice I made with the new hook is to pass a
142644 	The only negative change with this commit is how we currently style
142696 	PR28882, build failure with gcc-4.2 due to use of 0b literals
142698 		* elf/loongarch.h: Replace binary literals with hex.
142761 	In a typical basic executable with two memory segments, text (RE) and
142763 	last text segment page.  For example, with 64k pages and a small
142773 	example to one with 64k-1 text size, following that heuristic would
142791 	protection if an executable is running with MAXPAGESIZE pages, since
142795 	with 4k (COMMPAGESIZE) memory pages, and therefore using a larger
142807 	games with the start of the data segment to save disk space.  At
142908 	An attempt to print namelist variables results in gdb bailing out with
142916 	below, with fixed gdb.
142928 	gdb: fix until behavior with trailing !is_stmt lines
142933 	code, but might happen with gcc-compiled as well.  PR gdb/17315 relates
142934 	to this problem, as running gdb.base/watchpoint.exp with clang
142938 	with line numbers marked on the left:
142945 	we could end up with something like this:
142966 	associated with the same source line number as the previous stepping
142982 	non-statements associated with the same line number.  If they are then
142988 	0x114, the first address associated with a different line.
142994 	This patch also adds a test case that can be run with gcc to test that
143024 	bfd: Remove return with expression in void function
143025 	      * bfd.c (bfd_set_gp_value): Remove return with expression
143170 		attr-merge-arch-failed-{01,02}, replace with
143211 	Tested on glibc 2.35 build with GCC 11.2 and -Os.
143274 	Tested on x86_64-linux with no regression observed.
143318 	currently seems unnecessary given that I'm happy with the solution I'm
143323 	new-ui tty, or with gdb's standard, non-readline, mi tty.
143514 	The test for this issue sends two commands in a loop, with the first
143535 	newline included in the first read, with the second command split into
143560 	and write calls are going straight to the kernel with minimal glibc
143651 	Extend the 'cli_suppress_notification' struct with a new field,
143796 	function of the same name with the same arguments.
143803 	Remove the macro, replace with an equivalent method.
143810 	Remove the macro, replace with an equivalent method.
143817 	Remove the macro, replace with an equivalent method.
143824 	Remove the macro, replace with an equivalent method.
143927 	uses with compunit_symtab::primary_filetab.
143938 	method of compunit_symtab.  The name filetabs conflicts with the current
144006 	Fix Rust parser bug with function fields
144251 	This testcase triggers a stub sizing error with the patches applied
144403 		(sim_fpu_add): Factor out NaN operand handling with
144418 	This patch replaces the macro with a variable to track the current
144473 	may help them correlate the JIT objfiles created by with their logs /
144514 	Converting those with addr2line is somewhat involved: it requires
144519 	by looking up the symbol (with demangling if needed) and computing
144522 	It's possible that a symbol is ambigious with a hex number. In this
144555 	Starting with commit
144572 	  Program terminated with signal SIGKILL, Killed.
144701 	is done in Python.  We extended a classes __doc__ string with some
144721 	string is merged with the dynamically generated text.
144729 	commits), I was playing with making a change in the linespec parsing
144746 	This test passes on current gdb, but with my modified (and broken)
144751 	gdb: handle calls to edit command passing only a linespec condition
144753 	that the 'edit' command would suffer from the same problem.  That is,
144756 	  (gdb) edit task 123
144761 	As with the previous commit, this issue can be prevented by detecting,
144819 	This will place a breakpoint at the current location with the
144858 	comma, so, in the above case we end up with an empty linespec (between
144862 	As with the previous case, I've resolved this issue by adding an extra
144895 	skip_quote_char with `ARG + 1`, which is undefined behaviour (as ARG
144902 	nullptr, as calling is_ada_operator with nullptr can end up calling
144910 	later commit in this series, but, with this patch in place, both of
144952 	To fix this this patch introduces a special howto with
144996 	While experimenting with JIT reader API I realized that calling repr ()
145003 	objfile_filename (). This also makes consistent with the value of gdb.Objfile.filename variable.
145008 	The last updates of MIG introduced qualifying strings and arrays with
145030 	definition with no symbols associated with it.  It is used to verify
145059 	thought I'd run clang-tidy with this diagnostic on all the files (that I
145063 	is mixed up with preprocessor macros (#ifdef TUI), so I think there no
145104 	In the unmodified testcase this results in 'fails' when ran with the intel
145140 	error in bfd_set_section_contents with a .branch_lt input section
145266 	work with regcaches.  In the future these unwinders could create a
145321 	When building with clang, I run into an error:
145338 	Build on x86_64-linux with clang 13.0.0.
145344 	automatically with the right whitespace settings.  It will help me,
145345 	since I need to juggle with different whitespace settings for different
145353 	I added rules for the kinds of files I edit most often, but more can be
145386 	Using a symbol other than .TOC. with @tocbase is an extension to the
145414 	shrink).  The problem with that stopping condition is that it assumes
145475 	This leads to a GDB crash (when built with ASan, otherwise probably
145562 	Since there are some binaries with this in the wild, I think it would be
145564 	the DW_AT_data_member_location's value is -1, replace it with 0.  I
145593 	with this commit.)
145779 	PyString_FromString call failed with a UnicodeDecodeError and silently
145834 	code freely mixes writes to some parameterized stream with calls to
145845 	I think it only really makes sense to call wrap_here with an argument
145852 	gdb/python: improve the auto help text for gdb.Parameter
145954 	dealing with prefix commands.  If we create a prefix command but don't
145996 	by displaying the show_doc string with the current value appended, see
146014 	but only in the cases when the user has missed providing GDB with some
146074 	warning with GCC 12:
146093 	# with '#' will be kept; you may remove them yourself if you want to.
146134 	useful with the Python "with" statement:
146136 	   with gdb.with_parameter('language', 'ada'):
146148 	Fix another crash with gdb parameters in Python
146166 	I started this patch by fixing the problem with "endian".  Then I
146173 	nat-* files, or in remote-sim.c; and I was trying a build with all
146283 	rather than using something like fprintf_unfiltered with gdb_stdout,
146337 		(doc/bfd/index.html): Remove -I$(srcdir).  Replace bfd.texi with
146348 	Fix a proble building the libiberty library with gcc-12.
146416 	Regenerate Makefile.in files with automake 1.15.1
146417 	Regenerate Makefile.in files with the unmodified automake 1.15.1 to
146453 	Regenerate configure files with autoconf 2.69
146454 	Regenerate configure files with the unmodified autoconf 2.69 to remove
146501 	bfd: replace doc header generation with pattern rules
146502 	This unifies boilerplate rules for most files with pattern rules.
146517 	Update release makeing script with new release numbers
146572 	gdbsupport/gdb_regex.cc: replace defs.h include with common-defs.h
146583 	Avoid bad breakpoints with --gc-sections
146585 	breakpoint.  In the included test case, gdb will set a breakpoint with
146607 	Respect `set print array-indexes' with Fortran arrays
146626 	for a 5-element vector and a 5 by 5 array filled with the value of 2.
146635 	total element count as with Fortran arrays.
146639 	Respect `set print repeats' with Fortran arrays
146645 	which turned out a bit of a challenge where interacting with the `set
146669 	is unlike with the C/C++ array printer where the per-dimension element
146682 	for a 5 by 5 array filled with the value of 2.
146699 	More fun with R_PPC64_NONE found in .opd.  Fixed by the
146722 	Fixes another case where we end up with superfluous R_PPC64_NONE.
146768 	all debug_print uses that are predicated by debug_threads with
146770 	debug_exit macros with THREADS_SCOPED_DEBUG_ENTER_EXIT, which serves
146822 	gdb has some extensions and helpers for working with the libiberty
146954 	I see this error with clang-14:
146957 …/home/smarchi/src/binutils-gdb/bfd/elf64-ppc.c:13131:11: error: use of bitwise '&' with boolean op…
146961 	Fix by replacing & with &&.  But given that the check_pasted_section
147131 	Since commit ce2d3708bc8b ("Synchronize binutils libiberty sources with
147193 	x86: share yet more VEX table entries with EVEX decoding
147208 	with VMOV{H,L}PD and VMOVDDUP, and only in AT&T mode, but not checked
147224 	  valid broadcast when EVEX.b is set with a memory operand; use
147346 	Synchronize binutils libiberty sources with gcc version.
147352 	+	with digits in name.
147472 	gdb: don't use -Wmissing-prototypes with g++
147474 	compiling with g++.
147476 	Use of -Wmissing-prototypes was added with this commit:
147483 	Because clang can provide helpful warnings with this flag.
147510 	-Wmissing-prototypes with g++.  The configure script will then disable
147514 	-Wmissing-prototypes flag if we are compiling with gcc.
147537 	I've tested this with both gcc and clang and see the expected results,
147572 	Otherwise the very simple test may not be linked with libc.so at all,
147576 		* testsuite/ld-elf/dt-relr.exp: Link with --no-as-needed.
147712 	When executed with --target_board=native-extended-gdbserver, the
147713 	gdb.python/py-events.exp test errors out with
147764 	When DT_RELR is enabled, to avoid random run-time crash with older glibc
147766 	which is provided by glibc with DT_RELR support, dependency on the shared
147818 	DT_RELR is implemented with linker relaxation:
147820 	1. During linker relaxation, we scan input relocations with the same
147977 	relr.dyn section for DT_RELR.  DT_RELR is implemented with the linker
147984 	with a special glibc version symbol, to avoid random crashes of DT_RELR
147985 	binaries with the existing glibc binaries.
148046 	In a later commit I want to address an issue with the Python pygments
148049 	area can be annoying, as it requires GDB to be rebuilt with use of GNU
148191 		* testsuite/ld-elfvsb/hidden0.d: move to ld-vsb and rename with
148222 	usual GNU syntax. But we want to provide compatibility with AIX
148267 	test-environments with "long" directory names, at least once more
148272 	test consistent with actual options; but added it to the readelf
148346 	Fix multiple problems with DLL generation.
148347 	ld	* pe-dll.c (make_head): Prefix the symbol name with the dll name.
148465 	inferior exits, with this error:
148498 	of other issues with this target that makes running the full testsuite
148526 	    PASS: gdb.base/arrayidx.exp: print array with array-indexes off
148528 	    PASS: gdb.base/arrayidx.exp: print array with array-indexes on
148534 	    PASS: gdb.base/arrayidx.exp: print array with array-indexes off
148537 	    PASS: gdb.base/arrayidx.exp: print array with array-indexes on
148619 	Also change some messages with the pattern "(timeout) $testname" into
148752 	Fix by placing the sections with duplication in with_test_prefix blocks.
148811 	- Replace an explicit GDB restart sequence with a call to clean_restart.
148889 	developers test the auto-completion capabilities of GDB.
148923 	This approach comes with a problem that we encounter when running the
148978 	various decimal floating point types with a loop to programmatically
149210 		* po/fr.po: Same.
149211 		* po/ru.po: Same.
149212 		* po/uk.po: Same.
149216 	RISC-V: update docs for -mpriv-spec/--with-priv-spec for 1.12
149229 		* po/fr.po: Same.
149230 		* po/ru.po: Same.
149231 		* po/uk.po: Same.
149281 	The procedure declaration lines can get pretty long with all of the
149320 …Revert previous delta to debug.c.  Replace with patch to reject indirect types that point to indir…
149419 	rather than printing the same output with an empty string as
149428 	This introduces target_announce_attach, by analog with
149445 	sub-commands, along with a one line summary of what each does.
149448 	change is acceptable as the new behaviour is more inline with other
149451 	This change will conflict with Tom's change here:
149478 	I believe this also fixes a possible bug with a missing 0-termination
149497 	'verbose' is on and when switching the "expected" language in auto
149535 	Neither non-64-bit code nor uses with a non-zero offset from a symbol
149663 	doc: Replace =frame-interp with =frames-interp
149668 		* doc/debug.options.texi: Replace =frame-interp with
149845 	gdb_internal_backtrace_1 with a check of GDB_PRINT_INTERNAL_BACKTRACE.
149850 	The patch to fix paging with redirection caused a regression in the
149882 	The issue is more general and probably affects other targets with multiple
150048 	Improve thin archive member error message with:
150086 	in clone-inferior) introduced a testcase that fails when testing with
150106 	Tested on x86_64-linux with native-extende-gdbserver and unix boards.
150194 	Symbols names ending in \ are in principle not expressable with that
150313 	[gdb/testsuite] Handle for loop initial decl with gcc 4.8.5
150314 	When running test-case gdb.threads/schedlock-thread-exit.exp on a system with
150326 	Tested on x86_64-linux, both with gcc 4.8.5 and gcc 7.5.0.
150353 	the files whose mode is changed by the script, plus a build with
150355 	out */po/*.pot which we don't update frequently.
150357 	The copy of cgen was with commit d1dd5fcc38ead reverted as that commit
150370 	replace with explicit signed types.  This matches what was done in the
150391 	This replaces want64 with enable_64_bit_bfd which was already being
150491 	ld-x86-64: Pass options to linker with "-Wl,"
150492 		* testsuite/ld-x86-64/x86-64.exp: Pass options to linker with
150678 	Fix logging redirection bug with pager
151000 	Bug PR gdb/28405 reports a regression when using attach with an
151004 	The regression was introduced with this commit:
151031 	In extended_remote_target::attach we create a new thread with a call
151042 	new thread to be added with a call to add_thread_silent.  We can now
151066 	but also, we now run with different packets disabled in gdbserver.  In
151069 	non-stop modes now for extra coverage, we also run the tests with
151261 	Now, if we have a class with virtual bases we will fail quicker, and
151324 	mi-async' (with a similar difference for the show/-gdb-show).
151439 	it, since the generated code is in conflict with -momit-lock-prefix=yes,
151537 	async mode disabled (with 'maint set target-async off'), but the async
151550 	There should be no user visible changes with this commit.
151556 	test with 'maint set target-async off' in place.  Unfortunately I ran
151560 	In my particular case I was actually running with:
151638 	::getpkt_or_notif_sane_1 with 'gdb_assert (rs->cached_wait_status ==
151642 	I did play with using some kind of scoped restore to backup, and
151645 	problem with this is that, where the ::cached_wait_status flag is
151701 	of the ::stop_reply_queue with how we used to handle the
151743 	For testing I've been running test on x86-64/GNU Linux, and run with
151745 	For each board I've run with the default GDBFLAGS, as well as with:
151750 	Though running with the above GDBFLAGS is clearly a lot more unstable
151752 	failures with my patch, except, with the native-extended-gdbserver
151823 	The new gdbarch.sh approach will be to edit a Python file, rather than
151869 	loops in `fortran_array_walker'.  The operation is exactly the same with
151989 	not when presented with fuzzed object files.
152009 	Fix AVR assembler so that it creates relocs that will work with linker relaxation.
152152 	RISC-V: Support svinval extension with frozen version 1.0.
152200 	sim: fix mingw builds with replacement gnulib open
152211 	x86_64-linux-gnu host:  testcase pr25490-5.s was failing with
152232 	gdb: re-format with black 21.12b0
152242 	gdb: re-format with black 21.9b0
152258 	per run" with PIEs and/or different compilers.  I've closed similar
152263 	an error string instead.  The address of the string varies with PIE
152281 	GDB/GDBserver, since the thread library doesn't play well with that setup.
152283 	If you try to run a statically-linked GDB built with threading, it will crash
152286 	This new option is also convenient when debugging GDB in a system with lots of
152370 	... trying to start an application with libinproctrace.so loaded
152401 	When building gdb with  on AArch64 with g++ 11.1.0 (and some preceding
152445 	bfd: fix -Wunused errors with clang 13+
152480 	Just give this class a new name, more inline with the name of the
152482 	mi-cmds.c inline with this new naming scheme.
152508 	update a comparison of a pointer to 0 with a comparison to nullptr,
152519 	std::map.  Not only is replacing a custom container with a standard
152552 	with the above two linker scripts.
152584 	Adjust linker tests for linker configured with --disable-separate-code:
152606 	as expected.  The issue appears to be with the kernel not returning the
152614 	While working on a Python script, which was interacting with a remote
152631 	Then I would work with items in foo_t.array, like:
152652 	end of an array, when working with zero element arrays, or when
152695 	fields, which were added with this commit:
152714 	Replace the direct assignments to current_thread with
152888 	gdb: only include mips and riscv targets if building with 64-bit bfd
152891 	problem, I configured with `--enable-targets=all
152905 	building with a 64-bit bfd.
152913 	So, though we can build most of GDB just fine for riscv and mips with
152921 	fine with the configure options given above.
152932 	GDB to build when configured with --enable-targets=all, and when using
153008 	Don't edit bogus sh_link on reading relocatable objects (Oracle fix)
153085 	Fix this, seen when building with clang 14:
153097 	Fix these, seen when building with clang 14:
153137 	        along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
153167 	with ELFv2 and other architectures.
153171 	[gdb/testsuite] Fix gdb.base/maint.exp with -readnow
153187 	Tested on x86_64-linux with native and target board readnow, as well as
153192 	[gdb/testsuite] Fix gdb.base/include-main.exp with -readnow
153205 	Fix this by skipping the check with -readnow.
153207 	Tested on x86_64-linux, with native and target board readnow.
153212 	* To be consistent with -march option, removed the "=" operator when
153229 		(riscv_update_subset): To be consistent with -march option,
153257 	While working with pending fork events, I wondered what would happen if
153259 	pending fork event.  What happens with the fork child, which is
153295 	while it is stopped with a pending fork event.  In order to verify that
153304 	TARGET_WAITKIND_SIGNALLED' failed.).  When detaching a thread with a
153313 	instead (since the thread was not stopped with a signal to begin with).
153347 	Suppose we continue past a fork with "follow-fork-mode == child" &&
153381 	 - Replace is_pending_fork_parent with is_fork_status, which just
153520 	This change inverted the sense of the test, which causes failures with
153524 	also tested it using the AdaCore internal test suite, with
153580 	call a gdb.Value might already be associated with a gdb value object,
153620 	GDB compiled on a 32-bit arm target, with --enable-targets=all.  Then
153743 	If a.so contains an SHT_RELR section, objcopy a.so will fail with:
153789 	replacing it with a simpler use of std::string.
153804 	maintenance commands, rename them accordingly (with the maint_ prefix),
153884 	 2 |       16     along with this program.  If not, see <http://www.gnu.org/|
153896 	 1 |       16     along with this program.  If not, see <http://www.gnu.org/|
153968 	we have this call sequence (with %ebx setup to point to the .got.plt):
153990 	When instead doing an inferior call to malloc (with nosharedlib to force
153992 	with the non-PIE exec, we have the expected:
154001 	But with the PIE exec, we run into:
154019 	Fixes this failure with target board unix/-m32/-pie/-fPIE reported in
154025 	Tested on x86_64-linux, with target board unix/-m32 and unix/-m32/-fPIE/-pie.
154032 	When running test-case gdb.base/cached-source-file.exp with target board
154050 	On openSUSE Leap 42.3, with system compiler gcc 4.8.5 I run into:
154087 	the output_target when dealing with the input target.  Fix that too.
154099 	script, to a library specified with -l, or to an element of a thin
154102 		* ldlang.c (open_output): Exit with error on output file matching
154118 	X86_64 with no regressions.
154144 	Add a new file lib/precise-aligned-alloc.c with functions
154152 	Tested on x86_64-linux, with both gcc and clang.
154157 	When running test-case gdb.arch/i386-avx.exp with clang I ran into:
154183 	Tested on x86_64-linux, with both gcc and clang.
154253 	Avoid implicit include deps with this to help untangle sim headers
154257 	Avoid implicit include deps with this to help untangle sim headers
154261 	Avoid implicit include deps with this to help untangle sim headers
154281 	handle name string wasn't freed.  When register a file handler with an
154286 	Fix this by allocating file_handler with new, deleting it with
154323 	replacing direct assignments with methods, and arranging for it to own
154434 	 - separate each entry with a newline, to visually separate them
154435 	 - style filenames with the filename style
154438 	A header now looks like this, with the compunit_symtab name added (and
154537 	Add a test for the new function, testing both with arrays of a trivial
154563 	While playing with some code creating target_waitstatus objects, I was
154582 	pretty much the same thing, with less new code.
154597 	are not paired with an error string, but we had an assert that the
154655 	which, when run with the address sanitizer enabled, highlights the
154665 	The gdb.server/server-connect.exp now runs cleanly with the address
154670 	libctf: workaround automake bug with conditional info pages
154672 	pages based on the GNU standard behavior of shipping info pages with the
154679 	its own extended generation target.  I'll follow up with the automake
154690 	The bpf sim doesn't work with a 32-bit bfd after all.
154716 	- use x86_64 machine with avx512 support
154717 	- compile a hello world with -m32 to a.out
154718 	- start a gdbserver session with a.out
154744 	- it adds 16 additional 512-bit wide zmm registers (with corresponding ymm and
154759 	Fix this by replacing the constants with variables that have the appropriate
154762 	Tested on x86_64-linux with native and unix/-m32.
154772 	string to see if the test program is compiled with DWARF debug
154773 	information.  Since everything is compiled with DWARF 4 or 5 nowadays,
154822 	(similar to what it does with floats, for instance).
154903 	store the value of into a buffer with the right register size.
154915 	The same happen with the "return" function, but the other way around.
154965 	types, then in gdb, printing the result of a call to call_fp1 with a
155082 	This becomes useful with a follow-on patch to check that code follows
155222 		and current_insns with num_added_insns and num_allocated_insns.
155288 	Allow the --visualize-jumps feature to work with the AVR disassembler.
155294 	gdb, include: replace pragmas with DIAGNOSTIC macros, fix build with g++ 4.8
155296 	Replace some "manual" pragma diagnostic with some DIAGNOSTIC_* macros,
155306 	DIAGNOSTIC_POP seems to misbehave with g++ 4.8, where we see these
155324 	out of nowhere and cause a build error if building with future
155415 	The "info source" command, with a DWARF-compile program, always show
155425 	    Compiled with DWARF 2 debugging format.
155437 	    Compiled with DWARF 5 debugging format.
155518 	When running test-case gdb.arch/i386-pkru.exp on a machine with "Memory
155612 	The test completes with 1 expected pass and no failures.
155744 	I noticed this with a test that used "zero" as a register alias
155758 	and with the input scrubber, we'll only keep whitespace after
155800 	with 'p', but not with 'i':
155805 	The new approach of using 'O' works fine with these cases.  I've added
155812 	[gdb/testsuite] Fix gdb.base/style.exp with stub-termcap
155813 	When running test-case gdb.base/style.exp with a gdb build using
155856 	module.  When running the Python tests with a GDB built against Python
155900 	code if we compiled GDB with a 32-bit bfd_vma.  Notice we return
155922 	However, there is one weakness with this strategy; if GDB broke such
155926 	for the default architecture (the one selected by "auto") we _only_
155987 	So:      "command can only be used with remote target"
155999 	One way to show the problem with this is if we try to read the auxv
156064 	RISC-V: The vtype immediate with more than the defined 8 bits are preserved.
156237 	strings: Replace references to -u option with references to -U.
156244 	psymbol_functions::expand_symtabs_matching calling expansion_notify with a
156262 	The includer of ps is a shared symtab for a partial unit, with as user:
156321 	[gdb/testsuite] Fix gdb.dwarf2/dw2-lines.exp with -m32
156322 	When running test-case gdb.dwarf2/dw2-lines.exp with target board -unix/-m32,
156579 	too.  A lot of the C code is written such that it works with either
156586 	So lets create a few stub files that we can do compile tests with
156641 	sim: testsuite: replace global_ld_options with LDFLAGS_FOR_TARGET
156643 	sim-specific settings with the dejagnu common LDFLAGS_FOR_TARGET and get
156672 	    [gas] Fix file 0 dir with -gdwarf-5
156674 	1. Replace i with j in
156693 	sim: testsuite: replace global_as_options with ASFLAGS_FOR_TARGET
156695 	sim-specific settings with the dejagnu common ASFLAGS_FOR_TARGET and get
156701 	The test-case gdb.ada/dgopt.exp uses the -gnatD switch, in combination with
156764 	confusion with dead code.
156818 	[gas] Fix file 0 dir with -gdwarf-5
156889 		* aarch64-asm.c: Replace assert(0) with real code.
156896 	Basic ambiguity detection assumes that when 2 fields with the same name
156952 	differences in Makefile.in are seen with a proper regeneration.  One
156956 	but it's nicer with a line between those rules.  Moving the rule
156963 		* po/BLD-POTFILES.in: Regenerate.
156964 		* po/SRC-POTFILES.in: Regenerate.
156969 		* po/fr.po; Updated French translation.
157001 	async mode disabled (with 'maint set target-async off'), but the async
157014 	There should be no user visible changes with this commit.
157095 	The test must be done with the shared object and not with the object
157178 	on Linux with other architectures, though, and it seems like a
157209 	The problem with this change is that XCNEWVEC calls xcalloc, which in
157240 	When readline development package is missing make fails with
157256 	However this target is not valid for use with gas but only with objcopy.
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.
157486 	RISC-V: Replace .option rvc/norvc with .option arch, +c/-c.
157487 	Since the .option rvc/norvc directives are obsolete, replace them with
157495 		rvc/norvc with .option arch, +c/-c.
157514 	A build error on x86_64 with x32 abi was reported here (
157548 	[gdb/symtab] Support .debug_line with DW_FORM_line_strp
157584 	Looking with readelf at the 0x1e0 entry, we have:
157610 	Note: the described test-case does trigger this complaint (both with and
157627 	Add a new target board dwarf64.exp, that runs test with -gdwarf64.
157640 	For now, make the v5 directory and filename tables work with the v4 type of
157643 	This will need to be properly fixed with an intrusive fix that changes how
157694 	up a make check with RUNTESTFLAGS like this to catch all dwarf assembly
157766 	assembler options with cpu_option -- the option and its value are
157767 	always separated by an =.  This is not the case with v850.  So tweak
157798 	     because it was inconsistent with how other operands were initialized.
157807 	gdbsupport: fix array-view compilation with c++11 && _GLIBCXX_DEBUG
157808 	When building with -std=c++11 and -D_GLIBCXX_DEBUG=1, we get some errors
157815 …lice(gdb::array_view<T>::size_type, gdb::array_view<T>::size_type) const [with T = unsigned char; …
157817 …lice(gdb::array_view<T>::size_type, gdb::array_view<T>::size_type) const [with T = unsigned char; …
157831 	When building gdb with g++ 4.8.5, I ran into:
157839 	we're excercising the enable_source_highlight=auto scenario. ]
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
157855 	In the enable_source_highlight=auto scenario, this allows the build to skip
157924 	[gdb/testsuite] Fix 64-bit dwarf test-cases with -m32
157925 	When running test-case gdb.dwarf2/loc-sec-offset.exp with target board -m32,
157952 	Tested on x86_64-linux with target board unix/-m32.
158032 	type = class Cfoo<int> [with DataT = int] {
158049 	type = class Cfoo<int> [with DataT = int] {
158069 		* gdb.cp/templates.cc: 	New template class Cfoo with const,
158153 	entry, STO_RISCV_VARIANT_CC, to indicate there are symbols with the
158226 …data-directory data-directory -iex set height 0 -iex set width 0 -iex set auto-connect-native-targ…
158233 	(gdb) FAIL: gdb.base/dprintf-execution-x-script.exp: load and run script with -x
158248 	using the native target via "-iex set auto-connect-native-target off".
158270 	gdb: fix array-view-selftests.c build with g++ 4.8
158271 	When building with g++ 4.8, I get:
158285 	gdb: fix ia64-tdep.c build with g++ 4.8
158286 	When building with g++ 4.8, I get:
158300 	Later compilers don't have a problem with that, so I suppose that the
158392 	Because the format string passed by the caller is prepended with a "%s:"
158408 	The call to proc check_continue "execve" is removed and replaced with
158436 	Tested on Power 10 ppc64le-linux with no regressions.
158446 	are the result of calling do_test three times with different arguments.
158560 	with f/d/q.
158790 		(REGNUMS): New macro. Regs with suffix.
158791 		(REGSET16S): New macro. 16 regs with suffix.
158924 		assertion with a warning message.
158944 	with the compiler complaining about a missing class name after the colon.
158975 	RISC-V: Support rvv extension with released version 1.0.
159006 		and stores with EEW 64 cannot be used when zve32x is enabled.
159065 	read_core_file_mappings_pre_loop_ftype.  Intended for use with
159074 	settings.  This allows replacing the custom cris @exedir@ with it.
159076 	sim: cris: replace @srcdir@ test extension with $srcdir/$subdir
159078 	so replace the custom @srcdir@ logic with those.  Since the replace
159093 	all pass out of the box with little to no configuration so that they
159097 	test logic with the common sim test logic.
159129 	to use gdb::array_view"), I believe I made a mistake with the length of
159303 	Provide explicit control over the program's environment with the
159333 	but most ports don't do anything with them.  A few will use ad-hoc
159350 	Add testcases for Scalar Crypto extension, with total testcase contain all
159432 	riscv_supported_std_ext, to make the order check right with
159537 	to use with git send-email.  I'm planning to use this for my RISC-V
159558 	To understand what it does, I disabled this bit and ran with GDB_DEBUG=infrun,
159607 	Tested test-case gdb.base/foll-vfork.exp with and without GDB_DEBUG=infrun.
159614 		case ld was configured with --enable-textrel-check=error.
159671 	Deal with full path in .file 0 directive
159715 	Add quiet build support and make sure it's removed with `make clean`.
159717 	sim: cris: replace custom "dest" test field with new --argv0
159826 	Fix build with current GCC: EL_EXPLICIT(location) always non-NULL
159827 	Compiling GDB with current GCC (1b4a63593b) runs into this:
159878 	Sync Makefile.tpl with GCC
159879 		* Makefile.tpl: Sync with GCC.
159885 	This code triggers -Werror=switch-bool warnings with <=gcc-5 versions.
159902 	gdb_test "$enter_cmd to handler" with a gdb_test_multiple test.  The multiple
159920 	Patch has been tested on x86_64-linux and ppc64le-linux with no test failures.
159976 		* po/POTFILESin: Regenerate.
159987 	 - launch inferior with multiple threads
159994 	 - GDB hangs, not showing the prompt, impossible to interrupt with ^C
160020 	threads with a pending event, which makes us ignore the event.  But these
160035 	are resumed with a pending status, which is what we want.
160042 	When building with clang 13 (and -std=gnu++17 to work around an issue in
160046 	src/gdbsupport/new-op.cc:102:1: error: function previously declared with an \
160047 	  explicit exception specification redeclared with an implicit exception \
160065 	[gdb/build] Fix build with -std=c++11
160066 	When building with -std=c++11, we run into two Werror=missing-declarations:
160088 	Tested on x86_64-linux, with gcc 7.5.0, both without (implying -std=gnu++14) and
160089 	with -std=c++11.
160103 	aforementioned commit, and passes with the commit.  Both with assembly
160112 	problem that we probably dump an object with c.nop instructions, but
160223 	Since gcc dropped support for a.out starting with 4.4.0 in 2009, it's
160228 	sim: io: tweak compiler workaround with error output
160230 	to use %s with an empty string to avoid the compiler warning but not
160234 	There's no need to sync testutils.inc with remote hosts.  The one
160241 	accomplish the same thing with the -Ttext=0 flag, so switch to that
160259 	I tested this by running the gdb.dwarf2 tests both with and without
160307 	problem will always trigger with this test-case.
160337 		* readelf.c (print_symbol): Replace uint with unsigned int.
160346 	Previous flags were aimed to be run with XLC.
160347 	Nowadays, only GCC is being tested with GNU toolchain. Moreover,
160418 	This commit fixes Bug 28308, titled "Strange interactions with
160425 	which I've created along with this bug fix.  The name of the new test
160429 	start with 'dp-bug' instead of 'dprintf-execution-x-script'.
160469 	with three 'Breakpoint 2' messages.  This is the correct output.
160605 	return, i.e. prior to executing the command(s) associated with the dprintf
160654 	list associated with the breakpoint, regular breakpoints will place
160737 	gdb.debuginfod/fetch_src_and_symbols.exp: fix when GDB is built with AddressSanitizer
160743 	                 --with-auto-load-dir=$debugdir:$datadir/auto-load
160744 	                 --with-auto-load-safe-path=$debugdir:$datadir/auto-load
160748 	process outputs on stderr.  When GDB is built with ASan, it prints some
160901 	Then with the current interface nothinng prevents this usage of
160923 	and a size.  The valid type pointed to that can be used with this
161024 	is objfile-independent (can work with only the shared per-bfd data).
161033 	it as something to remember that adds cognitive load.  Also, with C++,
161072 	Goes with commit 68bbb9f788d0
161105 	source does this, and breaks with some mingw targets, so punt the
161108 	sim: sh: fix isnan redefinition with mingw targets
161115 	with our local usage here.  Undefine the system one to fix building
161129 	sim: sh: fix uninitialized variable usage with pdmsb
161149 	sim: sh: rework register layout with anonymous unions & structs
161151 	to fix a long standing issue with the SH register layout.  The use
161210 	This clashes with some of our old code that declares yyerror to return
161303 	open fails with EACCES or ENOENT.  When it happens, GDB just tries
161312 	ends up with no address space associated, so a subsequent read/write
161338 	operation until the exec event is consumed, with this kernel commit:
161372 	Replaces a hard coded line number with a use of gdb_get_line_number.
161380 	So, I've marked the 'return 0' with a comment, and now the test will
161384 	will only pass with the HP compiler, followed by an additional comment
161385 	from 2000 saying that the tests now pass with GCC.
161406 	PR28530, Hang in objdump on machine with 196GB RAM
161408 	header with an enormous size, I noticed that decompress_contents is
161452 	with respectively the default arguments "on" and "off".
161491 	setting with a getter and a setter.
161523 	Revert "bfd: Always check sections with the corrupt size"
161528 	bfd: Always check sections with the corrupt size
161529 	Always check sections with the corrupt size for non-MMO files.  Skip MMO
161535 		sections with the corrupt size.
161581 	files with missing prototypes which cause compiler errors.  In the
161627 	require this be the "new" combined tree with a ../common/ dir.  This
161658 	compiled with ASan, compared to a GDB compiled without ASan.  Some of
161660 	it exits, and the fact that it makes it exit with a non-zero exit code.
161674 	    gdb.base/with-mf.exp
161684 	While looking at an apparently malformed executable with
161721 	Currently for a binary compiled normally (without -fsanitize=address) but with
161777 	levels will automatically discard them.  But building with -O0 will
161894 	On powerpc64le-linux, with test-case gdb.arch/powerpc-addpcis.exp I run into
161900 	Program terminated with signal SIGILL, Illegal instruction.^M
161925 	[gdb/testsuite] Fix stepi test-cases with unix/-m32/-fPIE/-pie
161926 	When running test-case gdb.base/step-indirect-call-thunk.exp with target board
161938 	In contrast, with unix/-m32 we have instead:
161975 	[gdb/doc]: Updated manpages to be consistent with help
161976 	Updated manpages to be consistent with help information provided by the
162035 		* readelf.c (arm_attr_tag_CPU_arch): Update with
162039 		* arm.h: Update TAG_CPU_ARCH_ enums with correct values.
162049 		* testsuite/gas/arm/attr-march-all.d: Update test with v9.
162053 		* elf/arm.h Update TAG_CPU_ARCH_ defines with correct values.
162055 		(ARM_ARCH_NONE): Updated with arm_feature_set.core size.
162095 	Fix a few printf warnings in sim-main.c, and then we're left with only
162115 	sim: or1k: build with -Werror
162145 	defines with printf formats.
162198 …invariant: command 'info set debuginfod' help doc first line is not terminated with a '.' character
162199 …help doc broken invariant: command 'set debuginfod' help doc first line is not terminated with a '…
162200 …ken invariant: command 'show debuginfod' help doc first line is not terminated with a '.' character
162268 	sim: erc32: use silent build rules with sis linkage
162366 	never worked properly, but still produce coff-x86_64.o with
162401 	gdb: fix gdb.gdb/unittest.exp with C++17 compiler
162402 	On a machine with gcc 11, I get:
162407 	That's because when compiling with C++ >= 17, we use the standard
162421 	Refer to this new section in the description of the '--with-debuginfod'
162435 	    This GDB supports auto-downloading debuginfo from the following URLs:
162459 	If GDB is not built with debuginfod then these commands will just display
162470 	Remove TYPE_FIELD_DWARF_BLOCK, replace with type::field +
162478 	Remove TYPE_FIELD_STATIC_PHYSADDR replace with type::field +
162486 	Remove TYPE_FIELD_STATIC_PHYSNAME, replace with type::field +
162494 	Remove TYPE_FIELD_ENUMVAL, replace with type::field +
162502 	Remove TYPE_FIELD_BITPOS, replace its uses with type::field +
162510 	Remove TYPE_FIELD_LOC_KIND, replace its uses with type::field +
162518 	Remove FIELD_DWARF_BLOCK, replace its uses with field::loc_dwarf_block.
162525 	Remove FIELD_LOC_KIND_PHYSADDR, replace its uses with
162533 	Remove FIELD_STATIC_PHYSNAME, replace its uses with field::loc_physname.
162540 	Remove FIELD_ENUMVAL, replace its uses with field::loc_enumval.
162547 	Remove FIELD_BITPOD, replace its uses with field::loc_bitpos.
162554 	Remove FIELD_LOC_KIND, replace its uses with field::loc_kind or
162617 	arch with a 64-bit address size when bfd_vma is 32-bit.
162629 	[gdb/build] Fix build with --disable-unit-tests
162630 	A build with --disable-unit-tests currently run into:
162643 	maintenance_selftest_completer with GDB_SELF_TEST, such that the "-verbose"
162683 	obcopy vs. files with silly section alignment
162733 	Hence the comment about registers definitions being inline with glibc.
162852 	with a gdb configured without python:
162866 	Tested on aarch64-linux (with python support disabled) and x86_64-linux (with
162892 	[gdb/symtab] Handle DW_AT_string_length with location list
162903 	When compiling with optimization level -O1 and printing the type of
162916 	while with -O0 we have instead:
162960 	not emitted when built with debug option. If the anonymous union is
162989 		* aoutx.h: Replace use of INLINE with inline.
162999 	ASSERT in empty output section with address
163029 	Fix watchpoints with multiple threads on Windows
163044 	On OBS I ran into this failure with test-case
163126 	It does not happen with the programs included with binutils or GDB,
163128 	happen with external software, e.g.:
163138 	prevents this from happening by linking in libbfd with an explicit file
163141 	with a suitable library search path specified via `-L', as it would be
163148 	not at least with our current libtool incarnation, as directly referring
163150 	with no link-time reference to the installation directory other than to
163185 	avoid being placed between other note sections with different alignments.
163214 	and then indexes it with a non-sensical index.
163218 	that when GDB is built with _GLIBCXX_DEBUG, accesses to the array_view
163300 	structure member with a nonrepresentable type caused an abort with
163340 	ld by default (and always, unless adjusted with a hand-rolled linker
163410 	with a parent archive member named something other than ".ctf", still
163411 	contained with all its children in a single .ctf section) had no support
163425 	of the objdump output and thus we'll end up with a shared dump
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.
163707 	I tested this with 'make install' followed by 'make uninstall', then
163722 	On openSUSE Tumbleweed with glibc-debuginfo installed I get:
163817 	felt a little random that the Membuf creation code should live with
163824 	Most of the code is moved directly from py-inferior.c with only minor
163825 	tweaks to layout and replacing NULL with nullptr, hence, I've left the
163920 	not finished with the relaxation process so in some cases - such as the
163999 	after.  Or, since that GDB was built with ubsan, this nice error
164103 	Build on x86_64-linux, tested with all .exp test-cases that contain
164117 	On PowerPC, the test passes when compiled with no optimization but fails
164118 	with all levels of optimization due to gdb stopping in the prolog.
164180 		(GET_DYNAMIC_NAME): Delete.  Replace with..
164219 	with zero sym on the call might be a solution, but current linkers
164254 	Make c-exp.y work with Bison 3.8+
164280 	The test-case is fragile, because (f.i. with -flto) it cannot be guaranteed
164307 	fails with EILSEQ.  I suspect that "UTF-32" is being interpreted as
164419 	which was originally dwarf2_per_objfile::int_type, with ctf_type_size bits.
164517 	Split .got into two piece, one with the header and entries for small
164518 	model got entries, the other with entries for medium/large model got
164532 		* powerpc.cc (enum Got_type): Extend with small types, move from
164596 	where x is an array with unknown bounds, we get:
164622 	PPC fix for stfiwx instruction (and additional stores with primary opcode of 31)
164683 	[gdb/testsuite] Fix gdb.fortran/call-no-debug.exp with native-gdbserver
164684 	When running test-case gdb.fortran/call-no-debug.exp with target board
164702 	When running with target board native-gdbserver, we run into a number of FAILs
164708 	- guarding some tests in the test-case with use_gdb_stub == 0.
164721 	The two tests are instances of the same test, with different values for
164725 	This is due to using a gdb_test nested in a gdb_test_multiple, with the inner
164741 	[gdb/testsuite] Fix gdb.base/batch-exit-status.exp with native-gdbserver
164742 	When running test-case gdb.base/batch-exit-status.exp with target board
164748 	  -ex "set auto-connect-native-target off" \
164759 	"set auto-connect-native-target off", which makes that the last command to
164769 	When running test-case gdb.arch/i386-mpx.exp with target board
164906 	Built and regtested with a simulator.
164951 	(with glibc 2.34) I run into:
165013 	Before the commit the main file was compiled with debug info, and the two
165021 	After the commit, all were compiled with debug info, and consequently, there
165023 	running the test-case with target boards readnow and cc-with-debug-names.
165041 	with:
165047 	Tested on x86_64-linux, both with native and target board readnow.
165052 	When running test-case gdb.base/with-mf.exp with target board readnow, I run
165055 	FAIL: gdb.base/with-mf.exp: check if index present
165081 	    fail "Unable to call gdb-add-index with a symlink to a symfile"
165086 	However, it's possible that the gdb-add-index also fails with a regular
165097 	    # Valgrind gdbserver requires gdb with xml support.
165107 	Tested on x86_64-linux, both with and without a trigger patch that forces
165215 	Testing with check-readmore showed these regressions:
165217 	FAIL: gdb.base/bp-cmds-continue-ctrl-c.exp: run: stop with control-c (continue)
165218 	FAIL: gdb.base/bp-cmds-continue-ctrl-c.exp: attach: stop with control-c (continue)
165229 	[gdb/testsuite] Fix fortran module tests with stressed cpu
165234 	in conjunction with:
165241 	- "set auto-solib-add off" to avoid symbols of shared libs
165264 	[gdb/testsuite] Fix gdb.base/info-types-c++.exp with stressed cpu
165265 	When running test-case gdb.base/info-types-c++.exp in conjunction with:
165274 	Fix this by setting auto-solib-add to off.
165280 	[gdb/testsuite] Fix gdb.base/info_sources_2.exp with check-read1
165281 	When running test-case gdb.base/info_sources_2.exp with check-read1, I run
165296 	[gdb/testsuite] Fix gdb.mi/gdb2549.exp with check-read1
165297 	When running test-case gdb.mi/gdb2549.exp with check-read1, I run into:
165303 	478e490a4df "[gdb/testsuite] Fix gdb.mi/gdb2549.exp with check-read1".
165309 	[gdb/testsuite] Fix gdb.base/bt-on-error-and-warning.exp with check-read1
165310 	When running test-case gdb.base/bt-on-error-and-warning.exp with check-read1,
165345 	When running test-case gdb.dwarf2/dw2-restrict.exp on openSUSE Leap 15.2 with
165354 	This is due to using a hardcoded .S file that was generated with -fno-PIE.
165368 	[gdb/testsuite] Fix gdb.threads/check-libthread-db.exp with glibc 2.34
165370 	Tumbleweed (with glibc 2.34) I get:
165399 	[gdb/testsuite] Fix gdb.guile/scm-type.exp with gcc 4.8
165408 	but with gcc 4.8.5, I get instead:
165428 	and with gcc 7.5.0, we have instead:
165443 	array member declared with size 0, regardless of how the debug info
165470 	bitpos location with value 0.  While writing this patch, I tried to make
165570 	XCOFF archive with one member pointing to itself, which results in
165573 	The use-after-free with "objdump -r" happens like this:  The first
165588 	is overkill.  If someone deliberately fuzzes an XCOFF archive with an
165691 	 Program terminated with signal SIGTRAP, Trace/breakpoint trap.
165710 		* coff-mips.c (mips_adjust_reloc_in): Replace abort with error
165754 	can't safely catch all such cases by comparing with file size, for
165923 	to GDB's real inferior object.  We therefore end up with a system that
165981 	  memory associated with the gdb.Inferior object, which is what we
165994 	Following 2 test points are failing with clang compiler
166006 	Tested on x86_64-linux with gcc and clang.
166020 	prompt, or if GDB is run with '-batch' and has processed all of the
166025 	with.
166150 	Consider test-case gdb.trace/entry-values.exp with target board
166183 	test-case, with debug info for foo and bar, but not for main.
166246 	called with a pointer to the pc field (as passed into htab_find_slot) and a
166261 	Tested on x86_64-linux, both with and without a trigger patch that moves pc to
166294 	The problem with this is, the file bfd-in3.h is generated into the bfd
166303 	TARGET_WORD_SIZE ends up being defined, but with no value because the
166318 	list all the targets that the current build supports.  This aligns with
166396 	with the appropriate commands.  This patch proposes that a setting can
166400 	The callbacks functions can be used to retrieve or change the value with
166408 	the way to access it is (through MI, Python, Guile, the "with" command
166415 	Tested on GNU/Linux x86_64 with no regression observed.
166429 	easier to write than with C strings.  And they avoid having to do any
166432 	Another interesting reason is that, with `char *`, nullptr and an empty
166443 	representing an empty string setting, that is with an empty string.
166467 	allocate (with new) an std::string that is owned by the param_smob (in
166492 	shown.  This is achieved with the void* VAR member which points to the
166497 	is the storage type associated with a given VAR_TYPES in order to do
166517 	that is coherent with the setting's var_type.  This is achieved by
166524 	instantiating the member functions with bool will yield something
166569 	VAR and VAR_TYPES members of the struct are replaced with a
166580 	  pascm_param_value and gdbpy_parameter_value have been replaced with a
166585 	Tested on GNU/Linux x86_64, with no regression noticed.
166597 	symbols that start with "SIG" so as to automatically include any
166604 	with that same value (since the range of valid signals tend to be
166606 	never be that small).  But with recent glibc changes that make this
166742 	Change how rnglists and loclists procs to align them with how procs for
166754 	assembler, I made it with nested procs, for example proc "table" inside
166770 	 - Prefix them with "_rnglists_" or "_loclists_".
166819 	with a hard-coded "/bin/sh" as its argument.  We've had 'get_shell'
166941 	behavior with the rest of the testsuite.
167006 	With running test-case gdb.debuginfod/fetch_src_and_symbols.exp with target
167010 	compiler exited with status 1
167015 	Replace the FAIL with the usual:
167025 	When running test-case gdb.base/info-os.exp with target board unix/-bad, I run
167054 	When running test-case gdb.dwarf2/dw2-opt-structptr.exp with target board
167073 	When running test-case gdb.base/structs.exp with target board unix/-bad, I
167091 	When running test-case gdb.base/cvexpr.exp with target board unix/-bad, I get:
167101 	Fix this by preparing another executable compiled with nodebug, and using
167128 	When running test-case gdb.base/call-sc.exp with target board unix/-bad, I
167160 	Replace these untested messages in gdb.mi/*.exp with the usual "failed to
167257 …FAIL: gdb.multi/multi-term-settings.exp: inf1_how=attach: inf2_how=attach: stop with control-c (SI…
167313 …(gdb) FAIL: gdb.multi/multi-term-settings.exp: inf1_how=attach: inf2_how=attach: stop with control…
167316 	is to resumes the program with "continue", wait to see a few of those
167317 	"pid=..., count=..." lines, and then interrupt the program with
167319 	the Ctrl-C stopping the program with SIGINT.
167373 	After googling the error message with context valgrind gdbserver, I found
167384 	with the "expat" library.  If your GDB was not configured with XML support, it
167401 	[gdb/testsuite] Fix gdb.python/py-breakpoint.exp with python 2
167438 	             --with-auto-load-dir=$debugdir:$datadir/auto-load
167439 	             --with-auto-load-safe-path=$debugdir:$datadir/auto-load
167441 	             --with-gdb-datadir=$install/share/gdb (relocatable)
167442 	             --with-jit-reader-dir=$install/lib64/gdb (relocatable)
167447 	             --with-mpfr
167449 	             --with-python=/usr
167450 	             --with-python-libdir=/usr/lib
167451 	             --with-debuginfod
167454 	             --with-separate-debug-dir=/usr/lib/debug
167455 	             --with-system-gdbinit=$devel/system-gdbinit
167508 	gdb_internal_backtrace_1 with '#ifdef GDB_PRINT_INTERNAL_BACKTRACE',
167542 	populates the file_table array with entries read from .debug_line
167632 	Add a test that tests attaching with gdbserver's --attach flag to a
167695 	riscv_supported_std_ext[](elfxx-riscv.c) and assembling with
167716 	* The extension name ends with <number>p is invalid, since this may
167717 	be confused with extension with <number>.0 version.  We report errors
167722 	* The extension name ends with numbers is valid, but the numbers will
167728 		(riscv_parsing_subset_version): The extensions end with <number>p
167760 	Whether a backtrace is printed or not can be controlled with the new
167769 	Here is an example of what an internal-error now looks like with the
167822 	names it is required that the application (GDB) be compiled with
167851 	GDB.  Now (when GDB is compiled with debug information) the backtrace
167879 	Use of libbacktrace is optional.  If GDB is configured with
167911 	tree with --disable-libbacktrace.
167948 	The problem with zlib impacted a previous attempt to synchronise the
167975 	resolves the issues with 'make all'.
168035 		(OP_E_memory): Mark invalid broadcast with no_broadcast=1 and Print "{bad}"for it.
168036 		(intel_operand_size): mark invalid broadcast with no_broadcast=1.
168037 		(OP_XMM): Mark scalar_mode with no_broadcast=1.
168042 	Replace the manually maintained linked list of lwp_info objects with
168043 	intrusive_list.  Replace the ALL_LWPS macro with all_lwps, which returns
168052 	Replace the lwp_free function with a destructor.  Make lwp_info
168073 	gdb: don't share aspace/pspace on fork with "detach-on-fork on" and "follow-fork-mode child"
168116 	inferior 1 and run again, we find ourselves with two unrelated inferiors
168123 	stops, we compare that symtab with the symtab the program has stopped
168126 	the parent's program space to it with clone_program_space, it creates
168133 	Note that the problem described above happens today with "detach-on-fork
168191 	gdb_test_multiple with gdb_test.  I don't think using gdb_test_multiple
168201 	particularly if we called ctf_lookup_by_name in a child dict with "*foo"
168204 	not even a valid thing to call ctf_lookup_by_name with: foo * is.
168205 	Nonetheless, users sometimes do call ctf_lookup_by_name with invalid
168213 	bug on any machine with 4KiB pages.)
168253 	when reading in the symtypetab section -- but if the set of symbols with
168259 	uint32_t, associated 1:1 with each other). But this is not true for the
168328 	implements a --version-script with different semantics.  Try linking a
168329 	test program with a small wildcard-using version script with each
168345 		* configure.ac (VERSION_FLAGS): Replace with...
168390 	(Tested with NM unset, and set to nm, /usr/bin/nm, my-nm where my-nm is a
168398 		* libtool.m4 (LT_PATH_NM): Try BSDization flags with a user-provided
168434 	be completely incompatible with what is being installed and break either
168440 	linker at install time too, if installing with --prefix=/usr.  That's
168453 	[gdb/build] Fix build with g++-4.8
168474 	and does not reproduce with newer g++.
168478 	[ I considered just removing the initialization, with the idea that access
168498 	reading the source files.  A user can run with source code reading
168539 	Given such a situation we would expect GDB to terminate the stack with
168557 	normal_frame, but also within a block associated with the inlined
168592 	GDB doesn't know the stack is corrupted (with a cycle), GDB still
168811 	with prepare_for_testing for brevity.
168910 	The gdb.perf/disassemble.exp testcase debugs GDB with itself, runs to
168917 	It would perhaps be better to come up with some test program to
168920 	done to begin with.  I'll have to leave that for another rainy day,
168960 		with "$srcdir" not expanded.
169021 	A new test case is included.  This test fails with GCC 11, but passes
169022 	with an earlier version of GCC.
169067 	- do a prepare_for_testing with $srcfile (roughtly equivalent to what
169117 	example, with:
169129 	   # Test with 32-bit and 64-bit DWARF.
169172 	When running test-case gdb.dwarf2/implptr-64bit.exp with target board
169196 	When doing a testrun with:
169242 	There is no indication that this is on purpose, so replace these with pie and
169279 	language.c.  However, it really has to do with types, so it should
169290 	When running gdb.rust/*.exp test-cases with target board unix/-fPIE/-pie, I
169297 	compiler exited with status 1
169308 	Tested on x86_64-linux, with:
169312 	specifically, on openSUSE Leap 15.2 both with package gcc-PIE:
169320 	Replace {additional_flags=-fPIE ldflags=-pie} with {pie}.
169350 	- gdb is build without --with-separate-debug-dir so it can't find the
169383 	- gdb is build without --with-separate-debug-dir so it can't find the
169446 	with:
169507 	using 'long' can sometimes end up with the value being sign-extended.
169522 	the type is 'long', this can cause problems with sign extension.
169599 	running the testcase on ia64 targets I found timeouts along with lots
169602 	in them being added to subsegment 0, with no increase to subsegment 1
169659 	In test-case gdb.base/gdb-caching-proc.exp, we run all procs declared with
169703 	[gdb/testsuite] Fix gdb.ada/interface.exp with gcc-9
169704 	When running test-case gdb.ada/interface.exp with gcc-9, we run into:
169722 	When running test-case gdb.ada/mi_prot.exp with gcc 8.5.0, we run into:
169780 	Tested on x86_64-linux with an --enable-targets=all build.
169818 	Bug 28341 shows that GDB fails to compile when built with -std=c++11.
169830 	The failure (and fix) can be observed by configuring GDB with CXX="g++
169887 		before an unknown instruction, '%d' is replaced with the
169897 	Re: PR28149, debug info with wrong file association
169911 	--enable-targets=all on a 32-bit host results in a link failure with
169961 	compilation units (CUs) with the CTF debug info. An executable could
169983 	[gdb/testsuite] Fix gdb.server/server-kill.exp with -m32
169984 	When running test-case gdb.server/server-kill.exp with target board unix/-m32,
170020 	[ The FAIL doesn't reproduce with gcc 9.3.1.  This difference in
170023 	The FAIL with earlier gcc bisects to gdb commit ba8694b650b. ]
170062 	Mixing compiler generated line info with gas generated line info is
170063 	generally just confusing.  Also .loc directives with non-zero view
170082 	PR28149, debug info with wrong file association
170092 	debug info until the end of assembly, thus avoiding any clashes with
170095 	specified with .file.
170103 		(set_or_check_view): Replace all accesses to view with u.view.
170145 	This takes care of writing out GOT entries with addends.  The local
170209 	with addend of zero.
170250 	and global symbols can have GOT entries with addend.
170261 		uint64_t parameter with FIXME.
170352 	When running test-case gdb.threads/continue-pending-status.exp with native, I
170365 	but with target board unix/-m32, I run into:
170410 	When I run test-case gdb.dwarf2/dw2-abs-hi-pc.exp with gcc, we have:
170416 	but with clang, I run into:
170460 	Tested on x86_64-linux with gcc and clang-7 and clang-12.
170515 	[gdb/testsuite] Fix gdb_load_no_complaints with gnu-debuglink
170516 	When running test-case gdb.dwarf2/dw2-ranges-psym-warning.exp with target
170615 	With current trunk and target board cc-with-debug-names we have:
170690 	Tested on x86_64-linux with native and target board cc-with-debug-names.
170697 	When running test-case gdb.dwarf2/locexpr-data-member-location.exp with target
170698 	board cc-with-debug-names, all tests pass but we run into PR28261:
170786 	With a gdb build with --enable-targets=all we run into a KFAIL:
170841 	With a gdb build with --enable-targets=all, we have 2 arch-specific failures
170902 	With a gdb build with CFLAGS "-O2 -g -flto=auto", I run into:
170959 	But with target board cc-with-debug-names, we run into (added missing double
170972 	The difference between the passing and failing case is that with native we
170979 	and with target board cc-with-debug-names:
171052 	However, this is not checked, and when mi_gdb_test is called with less than 3
171073 	A regexp pattern with escapes like this is hard to read:
171108 	When running the gdb testsuite with gnatmake-4.8, I get many fails of the
171113 	compiler exited with status 1
171146 	pretty easy with a stub file.
171179 	[gdb/testsuite] Fix gdb.base/coredump-filter-build-id.exp with older eu-unstrip
171180 	On openSUSE Leap 42.3 with eu-unstrip 0.158, we run into:
171185 	FAIL: gdb.base/coredump-filter-build-id.exp: gcore dumped mapping with build-id
171189 	introduced with eu-unstrip 0.161.  Before it printed '[exe]' or '[pie]'.
171198 	I noticed this failure in gdb.mi/mi-sym-info.exp with gcc-4.8:
171228 	Furthermore, I found a silent FAIL due to calling mi_gdb_proc with 2 args, fix
171231 	Then I ran with clang and found another FAIL, fix by updating the regexp.
171233 	Tested on x86_64-linux with gcc-4.8.5, gcc-7.5.0, gcc-11.2.1, clang-7.0.1 and
171239 	When building gdb with "-Wall -O2 -g -flto=auto", I run into:
171289 	that GDB will always be compiled with a version of Python that has the
171347 	defines ends up conflicting with the standard Windows VOID define.
171352 	will take larger discussion & coordination with the cgen project.
171359 	conflicting with system headers.  So including it before the system
171441 	When compiling with --enable-werror and CFLAGS="-O0 -g -Wall", we run into:
171468 	We could add some core APIs to the ppc sim that deal with raw bytes and then
171476 	is also why we go with a cast rather new (but largely unused) APIs.
171481 	This aligns with common code which already uses this flag.  We have
171484 	lot more work & conversions in the process, so going with the decl
171489 	sim: microblaze: replace custom basic types with common ones
171490 	The basic "byte" type conflicts with Windows headers, and we already
171491 	have common types that provide the right sizes.  So replace these with
171507 ….../buildsim/../../../sim/microblaze/microblaze.h:94:25: note: previous declaration of 'byte' with…
171514 	RISC-V: Pretty print values formed with lui and addiw.
171534 	sim: ppc: align format string settings with common code
171601 	gdbsupport/gdb_optional.h, when compiling with _GLIBCXX_DEBUG
171614 	Now, handle_one leaves the stop_pc with no value.
171617 	again, in proceed() we compare the current pc with the cached stop_pc.
171627 	needs to be guarded with a call to thread_info::stop_pc_p(), in most
171639 	[gdb/build] Fix build with undefined CXX_STD_THREAD
171677 	and makes it easier to keep it aligned with the sim target tests.
171696 	Replace some of the manual string management (malloc/free) with
171839 	-notransfer, and let the caller proc runto deal with it.
171847 	gdb: rename gdb/testsuite/gdb.arch/riscv64-unwind-prologue-with-ld-lw.c
171849 	gdb.arch/riscv64-unwind-prologue-with-ld-lw.exp testcase, but one of its
171961 	Tested on my x86_64-linux laptop with avx support, where both test-cases pass.
172004 	of the compiler version.  (Well, it'll work with whatever compilers
172005 	the DWARF assembler works with.)
172111 	When building gdb with "-Wall -O2 -g -flto=auto", I run into:
172141 	Values of type _Float16 and _Float16 _Complex can now be used on CPUs with
172187 	in the original enablement.  This also adjusts the testcase to pass with
172204 	When building gdb with "-Wall -O2 -g -flto=auto", I run into:
172247 	attempt to trim off -fsanitize options left us with ",undefined".
172257 		* testsuite/ld-auto-import/auto-import.exp: Don't pass
172280 	is the compiler that should be used for almost all tests with C
172282 	too.  This was all supposed to work with the testsuite .exp files
172284 	compiler, with the makefiles passing CC=$CC_FOR_TARGET and
172289 	itself.  Since the files being linked were created with the host
172294 	the makefiles with CC was a bad idea.  Not only is it confusing, but
172308 		and similar.  Pass variables with unchanged names.  Don't set
172313 		* testsuite/ld-cdtest/cdtest.exp: Replace all uses of CC with
172315 		* testsuite/ld-auto-import/auto-import.exp: Likewise.
172374 		* po/BLD-POTFILES.in: Regenerate.
172416 	than 64k.  Since the mapping is 1-1 with symbols there is no need to
172420 	linker's elf hash table is incremented in lock-step with the output
172428 	case where it is known that the offset is always zero with a NULL
172631 	Remove breakpoint_find_if, replace its sole usage with using
172654 	as usual.  I have discussed this with Kito many times, we all think
172693 	fbsd-nat: Don't use '%jd' and '%ju' with printf_filtered.
172695 	uses the 'j' size modifier along with uintmax_t / intmax_t casts to
172917 		with MAP_DATA.
172946 		Added to dump sections with mapping symbols.
173030 	PR28264, ld.bfd crash on linking efivar with LTO
173042 	[gdb/symtab] Don't write .gdb_index symbol table with empty entries
173059 	The problem is that the .gdb_index contains a non-empty symbol table with only
173085 	with a corresponding .debug_aranges entry:
173155 	A couple of test-cases fail when run with target board cc-with-debug-names due
173244 	the patches that merge the list of CUs with the list of TUs (and to a
173264 	Real programmers don't configure gcc using --with-ld
173288 	overflow.  Replaced with a pair of non-recursive functions.
173305 	and runs to it, expecting that the language should remain "auto; c"
173319 	still exercises the original problem, but also avoids problems with my
173334 	The problem is caused by using %ps in combination with the error function
173335 	(note that confusingly, it does work in combination with the warning
173429 	[gdb/testsuite] Fix dw2-ranges-psym.exp with -readnow
173430 	When running test-case gdb.dwarf2/dw2-ranges-psym.exp with target board
173553 	Re: as: Replace the removed symbol with the versioned symbol
173555 	relocation symbol with a section symbol (see tc_fix_adjustable).
173669 	only reads fields defined for r_version == 1, it is compatible with
173826 	This also reduces .ds.x output and .tfloat output with hex input from
173830 		* NEWS: Mention changes of .ds.x output and .tfloat output with
173850 	problem... I can only really run native tests with dejagnu AFAIK.
173871 	to reproduce this with the GDB test suite, but the test is identical
173905 	Notify observer of breakpoint auto-disabling
173907 	before handling auto-disabling when enable count is reached, the observer
173914 	- insight: breakpoint GUI window is not properly updated upon auto-disable
173916 	This patch moves the observer notification after the auto-disabling
173925 	as: Replace the removed symbol with the versioned symbol
173928 	it to be removed and replace the removed symbol used in relocation with
174024 	Stack overflow with a large float. %f is not a goot choice for this.
174025 	%f should be replaced with %.7g.
174050 	state to WILD with a reduced scope.)
174061 		(script_file): Replace ldlex_both with ldlex_script.
174069 		* ldfile.c (ldfile_try_open_bfd): Replace ldlex_both call with
174076 	the target should still be accepted with --enable-obsolete.
174134 	with the 'ld' instruction.  GDB thinks it reached the end of the
174162 	The testsuite have been run on riscv64 ubuntu 21.01 with no regression
174260 	The following patch synchronizes includes/objdump/readelf with the Linux
174269 	We don't need GDB to bother with this at the moment, so this doesn't update
174296 	come back, it would be with ELF. The binutils implementation is
174363 	this commit.  Only if GDB terminates with one of the above signals
174402 	previously, if GDB hit a SEGV then we would terminate GDB with a
174403 	SIGABRT.  After this commit we will terminate GDB with a SIGSEGV.
174438 	not being built with -rdynamic as the manual page for
174450 	The async_init_signals has, for some time, dealt with async and sync
174467 	comment on SIGQUIT talks about problems with BSD4.3 and vfork,
174544 	token associated with SIGFPE has been marked and will call the async
174566 	    will terminate.  This is inline with what happens if the user
174572 	    this is inline with what happens if GDB receives a SIGSEGV due to
174616 	Some frontends, like the gcc Objective-C frontend, emit symbols with $
174633 	gas: fold IEEE encoding of -Inf with that of +Inf
174645 	Note that an anomaly with x86'es double extended precision NaN values
174647 	value with all mantissa bits set was used, while here a negative value
174648 	with all non-significant mantissa bits clear was chose for an unknown
174703 	x86/ELF: fix .tfloat output with hex input
174705 	bytes long (with 2 bytes of trailing padding), while on 64-bit it is 16
174706 	bytes long (with 6 bytes of padding). Make hex_float() capable of
174719 	is 12 bytes long (with 2 bytes of trailing padding), while on 64-bit it
174720 	is 16 bytes long (with 6 bytes of padding). Make s_space() capable of
174724 	would complain if this was out of sync with config/atof-ieee.c.
174745 	bytes long (with 2 bytes of trailing padding), while on 64-bit it is 16
174746 	bytes long (with 6 bytes of padding). Make ieee_md_atof() capable of
174789 	when run with --target_board=cc-with-debug-names:
174808 	came up with this patch, which generalizes the addrmap-dumping code
174817 	do so, we iterate on all threads using iterate_over_threads with the
174828 	aware: since it only filters on pid, if there is an inferior with the
174867 	If you're more familiar with Python, it would be quite similar to being
174880 	[1]: This changed with Guile commit
174941 		objcopy/strip with NULL output_section.
174948 	an object file with a reloc stack underflow produces a linker error
174970 	[gdb/symtab] Recognize .gdb_index symbol table with empty entries as empty
174971 	When reading a .gdb_index that contains a non-empty symbol table with only
174985 		filled with empty entries.
175002 	definition.  It can be reproduce with --disable-unit-tests.
175015 	 Program terminated with signal SIGABRT, Aborted.
175074 	         Don't pollute the addrmap with bad data.  */
175093 	called with cu_bounds_kind == PC_BOUNDS_INVALID, which sets the set_addrmap
175102 	During that process, addrmap_set_empty is called with a range that includes
175110 	but it's called for a function at DIE 0x54153 with DW_AT_ranges at 0x40ae:
175157 		* testsuite/gas/i386/x86-64-avx512_fp16_pseudo_ops.d: Pass with
175173 	only happen with huge sections which would certainly cause out of
175197 		(bfd_elf32_bfd_reloc_type_table_lookup): Replace assertions with
175240 	we need to associate this with the .toc section in order to
175242 	is not found, iterate the sections until we find one with the
175248 	gdb/testsuite: gdb.base/attach.exp: expose bug when testing with native-extended-gdbserver
175284 	deal with the confirmation.  And to be really sure the extended-remote
175301 	When running this test with the native-extended-gdbserver, we get:
175316 	uses "set auto-connect-native-target off" on the command line.  The full
175320 	          -iex set height 0 -iex set width 0 -ex set auto-connect-native-target off \
175324 	auto-connect-native-target off", or it somehow bypasses it.  When the
175327 	auto-connect-native-target off".  So we get that "Don't know how to run"
175330 	Really, I think it's a case of the test doing things incompatible with
175331 	the board, I think it should just be skipped.  And as we can see with
175395 	requirement was fulfilled by extending the evaluated expression with
175571 	What we are left with in the end is a clean public interface of the
175579 	The idea with this particular patch is to move piece_closure structure
175624 	Although, it is not really necessary to merge this class with it's
175628 	it is also reasonable to expect that with a new evaluator design and
175638 		* dwarf2/expr.c (dwarf_expr_context::read_mem): Merge with
175755 	Once this is done, the get_frame_pc can be replace with lambda
175762 		(dwarf_expr_context::get_frame_pc): Replace with lambda.
175858 	- dwarf_evaluate_loc_desc can evaluate any expression with no
175960 	Replace the symbol needs evaluator with a parser
175961 	This patch addresses a design problem with the symbol_needs_eval_context
175992 	others is that this evaluator is not meant to interact with the actual
175998 	evaluation mechanism and to fake all required interactions with the
176016 	the location description evaluator) with a missing frame information.
176020 	scenario, with the following DWARF expression:
176079 	implicit location description with a constant value that depends on a
176090 	one class that deals with parsing of the DWARF expression, while there
176091 	are virtual methods that deal with specifics of some operations.
176095 	target with the possibility of skipping the evaluation of some parts of
176120 	As described previously the problem with this evaluator is that if the
176135 	replaced with a lightweight recursive analysis function, that will give
176148 	with parsing of the DWARF expression, while there would be a virtual
176149 	methods that deal with specifics of some DWARF operations. Then that
176159 	ended with a 0 value byte, which was never reached by the symbol needs
176188 	There are some exceptions to this rule. Some things in map 1 (0Fxx) with imm8
176192 	prefix (EVEX.pp) bits with the related FP32 operations.
176241 	There are some exceptions to this rule. Some things in map 1 (0Fxx) with imm8
176245 	prefix (EVEX.pp) bits with the related FP32 operations.
176376 	new thread is created with a $pc in the displaced step buffer.  GDB
176378 	be set running with its current $pc value.  This means that the new
176442 	gdb/testsuite: fix gdb.base/info-macros.exp with clang
176447 	I tested with gcc 4.8, and that works fine with -g after -g3.
176449 	The current state is problematic when testing with CC_FOR_TARGET=clang,
176458 	fine with it.  Also, this lets the test use the debug flag specified by
176459 	the board file.  For example, we can test with GCC and DWARF 5, with:
176463 	With the hard-coded -g3, this wouldn't actually test with DWARF 5.
176471 	gdb::optional::get"), some macro-related tests fail on Ubuntu 20.04 with
176472 	the system gcc 9.3.0 compiler when building with _GLIBCXX_DEBUG.  For
176476 …dbsupport/gdb_optional.h:206: internal-error: T& gdb::optional<T>::get() [with T = long unsigned i…
176485 	The same thing happens when building the test program with DWARF 5 with
176487 	string forms, even with DWARF 5.  So it still doesn't add a
176495 	unlikely to happen, but could happen in theory with an erroneous file
176502 …During symbol reading: use of DW_MACRO_define_strx with unknown string offsets base [in module /ho…
176504 	The test now passes cleanly with the setup mentioned above, and the
176505 	testsuite looks on par with how it was before 4d7188abfdf2.
176514 	to only see DW_MACINFO with a file that uses a DWARF 5 .debug_macro
176516 	we are dealing with a .debug_macro section or .debug_macinfo section, to
176667 	gas: correctly output XCOFF tbss symbols with XTY_CM type.
176669 	a symbol with XTY_SD instead of XTY_CM as expected.
176680 	This was already made for most of the sections with the creation
176693 	PR28156, rename.c doesn't compile with MinGW
176722 	target_follow_fork is called with the parent as the current inferior.
176723 	When it's "child", target_follow_fork is called with the child as the
176745 	 - make follow_fork_inferior always call target_follow_fork with the
176769 	   Although this could perhaps be replaced with just having the exec
176840 …dbsupport/gdb_optional.h:206: internal-error: T& gdb::optional<T>::get() [with T = int]: Assertion…
176851 	Please consider below testcase with intended error.
176972 	problem can easily be seen under valgrind (and, I presume, with ASAN,
176976 	branch, with a suitable ChangeLog entry of course.
176982 	[gdb/testsuite] Fix gdb.dwarf2/dw2-using-debug-str.exp with cc-with-dwz-m
176983 	When running with target board cc-with-dwz-m, we run into:
176995 	With cc-with-dwz-m, the .debug_str section is not present in the
177000 	The same problem arises with target board cc-with-gnu-debuglink.
177016 	[gdb/testsuite] Fix gdb.dwarf2/dw2-using-debug-str.exp with cc-with-gdb-index
177017 	When running with target board cc-with-gdb-index, we run into:
177037 		cc-with-gdb-index output.
177041 	[gdb/testsuite] Fix gdb.dwarf2/per-bfd-sharing.exp with cc-with-gdb-index
177042 	When running with target board cc-with-gdb-index, we run into:
177064 	[gdb/testsuite] Fix gdb.dwarf2/gdb-index-nodebug.exp with cc-with-gdb-index
177065 	When running with target board cc-with-gdb-index, we run into:
177087 	[gdb/testsuite] Fix gdb.dwarf2/fission-relative-dwo.exp with cc-with-gdb-index
177088 	When running with target board cc-with-gdb-index, we run into:
177099 	- cc-with-tweaks.sh moves the executable to a temp dir, but not
177112 		* contrib/cc-with-tweaks.sh: Copy .dwo files alongside executable.
177168 	[gdb/testsuite] Fix gdb.base/maint.exp with cc-with-gdb-index
177169 	With target board cc-with-gdb-index we run into:
177181 	  Number of symbol tables with line tables: 2^M
177182 	  Number of symbol tables with blockvectors: 2^M
177201 		output with target board cc-with-gdb-index.
177205 	[gdb/testsuite] Fix gdb.base/index-cache.exp with cc-with-gdb-index
177206 	With target board cc-with-gdb-index we run into:
177236 	classes with a specialization of iterator_range.
177242 	Replace exception_print_same with operator!=
177259 	Tested by building with trunk gcc.
177382 	inferiors (e.g. after a fork with detach_on_fork disabled).
177402 	  properly returns ptid's with thread IDs when reporting PTRACE_FORK
177421 	  needs to be updated with an LWP ID, or if this is a new thread.
177490 		* gdb.tui/tui-layout-asm.exp: Replace window width of 80 with the
177499 	vlscm_convert_typed_number to be better in line with the prevailing
177513 	guile: fix make-value with pointer type
177514 	Calling the `make-value' procedure with an integer value and a pointer
177539 		for creating pointers with make-value.
177577 	generating object files with gas or when reading them with objdump.
177579 	object files with such symbols to be accepted by AIX ld.
177661 	 - we generate a regformats/microblaze-with-stack-protect.dat file.  I
177682 	If any pair of operands in AMX instructions with 3 TMM register operands
177701 	to avoid running out of file descriptors on thin archives with many
177775 	[gdb/symtab] Fix unhandled dwarf expression opcode with gcc-11 -gdwarf-5
177777 	commit 0057a7ee0d9 "[gdb/testsuite] Add KFAILs for gdb.ada FAILs with
177779 	the default for gcc-11.  I keep getting confused because of working with a
177783 	When running test-case gdb.ada/arrayptr.exp with gcc-11 (and default
177820 	with upper bound of form DW_FORM_data16.
177839 	In contrast, with -gdwarf-4 we have:
177849 	result as with -gdwarf-4:
177857 	Tested on x86_64-linux, with gcc-11 and target board
177881 	options that extend a base cpu with extra functional units to be
177890 	functionality with .machine.  For example the following can be
177903 	compiled with -maltivec but containing
177934 	while with gcc 9.3.1 we have instead:
177965 	while with gcc 8.5.0 we have:
178010 	This commit replaced fprint_frame with frame_info::to_string.
178062 	That is, we start with the frame-id for the next frame as obtained by
178082 	  1. Start with a frame_id taken from a value,
178093 	  1. Start with a frame_id taken from a value,
178110 	more efficient, with no real additional complexity, by removing the
178114 	with a use of VALUE_NEXT_FRAME_ID, followed by a direct call to
178157 	This test fails on PPC64 because PPC64 prints the value of 3.5 with
178379 	As with the original commit, the intention behind this commit is to
178457 	overlays with weird section names.
178489 	make-parameter and then register it with GDB with register-parameter!.
178508 	registering the same callback with many commands, and alter the behavior
178522 	that goes with it.  Rename cmd_const_sfunc_ftype to cmd_func_ftype and
178554 	everything (like the utility functions) that goes with it.
178571 	well, which is shared with GDBserver.  So update the related GDBserver
178657 	Split in multiple procs, one per topic, and start with a fresh GDB in
178658 	each.  I find it easier to work on a test with multiple smaller
178677 	starts with a fresh GDB.  I find it easier to understand what a test is
178705 	if the spawn function is called with the argument -leaveopen, which is
178719 	Fix this issue by using -nocomplain with the call to unset in
178765 	When running test-case gdb.ada/formatted_ref.exp with gcc-11 and target board
178803 	Tested on x86_64-linux, with:
178821 	reflecting REX.W / VEX.W is not in line with the assembler's opcode
178832 	They're effectively redundant with {b,w,d,q}_mode.
178840 	These are fully redundant with, respectively, x_mode and scalar_mode.
178880 	By moving its vex.r check there it becomes fully redundant with OP_G().
178888 	[gdb/testsuite] Fix gdb.cp/step-and-next-inline.exp with gcc-11
178889 	When running test-case gdb.cp/step-and-next-inline.exp with gcc-11, I run
178899 	[ Note that I get the same result with gcc-11 and target board
178917 	and with gcc-11, I have instead:
178931 	and with clang-10, I have instead:
178946 	tree_check (lines 40-43) (so, with the clang trace we get that right).
178960 	Tested on x86_64-linux, with gcc-8, gcc-9, gcc-10, gcc-11, clang-8, clang-10
178968 		Tag closing brace with comment.
178969 		* gdb.cp/step-and-next-inline.h: Update to keep identical with
178992 	When running test-case gdb.base/ptype-offsets.exp with gcc-11 (with -gdwarf-5
178993 	default) or gcc-10 with target board unix/gdb:debug_flags=-gdwarf-5 we run
179032 	[gdb/testsuite] Add KFAILs for gdb.ada FAILs with gcc-11
179052 	Tested on x86_64-linux, with gcc-10 and gcc-11.
179070 	with
179214 	to catch errors, print them, and still continue with the normal
179278 	started failing with commit 0618ae414979 ("gdb: optimize
179374 	record_btrace_target::record_is_replaying with a null inferior_ptid.
179377 	ultimately trying to read memory with a null inferior_ptid already
179383 	thread_info to work with as a parameter, that typically means that it
179409 	Update how-to-make-a-release checklist with latest changes from 2.37 release
179413 	PR28098 Skip R_*_NONE relocation entries with zero r_sym without counting
179416 		with r_sym of zero without counting in advance method.
179434 	Fix file-name handling regression with DWARF index
179435 	When run with the gdb-index or debug-names target boards, dup-psym.exp
179448 	exist.  Then, the functions that work with this data are changed to
179521 	you may use some simulator with GDB support.
179549 	Looking at the log, we see that we are left with a bunch of inferiors in
179591 	constructing the wrapped iterator with multiple arguments, not just one.
179661 	Investigation of using the Python API with an Ada program showed that
179699 	Avoid expression parsing crash with unknown language
179770 	   check_for_thread_db, for example) is called with inferior 1 as the
179901 		* i386-dis.c (dis386): Replace icebp with int1.
179920 	fixups with BFD_RELOC_GPREL32/16 and use a syntax explicitly showing
179998 	When building gdb with --disable-tui, we run into:
180041 …builder for '/nix/store/xs8my3rrc3l4kdlbpx0azh6q0v0jxphr-gdb-gdb-11.0.90.drv' failed with exit cod…
180067 	which are fetched and stored with dedicated ptrace operations.  These
180146 	with -fasynchronous-unwind-tables (x86-64 defaults that on, but not
180176 	Fix detach with target remote (PR gdb/28080)
180178 	with threads running") regressed "detach" with "target remote":
180237 	managed to detach already, and, we're debugging with "target remote"?
180247 	to do, and we don't try to talk with the remote target anymore.
180249 	The regression isn't seen when testing with
180252 	commit adds a testcase that explicitly tests detach with "set sysroot
180277 	[gdb/testsuite] Fix check-libthread-db.exp FAILs with glibc 2.33
180279 	Tumbleweed with glibc 2.33, I get:
180293 	which is what I get on openSUSE Leap 15.2 with glibc 2.26, and what is
180296 	    # libthread_db should fake a single thread with th_unique == NULL.
180329 	Fix this by updating the regexp patterns to agree with what libthread-db is
180332 	Tested on x86_64-linux, both with glibc 2.33 and 2.26.
180402 	-exec-interrupt with --thread-group:
180423 	Calling -exec-interrupt with --thread-group is apparently not tested at
180425 	that.  The test runs two inferiors and tries to interrupt them with
180500 	by playing with the ptid.
180551 	gdb: optimize selection of resumed thread with pending event
180555 	resumed with a pending wait status.  It is currently implemented by
180559 	Since we now maintain a per target list of resumed threads with pending
180564 	the common case where there isn't any resumed thread with pending
180566 	out.  With this patch, the list of resumed threads with pending event
180573 	the list of resumed threads with pending wait statuses will generally be
180579 	threads with pending wait statuses, and random_pending_event_thread is
180580 	called with inferior B.  We'll need to go through the list that contains
180582 	with pending wait status.  But I think that this is a corner /
180591 …gdb: optimize check for resumed threads with pending wait status in maybe_set_commit_resumed_all_t…
180597 	whether the target has at least one resumed thread with a pending wait
180602 	Since we now maintain a per-target list of resumed threads with pending
180613 	gdb: maintain per-process-target list of resumed threads with pending wait status
180641 	there are no resumed with pending wait status threads.
180687 	thread_suspend_state, along with other fields that we need to backup
180760 	     others with their status pending.  */
180775 	GDB_SIGNAL_0).  This doesn't work with the assertions I've
180783 	stopped with TARGET_WAITKIND_STOPPED + GDB_SIGNAL_0.
180842 	inferior list with only the new mock inferior.  Tests using two
180847 	it on destruction.  This means that tests run with mock inferiors in the
180869 	nice to avoid the boilerplate associated with maintaining such a list
180878 	Note that with std::list, element removal is O(N).  I.e., with
180897 	linked list, while avoiding the boilerplate associated with manually
180923 	This wasn't great for when debugging GDB with GDB, as it was difficult
180954 	debugging GDB with GDB.  Here's an example of the output:
180959 	It's not possible with current master, but with this patch [1] that I
180997 	[gdb/testsuite] Fix gdb.btrace/tsx.exp on system with tsx disabled in microcode
180998 	Recently I started to see this fail with trunk:
181011 	Tested on x86_64-linux, with both gcc 7.5.0 and clang 12.0.1.
181020 		* gdb.btrace/tsx.exp: Add pattern for system with tsx disabled in
181029 …binutils * readelf.c (process_dynamic_section): Use ngettext to help with translation of header te…
181065 	Then I run into FAILs when using the cc-with-gnu-debuglink board.  Fix these
181068 	Tested on x86_64-linux, with native, check-read1, readnow, cc-with-gdb-index,
181069 	cc-with-debug-names, cc-with-gnu-debuglink, cc-with-dwz, cc-with-dwz-m.
181082 	Replace leading 8-spaces with tab and remove trailing space in
181105 	We shouldn't be asserting on anything to do with leb128 values, or
181165 	3. Treate reference to protected symbols with indirect external access
181191 		STV_PROTECTED symbols with indirect external access.
181229 		* testsuite/ld-elf/linux-x86.exp: Run test with
181232 		function and data with indirect external access.
181248 	cannot be used with copy relocation.
181306 	are many input files with many relocations, we may run out of memory.
181434 	The distclean operation fails with:
181482 	[gdb/testsuite] Fix gdb.guile/scm-breakpoint.exp with guile 3.0
181484 	with guile 3.0, I run into:
181495 	The same test passes on openSUSE Leap 15.2 with guile 2.0, where the second
181496 	line of the error message starts with the same prefix as the first:
181514 	Tested on x86_64-linux, with both guile 2.0 and 3.0.
181583 	Fix Solaris gprof build with --disable-nls
181584 	gprof fails to compile on Solaris 10 and 11.3 with --disable-nls:
181653 	Fixed with the following patch.  Tested on i386-pc-solaris2.10.
181675 		* po/gas.pot: Regenerate.
181682 		* po/bfd.pot: Regenerate.
181731 	with:
181768 		(struct program_space) <objfiles_range>: Define with "using".
181770 		<objfiles_safe_range>: Define with "using".
181803 	check" with an appropriate board file.
181863 	elf/riscv: Fix relaxation with aliases [PR28021]
181888 	Update gdb performance testsuite to be compatible with Python 3.8
181889 	Running "make check-perf" on a system with Python 3.8 (e.g., Ubuntu
181920 	       counter, i.e. a clock with the highest available resolution to
181933 	with two new classes -- MeasurementPerfCounter and
181941 	For backward compatility, with Python < 3.3, both perf_counter and
181965 	Currently, if you run make check-perf on a system with Python 3.8,
182055 		gdb_test_multiple_with_read1_timeout_factor with gdb_test_lines.
182061 	RISC-V: Fix the build broken with -Werror.
182079 	      /* We're importing a C++ compilation unit with tag DW_TAG_compile_unit
182093 	  (with 5 unexpected FAILs)
182096 	  (with 1000 unexpected FAILs)
182179 	mixed in with the CUs.
182243 …R and RANLIB programs used when building libiberty, which in turn allows building with LTO enabled.
182249 	[gdb/testsuite] Fix fail in gdb.fortran/ptype-on-functions.exp with gcc-7
182269 	Tested on x86_64-linux, with gcc-7 and gcc-10.
182289 	An alternative to sigtimedwait with a timeout of 0 is to use sigpending,