Lines Matching +refs:po +refs:auto +refs:fuzzy +refs:on +refs:edit
198 should be applied on PC for these reloc types to avoid wrong relocation
216 encoded relative relocs were allowed when it was known they were on
218 (non-relr) on eight byte boundaries.
247 Since SCFI isn't supported on x32:
295 with `#<simm>' taking on a signed 8-bit integer value in the range
398 This leads to the requirement that this quantity be calculated based on
419 currently fails on riscv because a local label name is assumed
738 opcodes: i386-reg.tbl: Add a comment to reflect dependency on ordering
740 operands. The API ginsn_dw2_regnum relies on the the relative ordering
1094 Tested on x86_64-linux, with:
1105 Make breakpoint pending on future shared library load? (y or [n]) y^M
1116 "Make breakpoint pending on future shared library load?.*" "y"
1126 "Make breakpoint pending on future shared library load\\? $yn_re " "Y"
1129 Tested on x86_64-linux.
1172 noticeable impact on the performance for large applications.
1260 thread. I do this by recording the main thread early on (when there
1305 Additionally, change FEAT_XS tlbi variants to be gated on "+xs" instead of
1348 gdb/doc: add some notes on selecting suitable attribute names
1354 on selecting good names for their custom attributes so they
1371 paragraph on selecting attribute names.
1607 on the command being completed for the test name. This is fine for
1680 and consequently on aarch64-linux I ran into an UNSUPPORTED followed by 3
1688 Tested on x86_64-linux and aarch64-linux.
1737 Add a test based on the DWARF assembler to expose the problem and test
1738 the fix. I also tested on ppc64le to make sure the problem reported in
1746 [gdb/testsuite] Fix gdb.dwarf2/dw2-entry-points.exp on ppc64le
1766 However, when setting a breakpoint on the entry point foo:
1780 Tested on ppc64le-linux and x86_64-linux.
1831 Tested on x86_64-linux.
1870 between integers and pointers which breaks down hard on 64-bit hosts.
1907 still keep it on the prototype for cases where it's used as a
1967 Our hardware counter profiling is based on perf_event_open().
2009 to run cgen using 'guile'. However, on my host, guile is guile 2.2,
2036 making these targets depend on a new phony target which makes sure site.exp
2045 Recent Darwin versions place contraints on the use of run paths
2071 We default this on for systems where the external DYLD_LIBRARY_PATH
2082 Without the change profiled bootstrap fails for various warnings on
2136 Tested on x86_64-linux.
2174 Tested on x86_64-linux.
2202 Tested on x86_64-linux.
2218 Tested on x86_64-linux.
2228 Tested on x86_64-linux and ppc64le-linux.
2238 Tested on x86_64-linux and ppc64le-linux.
2274 to run cgen using 'guile'. However, on my host, guile is guile 2.2,
2328 also add GLIBC_2.36 version dependency for -z mark-plt on the shared C
2410 Regression tested on x86-64 Fedora 38.
2437 f6c7c3e8b742 ("Referencing a function's address on PowerPC64 ELFv2"),
2452 Tobias reported on IRC that the linker fails to build with GCC 4.8.5.
2479 currently returns int. However, on Solaris pid_t is long for 32-bit,
2485 Bootstrapped without regressions on i386-pc-solaris2.11,
2506 cases found by running the testsuite with -Wabi forced on:
2563 Tested on i386-pc-solaris2.11 with as and gas.
2576 speedup on those hosts as well, the intent in sha1.c was that
2582 the other arch support, similarly for any target attributes on
2609 fork), but should have equivalent or faster performance on all
2614 Tested on x86_64-linux.
2620 in/out/errdes on error, and check close() for errors.
2657 instructions are enabled on passing both "+the and +d128" flags.
2668 Read check write atomic bit clear on doubleword:
2670 Read check write atomic bit clear on quadword:
2672 Read check write software atomic bit clear on doubleword:
2674 Read check write software atomic bit clear on quadword:
2676 Read check write atomic bit set on doubleword:
2678 Read check write atomic bit set on quadword:
2680 Read check write software atomic bit set on doubleword:
2682 Read check write software atomic bit set on quadword:
2873 likewise take on a value of xzr.
2886 `operand_general_constraint_met_p' to allow the pair to both take on
2983 done by linkage name (it would require relying on a certain mangling
3049 be done on the main thread when scanning DWARF -- before the main
3057 Before this patch, "file" on my machine:
3142 DWARF reader and other code on the main thread to both attempt to open
3232 The implementation was based on comments and code in LLVM, as the GNU
3245 This change can fix 2 test failures on mipsisa32rN(el)-linux:
3287 FAIL: $exp: exec_file=vfork-follow-parent-exit: target-non-stop=on: \
3293 Tested on x86_64-linux.
3300 Add support for the aarch64-gnu target (GNU/Hurd on AArch64)
3364 Tested on aarch64-linux.
3386 on adcx. Add
3390 replace S with L on adcx and adox.
3404 (prefix_table): Replace S with L on adcx and adox.
3428 based on that. If the variable is out of range, it ends up returning
3525 - cpu_flags_from_attr() wasn't ready for use on big-endian hosts,
3547 ELF and COFF have; afaict doing so broke .previous on ELF, and a sub-
3586 other precautions against subsections being used on ELF with .bss. It
3613 other precautions against subsections being used on ELF with .bss. It
3639 against subsections being used on ELF with .bss. It also doesn't look
3641 have (afaict doing so further broke .previous on ELF).
3651 other precautions against subsections being used on ELF with .bss. It
3653 ELF and COFF have (afaict doing so further broke .previous on ELF).
3661 it depends on the compiler having at least C++11 as the default
3713 files on real HW and make sure they don't trigger SIGILL.
3781 Tested on aarch64-linux.
3800 4) Check out */po/*.pot which we don't update frequently.
3870 that gcc produces, with some kind of '~~~~~^' marker on the second
3903 While working on a later commit in this series I realised that the
3959 operates on two strings and not an actual filter object, and it's
4004 This will make it easier to share common/ code that rely on these
4020 No port relies on this anymore, so we can scrub it all.
4197 When running GDB's testsuite on aarch64-linux/Ubuntu 20.04 (also spotted on
4209 - step from line 38 will land on line 40.
4210 - step from line 40 will land on line 42.
4213 - step from line 42 will land on line 40.
4214 - step from line 40 will land on line 40.
4215 - step from line 40 will land on line 38.
4226 When stepping forward from line 40, we skip both of these ranges and land on
4241 Patch has been tested on PowerPC, X86 and AArch64 with no regressions.
4248 options are supported on clang and gcc version 7 and newer.
4250 Patch has been tested on PowerPC with both gcc and clang.
4266 will it attempt heuristics based on the current instruction.
4301 Since we rely on the top-level config.h now, the defines.h generation
4436 depends on the configure-time checks. Delete the logic to simplify
4450 This code sets up the cc variable based on the comparison of other
4456 Move it into read-only data sections to avoid constructing them on the
4477 Run 'black' on tui-window.py
4511 Tested on aarch64-linux.
4545 Tested on x86_64-linux.
4564 Please DON'T edit this file. READ THE COMMENT!
4636 For gfortran there actually exists a bug on bugzilla, asking for the use
4669 This commit should have no functional impact on GDB.
5420 The new carry.s test was also validated to pass on real hardware -
5503 const from name_list.name. Unlink output element on bfd_close
5505 cleanup to prevent rmdir on non-existent file.
5595 Some spots loop on the frame chain to find the first next non-inline
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
5722 a frame lookup on the callee side, when we can just pass the frame down
5783 gprofng: fix build problems on linux-musl
5784 ino64_t, off64_t, fpos64_t, stat64, __u64 are not defined on linux-musl.
5873 file is the easiest way to suppress while keeping it on everywhere else in
5971 Step (b) was omitted for rs6000-tdep.c; this manifests as a regression on
6001 gdb: add git trailer information on gdb/MAINTAINERS
6041 While there also hand on the function arguments, even if right now
6073 with .insn we can't make assumptions anymore on all respective templates
6153 ld: Add lib32 directories for 32-bit emulation on FreeBSD/amd64
6154 GNU ld currently fails to link 32-bit executables on FreeBSD/amd64 when
6155 the linked libraries have dependencies on shared objects themselves:
6167 Tested on amd64-pc-freebsd14.0.
6242 Seems like these register operations intended on falling thru.
6306 statement seems kind of obvious based on the 32-bit case above it.
6353 the same size as an address on the target system.
6366 can't be added upstream yet, unfortunately, due to dependency on DWARF
6367 extensions that can't be upstreamed yet. However, it can be found on
6368 the mailing list on the same series as this patch.
6371 but exit. There is a breakpoint on the s_endpgm instruction. Once
6386 not on the thread list yet. The output shows "?"s instead of proper
6476 amd_dbgapi_thread_deleted trips on this assertion:
6549 placed on top of the s_endpgm instruction inline (displaced=off), GDB
6566 what first called delete_thread on the exiting thread, which is
6600 While making step over thread exit work properly on AMDGPU, I noticed
6601 that if there's a breakpoint on top of the exit syscall, and,
6615 exercise this on GNU/Linux (on the CPU side), and there, after that
6621 GNU/Linux, and the actual problem on AMDGPU. I wrote a gdb.rocm/
6639 currently on GNU/Linux by coincidence, but a similar testcase on AMD
6650 …gdb.threads/step-over-thread-exit.exp: displaced-stepping=auto: non-stop=on: target-non-stop=on: s…
6694 that later on when we acknowledge it, we also discard it. */
6738 mnemonics with their condition (e.g. "on A high"). This complements
6967 However, clang doesn't use the CFA and instead relies on specifying when
6986 from the various ports on the fly, so abuf will never be used.
7085 Note that on x86_64 this is also relaxed and the produced code is like:
7102 multiplies, we may need to do a bit reflection, which on the mcore
7159 [gdb/testsuite] Fix gdb.threads/thread-specific-bp.exp on native-gdbserver
7172 (gdb) PASS: gdb.threads/thread-specific-bp.exp: non_stop=on: thread 1 selected
7180 FAIL: gdb.threads/thread-specific-bp.exp: non_stop=on: continue to end (timeout)
7183 This only crops up (for me) when running on a loaded machine, and
7367 [gdb/build] Remove dependency on _rl_term_autowrap
7369 dependency on readline private variable _rl_term_autowrap.
7374 Remove the dependency on _rl_term_autowrap, and instead calculate
7378 Tested on x86_64-linux.
7401 Tested on x86_64-linux.
7417 Tested on x86_64-linux.
7504 before all the options were on one line:
7522 Ok for binutils-master? I don't have commit access so I need someone to commit on my behalf.
7536 Ok for binutils-master? I don't have commit access so I need someone to commit on my behalf.
7604 mnemonics. Enforce this on the assembler side, and disentangle command
7605 line option handling on the disassembler side accordingly.
7624 on the FLMAP bit field as specified by the user.
7714 RISC-V: Imply 'Zicntr' and 'Zihpm' implicitly depended on 'Zicsr'
7716 'Zicntr' and 'Zihpm', Which are all implicitly depend on 'Zicsr'.
7718 This is based on:
7750 the same size on every target GDB cares about.
7793 reading pseudo registers in non-current frames on that architecture.
7803 writing pseudo registers to non-current frames on this architecture.
7893 Let's say the user wants to read the ebx register on amd64. ebx is a pseudo
7957 - I do not plan on changing gdbarch_pseudo_register_read to receive a
7959 Instead, we should be working on migrating implementations to use
8042 subsequent patches) to operate on "the next frame". Things become a bit
8043 less awkward when all these functions agree on which frame they take.
8079 complained. I'm wondering which architecture relies on that register
8093 knowing which callers rely on the overflow behavior and which don't.
8124 reg_buffer_common::{raw_supply,raw_collect} operates on `void *`, which
8125 IMO is dangerous. It uses raw_supply/raw_collect directly on
8129 work on uint64_t.
8131 This file also uses raw_collect and raw_supply on `char` pointers.
8133 raw_collect and raw_supply that work on `gdb_byte *` and make an
8134 array_view on the fly using the register's size. Those call sites could
8191 class `reg_buffer_common`, that is the base of regcaches on both sides.
8197 and wants to use an operation defined on reg_buffer_common, it can't.
8205 (like regcache_register_size) to be virtual methods on
8280 some impact on the implementation of the binutils, so this patch
8377 will acquire the GIL based on the current thread. I think this should
8379 gdbpy_readline_wrapper on one thread on behalf of a different Python
8510 gdbserver/win32: fix crash on detach
8651 The implemntation is based on the code from bfd/elfnn-riscv.c. We probably
8716 DAP cancellation needs a way to interrupt whatever is happening on
8789 Tested on x86_64-linux.
8927 to operate on a half-word by the howtos in elf32-mips.c, elfn32-mips.c
8991 Running the H8 port through the GCC testsuite currently takes 4h 30m on my
9006 find the right entry. That's made excessively complex due to the encoding on
9011 instructions that can be disambiguated based on the first nibble (4 bits) of
9012 instruction data and a mapping for those which can be disambiguated based on
9018 on just 0x4X. Ugh!
9023 So what I settled on was to first sort the opcode table by the first nibble,
9028 Next I adjusted the sort so that instructions that are not available on the
9032 The net of the two changes is on my fastest server we've gone from 4:30 to 1:40
9058 Tested on x86_64-linux.
9075 on boxed windows, and then infer that the focus is on the unboxed window.
9088 Tested on x86_64-linux and ppc64le-linux.
9114 Following on from the previous commit, I searched the testsuite for
9170 Building on the last commit, which added a general --debug=COMPONENT
9174 (gdb) monitor set debug COMPONENT off|on
9180 While on the command line it is possible to do:
9190 Notice in the above that I use 'off' and 'on' instead of '0' and '1',
9192 can still be used, but I now advertise off/on in all the docs and help
9203 monitor set debug remote off|on
9204 monitor set debug event-loop off|on
9331 Tested on x86_64-linux.
9346 Regression tested on x86-64 Fedora 38.
9364 I also tested this on a big-endian PPC system (cfarm203).
9510 watchpoints enabled". It sets a watchpoint on ival2, performs an
9519 the assignment to ival2. The watchpoint on ival2 should be triggered
9700 excessive number of threads in the pool on many-core systems. */
9739 Prior to commit 0e3c1eebb2 nm output depended on the host unsigned
9742 unsigned long. The fact that nm output changed depending on host is
9745 it was on 32-bit hosts prior to 0e3c1eebb2.
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
9793 Make breakpoint pending on future shared library load? (y or [n]) y
9841 Tested index-file.exp is fixed on my local machine.
9848 Now that DAP requests are normally run on the gdb thread, some DAP
9883 trailing whitespace on lines.
9978 Don't return without freeing debug_addr_info on error paths.
9988 when "contents" should be freed, costing a little extra on an error
10111 While working on gdb's .debug_names writer, I found a couple of small
10167 relative on count/index, and compare and jump / branch relative
10181 offset. Note that this is never the case on s390, as
10230 of threads on many-core systems under environments with restrictive
10247 on a many-core system.
10258 to control the number of worker threads spawned on many-core systems.
10259 This value was chosen as testing recorded on bugzilla issue 29959
10275 The new test relies on "gdb: install CLI uiout while processing early
10279 The clamping was tested on machines with both 16 cores and a single
10295 through current_uiout), and as a result code that depends on
10301 interpreter, which relies on having Python available during its
10322 I've not added a test in this commit. The next commit relies on this
10353 Tested on x86_64-linux.
10362 When using GDB on native linux, it can happen that, while attempting
10424 My colleague, Andrew Burgess, has done some recent work on other
10488 Fix ld/x86: reduce testsuite dependency on system object files
10493 ld/x86: reduce testsuite dependency on system object files
10578 gdb.arch/aarch64-sme-core-3.exp (on AArch64 Linux, in qemu). This is
10637 Fix right shifts in mcore simulator on 64 bit hosts.
10676 prompt again, so we don't need to rely on timeouts. With this, the
10733 on the following insn.
10756 Fix these two warnings, when building on macos:
10855 but I am not aware of any project that depends on the currently
10908 Build & tested on top of trunk.
10910 Also build on top of gdb-14-branch, and observed this in gdb/config.log:
10941 procfs.c doesn't currently compile on Solaris:
10959 Tested on amd64-pc-solaris2.11.
10984 Tested on i386-pc-solaris2.11 with as and gas.
11048 Rely on copy elision in scope-exit.h
11050 rely on copy elision in C++17. This patch makes the change.
11056 Rely on C++17 <new> in new-op.cc
11057 gdbsupport/new-op.cc has a comment about relying on the C++-17 <new>
11128 guide has a new section on the gprofng GUI.
11206 if there is user code in the wild that relies on raising an exception
11220 gdbpy_print_stack_or_quit(), but then carry on as if
11311 Tested on x86_64-linux.
11334 separates multiple commands on a single line.
11350 up in my testing about 2.5x sha1 build-id processing (in my case on
11360 Tested on x86_64-linux, both on Intel i9-7960X (which doesn't have
11361 sha_ni ISA support) without/with the patch and on AMD Ryzen 5 3600
11417 But one thing is pretty annoying. When a test fails on some random
11421 I always run with --keep-results on, so, in this commit, I propose
11422 that, when --keep-results is on the 'make check' command will be
11444 calls are ordered based on the entries within the cooked_index, and
11445 the ordering within cooked_index depends on the number of worker
11464 uses (maintenance set worker-threads NUM) would have an impact on the
11469 later depending on whether a particular CU moves between threads.
11581 load the GDB executable into GDB (for creating an on-disk debug
11617 gdb.base/vfork-follow-parent.exp on powerpc64 (likewise on s390x).
11679 Tested on top of trunk on x86_64-linux and ppc64le-linux.
11680 Tested on top of gdb-14-branch on ppc64-linux.
11690 When running test-case gdb.base/vfork-follow-parent.exp on powerpc64 (likewise
11691 on s390x), I run into:
11694 exec_file=vfork-follow-parent-exit: target-non-stop=on: non-stop=off: \
11722 incorrect result: it should always return false, given that we're running on a
11749 Tested on top of trunk on x86_64-linux and ppc64le-linux.
11750 Tested on top of gdb-14-branch on ppc64-linux.
12276 fallback XSAVE layout based on the included registers. This fallback
12309 Tested on x86_64-linux.
12328 lets us correctly report failures on Windows.
12345 It seems better to simply have the serial open functions throw on
12395 While working on cancellation, I noticed that a DAP 'pause' request
12449 an integer must be iterable, and we call PyObject_GetIter on it. When
12517 Tested on x86_64-linux and pinebook.
12522 I ran test-case gdb.python/tui-window-disabled.exp on a configuration without
12546 Tested on x86_64-linux.
12557 which warns on seeing null characters. However, it's perfectly valid
12570 allowing to shrink the table even on 32-bit builds, this results in
12608 want to err on the safe side.
12677 instructions that operate on high and low words of registers. They
12779 positive offsets. Linux on zSeries in ESA mode executes in 31-bit
12784 Linux on Z in z/Architecture mode executes in 64-bit addressing mode.
12823 MIPS/GAS: Fix test failures due to jr encoding changes on r6
12860 decl_field on 64-bit hosts.
13217 the 'V' extension. This encoding space conflict is not on
13253 …In AIX, while we followed the child process and detach on fork was on we hit thr!= NULL assertion …
13306 Tested on x86_64-linux.
13357 Tested on x86_64-linux.
13396 Tested on x86_64-linux, with both python 3.6 and 3.11.
13581 According to the function comment though, it should return -1 on error:
13616 AIX.") on x86_64-linux, I see:
13642 Tested on x86_64-linux.
13790 When running test-case gdb.base/catch-syscall.exp on a pinebook (64-bit
13830 Tested on pinebook.
13863 section into memory allocated on the stack with alloca(). However, the
13888 This patch corrects the oversight. I tested this by using readelf on
13898 be stored. However, on exit the ABI does not guarantee that r3 has not
13901 DW_TAG_call_site information to determine the value of r3 on entry to
13909 The patch fixes the one regression error for the test on PowerPC.
13911 The patch has been tested on Power 10 and X86-64 with no regressions.
13959 Following on from this commit:
13969 a target: prefix (files located on a possibly remote target machine).
13997 improve GDB's handling of the main executable being a file on a remote
14012 to check if the underlying, on-disk file has changed, then the bfd
14013 library will actually use fstat on the underlying file descriptor.
14014 This is of course slightly different than using system stat on with
14015 the on-disk file name.
14017 If the on-disk file has changed then system stat will give results for
14018 the current on-disk file. But, if the bfd cache is still holding open
14019 the file descriptor for the original on-disk file (from before the
14020 change) then fstat will return a result based on the original file,
14054 lie hidden until an on-disk file just happens to change at the wrong
14058 library from continually having to re-open the on-disk file. If we
14062 we will end up opening and closing the same on-disk file multiple
14074 changes the on-disk file(s) then we would like GDB to notice this
14081 inferior event arrives we want GDB to notice any changes to on-disk
14135 out later on that the frame has been changed.
14142 as a regression on gdb.dwarf2/dw2-out-of-range-end-of-seq. Since that
14215 (parse_error): Clear deferred symbol list on error.
14217 symbols to symbol table on successful parse.
14310 issues on 32-bit hosts as well as IL32LLP64 cases such as mingw64).
14363 helpful for cancellation. I am still working on that, but meanwhile
14417 use on pre-386 CPUs. The latter, also affecting other (real) prefixes,
14502 compile.exp generally does not work for me on Fedora 38. However, I
14659 bit fuzzy.
14669 While in the failing case, we have (note remarks on the rhs):
14696 If you run gdb in the build tree without --data-directory, on a
14716 Doing this on behalf of Arsen as obvious. Hopefully the last fixup.
14724 Doing this on behalf of Arsen as obvious.
14742 …ost_modules): Replace intl module with gettext module. (configure-ld): Depend on configure-gettext.
14803 on a misconception I had about Symbol.is_variable. This patch fixes
14826 While working on static links, I noticed that the DAP scopes code does
14906 Tested on x86_64-linux.
14914 to eliminate '.*' for better control on what is matched. Also,
14955 non-stop=on: displaced=off: i=0: continue
14963 FAIL: gdb.threads/stepi-over-clone.exp: third_thread=false: non-stop=on: \
14977 Tested on x86_64-linux, specifically:
14989 This commit builds on the previous commit, and implements the
14996 is modelled heavily on how GDB's Python frame unwinders are
15111 If the debug information is still not found then GDB carries on
15113 the GDB loads it and carries on,
15116 information. GDB loads the contents of this file and carries on.
15190 mingw toolchain on a Linux machine, GDB seems to still access the
15217 toolchain on a Linux host. After compiling the binary and splitting
15258 Tested on x86_64-linux.
15301 Tested on x86_64-linux.
15321 - calculate the smaxrow and smaxcol variables based on the sminrow and
15324 Tested on x86_64-linux.
15335 The gdb.ada/inline-section-gc.exp test may pass or fail depending on the
15336 version of gnat. Per the discussion on IRC, the ada inlining appears to
15352 This patch fixes the single regression failure for the test on PowerPC.
15353 It does not introduce any failures on X86-64.
15391 Cancel execution command on thread exit, when stepping, nexting, etc.
15394 target), and you step over thread exit with scheduler-locking on, this
15471 If GDB sets the GDB_THREAD_OPTION_EXIT option on a thread, then if the
15559 Even though that thread is not on the remote-reported thread list, it
15560 is still on the GDB thread list, due to the special case in remote.c
15571 described, we need to record early on that we want to report a
15582 on", and you step over a function that spawns a new thread, the new
15584 which point, whether the new thread is re-resumed depends on a number
15592 clone events on Linux, and of target_thread_events() on targets where
15604 Normally, if the last resumed thread on the target exits, the server
15606 GDB_THREAD_OPTION_EXIT option on a thread, and, that thread exits, the
15627 …eads/step-over-thread-exit.exp: displaced-stepping=off: non-stop=on: target-non-stop=on: schedlock…
15628 …eads/step-over-thread-exit.exp: displaced-stepping=off: non-stop=on: target-non-stop=on: schedlock…
15644 …d-exit-while-stop-all-threads.exp: displaced-stepping=off: target-non-stop=on: iter 0: continue (t…
15706 Fix this by explicitly enabling/re-enabling target async on targets
15715 gdb: clear step over information on thread exit (PR gdb/27338)
15721 looks like with displaced-stepping, on x86-64 Linux, where we have two
15757 the main thread, waiting on pthread_join, is unblocked. It spawns a
15758 new thread, which hits the breakpoint on the syscall again. However,
15902 Move deleting thread on TARGET_WAITKIND_THREAD_EXITED to core
16055 reports clone events or not, on a per-thread basis.
16059 exit events on per-thread basis too, the packet introduced here is
16061 set of options at once, modelled on Linux ptrace's PTRACE_SETOPTIONS.
16072 For example, this packet sets option "1" (clone events) on thread
16078 option "1" (clone events) on thread p1000.2345:
16265 The solution implemented here is to model clone on fork/vfork, and
16301 more thorough. The testcase passes on native GNU/Linux, but fails
16312 gdb/linux: Delete all other LWPs immediately on ptrace exec event
16313 I noticed that on an Ubuntu 20.04 system, after a following patch
16416 The crash with gdb.threads/step-over-exec.exp is not observable on
16420 libthread_db for the post-exec inferior, and, on such systems that
16428 then GDB crashes on newer systems as well. So instead of tweaking
16432 on Linux native, which also exposes the stale LWP problem with an
16484 Tested on x86_64-linux.
16517 Tested on x86_64-linux.
16704 (Qt5WebEngine) didn't build anymore on x86 32bit due to address
16751 We decide to emit BTI stubs based on the instruction at the target
16881 FEAT1|FEAT2, the meaning of which depends on context and requires
16952 The patch has been tested on Power 8 LE/BE, Power 9 LE/BE and Power 10 LE
16969 The unwinder bug shows up on platforms where the kernel uses a trampoline
16978 However, on PowerPC the bug is dormant as well as it is hidden
16991 valid frame exposing the pre-existing bug in how the signal handler on
16999 .debug_frame on Linux. PowerPC uses different mapping for .eh_frame and
17000 .debug_frame on other operating systems. The current GDB support for
17008 the DWARF register mappings on Linux. Function
17018 Additional detail on the signal handling fix.
17020 The specific sequence of events for handling a signal on most
17027 However on PowerPC the sequence of events is:
17037 handler. However, on some platforms such as PowerPC, the kernel actually
17050 The patch has been tested on Power 8 LE/BE, Power 9 LE/BE, Power 10 with
17063 The problem is that for these targets GDB relies on a call to
17088 Of course, this is only a problem when GDB is running on a target that
17089 relies on update_thread_list calls to learn about new threads,
17129 Which was my main motivation for working on this commit.
17266 * po/bfd.pot: Regenerate.
17281 * po/bfd.pot: Regenerate.
17295 * po/bfd.pot: Regenerate.
17307 * Atomic bit clear on quadword in memory (ldclrp{a|l|al});
17308 * Atomic bit set on quadword in memory (ldsetp{a|l|al});
17395 Regression tested on aarch64-linux-gnu, no regressions.
17421 Regression tested on aarch64-linux-gnu, no regressions.
17447 When compiling gdb with -fsanitize=address on ARM, I get a crash in test
17453 …==23295==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xb4a14fd1 at pc 0x01a48871 bp 0…
17455 Since it doesn't require running the program, it can be reproduced locally on a
17460 `bpaddr - boundary`. Normally, on ARM, all instructions are aligned on
17493 ld/x86: reduce testsuite dependency on system object files
17690 Fix this by resetting m_inner_window on every resize, it will anyways
17758 such that we only fail on the line:
17773 While working on background reading of DWARF, I came across the
17785 errors do not prevent gdb from continuing on to the extent possible.
17787 Regression tested on x86-64 Fedora 38.
17944 Tested on powerpc64le-linux.
17957 which are enabled on using Guarded Control Stack (+gcs flag)
17998 gprofng: remove dependency on help2man
18053 When running test-case gdb.tui/tui-layout-asm-short-prog.exp on AlmaLinux 9.2
18119 Tested on x86_64-linux.
18129 Tested on x86_64-linux.
18139 open DAP bugs on this topic), so this patch renames duplicates to
18222 Regression tested on x86-64 Fedora 38.
18262 Fix fixed-point "return" on ARM
18272 Fix range-type "return" command on ARM
18281 Fix "finish" for vector types on ARM
18295 Fix "finish" with range types on ARM
18306 Fix calls with small integers on ARM
18348 While working on background DWARF reading, I found a race case that I
18362 Regression tested on x86-64 Fedora 38.
18385 make it easy for users to easily build new GDB on currently
18508 created on-demand though to reduce unnecessary work.
18511 reading inferior memory based on gdb.Value.address and
18603 breakpoints ahead of the detach. The 'set debug remote on' trace
18633 The problem is that, as a result non-stop being on, the process
18640 The second problem I ran into was on the gdb side, as the process has
18670 while working on another patch, which did manage to trigger this
18707 Tested on x86_64-linux.
18780 gdb::unique_xmalloc_ptr<char> (or nullptr on error).
18800 is caught before we leave handle_v_run. I am working on a patch that
18803 follow on patch never arrives.
18807 the assignment could only trigger on the first iteration of the loop,
18809 always starts as nullptr, so, on the first loop iteration, if we have
18884 NULL howto. Don't abort on stack errors or on unexpected relocs.
18901 Tested on x86_64-linux.
18930 Tested on x86_64-linux.
18953 Make this conditional on GDB_SELF_TEST.
18955 Tested on x86_64-linux.
19084 (make_enum_header, ENDSENUM): Put start and end braces on
19086 * reloc.c: Remove uses of COMMENT and edit ENUMDOC paragraphs.
19139 In the case of python pygments, it autodetects which language to use based on
19144 Tested on x86_64-linux.
19218 (ctf_set_array): Likewise. Report errors on the child; require
19225 * ctf-string.c (ctf_str_add_ref_internal): Report ENOMEM on the
19254 Build on x86_64-linux.
19292 Regression tested on x86-64 Fedora 38.
19464 This trips on the fact that svr4_copy_library_list uses memcpy to copy
19586 reference (&&). Change the type of the method to be auto-deduced as an
19616 on global state other than accessing current_program_space.
19705 nodiscard depending on the configuration[1] (when compiled with C++17).
19727 ctf-types.c (ctf_type_resolve_unsliced): Return CTF_ERR on error.
19744 Tested on x86_64-linux.
19753 Tested on x86_64-linux.
19765 Tested on x86_64-linux.
19815 executed on the Windows platform.
19833 Tested on x86_64-linux.
19856 Tested on x86_64-linux.
19878 Tested on x86_64-linux.
19907 This header is only suitable for use on x86 hosts and is only included
20038 Tested on x86_64-linux.
20069 being used to return a couple different answers depending on the
20102 reliably on Arm, as that is the only architecture that faces this problem
20105 Regression-tested on Ubuntu 20.04. OK?
20127 is based on the thread's regcache gdbarch, which is set in
20346 cache holds a file descriptor for an open on-disk file, this can, on
20356 needed, and then uses fstat on the open file descriptor.
20358 What this means is that, if the on-disk file changes, but the cache
20435 This patch makes the shift count automatically adjust based on the size of the
20459 When execute the following command on LoongArch:
20484 Here is a simple test on LoongArch:
20591 we do on it. This will help by:
20593 - allowing to break on those methods when debugging
20665 This helped me by allowing putting breakpoints on set_arch to know when
20777 Tested on x86_64-linux.
20807 Tested on x86_64-linux, with target board unix and cc-with-gdb-index.
20922 [gdb/testsuite] Fix gdb.arch/i386-signal.exp on x86_64
20959 Tested on x86_64-linux, with target boards:
20972 fixes auxv.exp on kernels >= v6.3.
20999 gdb.threads/process-dies-while-detaching.exp on aarch64-linux. On this
21008 We are relying on gdb_continue_to_breakpoint to return the result of
21014 Tested on aarch64-linux.
21084 - Updated comment on args_test,
21106 I believe this smaller fix brings some benefits on its own, though the
21141 I believe this smaller fix brings some benefits on its own, though the
21284 It turns out that the extra backslash is injected on the gdbserver
21307 I believe this smaller fix brings some benefits on its own, though the
21368 Make breakpoint pending on future shared library load? (y or [n]) n^M
21412 With gcc-10, we set a breakpoint on the mangled minimal symbol. That
21420 Tested on x86_64-linux:
21461 Some callbacks relied on current_program_space, and following
21481 gdb: add program_space parameters to some auto-load functions
21489 gdb: use objfile->pspace in auto-load.c
21511 relies on the current program space, so I didn't add a parameter to that
21528 It was pointed out on the mailing list that a recently added
21540 failure really doesn't even rely on the new functionality added in the
21666 can't rely on the current inferior having any relationship with the
21668 in the commit a2827364e2bf, the only thing we can rely on is the
21729 delete it on error, then we might delete an address space that is
21735 call completely, and just rely on the reference count to auto-delete
21789 Fix: ld: Test case pr28158 fails on x86_64-linux-musl when index is > 19
21797 Fix: ld testsuite: glibc-specific DT_RELR tests should not be run on musl systems
21801 Fix: ld testsuite: non-PIC shared tests fail on powerpc-linux-musl
21805 Fix: ld testsuite: Thumb PLT and GOT tests should be skipped on musl armhf targets
21810 Fix: ld testsuite: pr22001-1 test segfaults on musl/x86
21813 …* testsuite/ld-i386/i386.exp: Skip the pr22001 test with TEXTREL relocations enabled on configurat…
21819 executable to be debugged is located on the remote machine, like this:
21917 objfile and tries to check if the file has changed on disk by calling
21930 'bfd_stat'. Calling bfd_stat on an in-memory BFD works just fine,
21983 stderr, the string followed by the result of calling strerror on the
22024 There were a couple of tests that depended on the existing output
22043 build on a Solaris machine, and I don't believe that I've broken
22053 While working on some other patch I noticed that in reread_symbols
22057 The code in question is checking to see if an objfile has changed on
22058 disk, we do this by stat-ing the on disk file and checking the mtime.
22076 indicate that the problem being addressed was seen on Darwin. I'm not
22094 Fix: ld testsuite: 'Version' pattern grabs 'Version5 EABI', breaking test on arm-linux-musleabihf
22161 Validated on the Fast Models.
22168 Teach gdb about the ZT state on signal frames and how to restore
22196 sme2: Enable SME2 for AArch64 gdb on Linux
22201 The target description is dynamic and gets generated at runtime based on the
22262 Regression-tested on aarch64-linux Ubuntu 22.04/20.04.
22278 description notes in the corefiles or to rely on the
22280 description for a given thread based on the various available register notes.
22297 the AArch64 Linux hook to rely on those notes.
22299 Regression-tested on aarch64-linux Ubuntu 22.04/20.04.
22312 dynamically-generated target descriptions/gdbarch depending on the vector
22317 changed during execution, this would not reflect on the core file, as gdb
22355 Regressions-tested on aarch64-linux Ubuntu 22.04/20.04.
22371 number of pseudo-registers and types that gets cached on creation of each
22393 Regression-tested on aarch64-linux Ubuntu 22.04/20.04.
22401 Teach gdb about the ZA/SSVE state on signal frames and how to restore
22410 Regression-tested on aarch64-linux Ubuntu 22.04/20.04.
22429 Regression-tested on aarch64-linux Ubuntu 22.04/20.04.
22449 Ideally we'd adjust the packet size dynamically based on what we need, but
22456 Thiago is working on this improvement, which hopefully will be able to be
22485 use to add expedited registers on-by-one depending on the target description
22501 In streaming mode, the SVE registers have their sizes based on svl rather than
22518 is based on the vector length register SVG (VG for SVE).
22531 otherwise they may have a size bigger than 16 bytes (depending on the current
22548 Tested on aarch64-linux Ubuntu 22.04/20.04.
22605 I used the opportunity to fix this, and it gets tested later on by
22608 I do plan on submitting some SVE-specific tests to make sure we have
22611 Regression-tested on aarch64-linux Ubuntu 22.04/20.04.
22625 Regression-tested on aarch64-linux Ubuntu 22.04/20.04.
22641 Regression-tested on aarch64-linux Ubuntu 22.04/20.04.
22734 gdb/corefile: write NT_GDB_TDESC based on signalled thread
22818 Following on Tom de Vries' work in the other array-printers, this
22849 information on section downloading and the new command.
22892 Tested on x86_64-linux.
22918 Tested on x86_64-linux:
22959 depend on there being an initial inferior, so I really don't think we
23062 Regression tested on x86-64 Fedora 38.
23210 In any case, this commit is based on one of Red Hat's really old
23215 Testing on Fedora 38 (correctly) shows 1 unsupported test for
23248 I'm starting to work on these files, I thought it would be a good time
23305 "set detach-on-fork off").
23322 -ex "set breakpoint pending on" \
23341 Tested on x86_64-linux.
23445 check on the executable file, and only calls exec_file_attach if the
23446 executable has changed on disk since it was last loaded.
23451 modification time, if the file on disk has changed then we reload the
23481 going on here, it just follows the same pattern as many of the other
23488 if the same executable changed on disk and has been reloaded, or is
23522 whole new path, or if GDB just spotted that the executable changed on
23701 support XSAVE layouts."), the test gdb.base/gcore.exp fails on my AMD
23732 to figure out the layout of the XSAVE area based on what features are
23753 notes in kernel-generated cores on this machine have size 832. So this
23758 Note that if PKRU was enabled on my machine, then the effective XSAVE
23784 Fix: nm: SEGV on unknow address at nm.c:718 in print_symname
23790 [gdb/testsuite] Add nopie to gdb.base/unwind-on-each-insn-amd64-2.exp
23791 When running test-case gdb.base/unwind-on-each-insn-amd64-2.exp with target
23794 gdb compile failed, ld: unwind-on-each-insn-amd64-21.o: relocation \
23801 other test-cases that source unwind-on-each-insn.exp.tcl and use a .s file.
23803 Tested on x86_64-linux.
23862 With this, the test passes cleanly on Cygwin [1]. Still passes cleanly on
23992 Broadcast needs to be specified on the memory operand.
24038 Bug 29965 shows on a Linux kernel >= 6.1, that test fails consistently
24051 Add an xfail in the test, based on the Linux kernel version. The goal
24053 should be caught if running on an older kernel where the behavior was
24065 When running test-case gdb.ada/mi_task_arg.exp on openSUSE Tumbleweed using
24099 Tested on x86_64-linux.
24109 qualifications. Tested on x86-64 Fedora 36.
24167 Tested on x86_64-linux.
24174 Following on from the previous patch to make the feature macros take
24237 Tested on x86_64-linux:
24246 A user pointed out that the build failed on FreeBSD/amd64 with my last
24251 Tested both on FreeBSD/amd64 and FreeBSD/aarch64 by rebuilding.
24259 …4 bytes of space. Due to this when we do a stepi on paddi instruction we get a SIGILL interrupt. H…
24563 * bfd/arc-got.h (TCB_SIZE): Depends on the target architecture.
24668 I see these errors on FreeBSD/aarch64 when using gcc 12 without passing
24697 Tested on FreeBSD/aarch64 by rebuilding.
24822 set on a raw address will have only the "address" field populated, but
24836 Run 'black' on printing.py
24881 6. Input: set tui mouse-events on.
24923 Tested on x86_64-linux.
24952 * elf-attrs.c (elf_new_obj_attr): Return NULL on bfd_alloc fail.
24957 (_bfd_elf_copy_obj_attributes): Report error on alloc fails.
24964 error on out of memory from bfd attribute functions.
25000 Note that the non-DWARF readers are changed on a "best effort" basis.
25101 Regression tested on x86-64 Fedora 38.
25141 The unit test fails on 32-bit systems due to wrapping overflow. Fix this by
25144 Tested on x86_64-linux.
25212 ROCm / HIP tests should only run on Linux for now, existing gdb.rocm
25277 with an old version of Bison (2.3, the version available on macOS).
25357 unnecessarily, thus preventing the files from being updated on some
25456 …$ gdb -q -nx -iex 'set auto-load no' -iex 'set debuginfod enabled off' -ex file ./libgraph_tool_in…
25488 package on Fedora. The Fedora bugzilla bug can be found here:
25497 …$ gdb -q -nx -iex 'set auto-load no' -iex 'set debuginfod enabled off' -ex file ./libgraph_tool_in…
25509 My testing on Fedora 38 shows no regressions.
25553 Using valgrind on the failing GDB binary pointed straight to the cause
25557 If anyone has ideas for a test I'm happy to work on something.
25565 I've been running the test-suite on an i686-linux laptop with 1GB of memory,
25569 So I investigated the memory usage, on my usual x86_64-linux development
25581 gdb_test "maint set per-command space on"
25636 This is dependent on malloc (which can use either mmap or sbrk or some
25647 auto iter = std::find (all_values.begin (), all_values.end (), mark);
25693 Tested on x86_64-linux.
25707 Tested on x86_64-linux.
25721 Recognize "/<number>" suffixes on both -march=+avx10.1 and the
25722 corresponding .arch directive, setting an upper bound on the vector size
25731 course this new attribute could also be used on other insns.)
25759 very much wanted in order to then put AVX10.1 support on top. Note that
25780 * elf.c (_bfd_elf_init_reloc_shdr): Don't segfault on alloc fail.
25822 I see the following warning when building GDB on FreeBSD/amd64 with
25869 Tested on FreeBSD/amd64 by rebuilding.
25949 gdb/testsuite: fix gdb.arch/amd64-init-x87-values.exp on AMD CPUs
25950 I see the following failure when running this test on an AMD machine:
25969 differently on AMD CPUs. In section "11.4.4.3 FXSAVE and FXRSTOR
25983 unmasked in the x87 FPU control register (which isn't by default on
25985 fioff as GDB calls it) will always be 0 on an AMD CPU.
26032 Run 'black' on recent test case
26033 The auto-builders pointed out that I neglected to run 'black' after a
26038 Set insn_type for branch instructions on aarch64
26040 But insn_type is always zero on aarch64.
26108 Tested on x86_64-linux.
26125 Make breakpoint pending on future shared library load? (y or [n]) n^M
26134 Tested on x86_64-linux.
26154 Tested on x86_64-linux.
26169 Tested on x86_64-linux.
26179 gdb: MI stopped events when unwindonsignal is on
26200 After this commit gdb.mi/mi-condbreak-throw.exp now passes on all
26272 statements meant to generate a line table entry at that line on which
26273 to break later on.
26310 Ifort (2021.6.0, -O0 -g) on the other hand does not emit anything here
26320 As I do not think that this is really a bug (on either side, gfortran/ifx or
26410 * kvx-dis.c (kvx_reassemble_bundle): Return bool, true on success.
26441 varobj_set_display_format takes an enum and exhaustively switches on
26498 Tested on x86_64-linux.
26548 Tested on x86_64-linux.
26593 Tested on x86_64-linux.
26610 Regression tested on x86-64 Fedora 38.
26709 This patch fixes that problem, and another that could occur on an
26714 blow away entire notes obstack on a missing string.
26763 Tested on x86_64-linux.
26790 When doing a lookup on a PU, the user link is followed until we end up at a CU,
26798 Tested on x86_64-linux.
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
26856 dependencies on libraries (libgprofng, libopcodes, libbfd, etc).
26860 Tested on aarch64 and x86_64 with and without --enable-shared and --target=<>.
26890 gdb/testsuite: Disable some tests that are broken on remote Windows host
26901 hardwired "/" pathname separators in them, which broke when testing on
26909 gdb/testsuite: Fix style.exp failures on targets without argc/argv support
26964 only works on the newest frame, so be sure to select it before
26987 updated to set the "GNAT-specific" flag on an array type.
26995 the DWARF reader to set this on Rust types. This will be used as a
27080 This is based on the "Hardware Updating of PTE A/D Bits (Svadu)"
27105 enabled on the privileged specification version 1.10 or later.
27110 This is based on the specification version v1.0_rc1 (Frozen):
27158 > The hypervisor extension depends on an "I" base integer ISA with 32 x
27259 Tested on x86_64-linux.
27299 The problem is on the gdbserver side, the zmmh and ymmh portions of the
27321 binaries (running on $build) in cases where $host is $build or
27328 for $host binaries that runs on $build; that is, it's appropriate to
27457 Replace with a new equivalent "is_packed" method on struct field.
27516 ternop_slice_operation. While working on another series, it was
27628 maybe_copied field is dependent on the objfile in the context of
27636 depending on whether the objfile is mainline. So maybe_copied
27638 based on that.
27713 sectioning commands, and (2) that some users are stuck on very ancient
27754 Tested on x86_64-linux, verified with shellcheck.
27760 vms-alpha: Free memory on failure path
27761 * vms-alpha.c (evax_bfd_print_eobj): Free rec on failure.
27769 or some obstack so that it doesn't show as a memory leak on exit.
27770 s_stab_generic at least does allocate the name for the stab section on
27836 Tested on x86_64-linux.
27847 Tested on x86_64-linux.
27858 Tested on x86_64-linux.
27885 Tested on x86_64-linux.
27935 Tested on x86_64-linux.
27951 Tested on x86_64-linux.
27998 elf: Check DT_SYMTAB only on non-IR object
27999 Check DT_SYMTAB only on non-IR object of archive member to avoid crash
28000 on LLVM IR object with NULL elf_tdata.
28004 DT_SYMTAB only on non-IR object.
28050 Tested on x86_64-linux, with make-check-all.sh.
28106 RV32 invalid (it just makes XVentanaCondOps on RV32 empty).
28120 objdump: Free sorted_syms on error path
28124 * dwarf.c (process_debug_info): Call free_abrev_list on
28163 Tested on x86_64-linux.
28230 can work on any size of array, so it seems bad to use alloca.
28238 When running this test on a processor that supports AVX512 (AMD EPYC
28239 9634) on Debian 12 bookwork (system compiler is gcc 12.2.0), I see:
28273 Tested on x86_64-linux.
28290 Tested on x86_64-linux.
28303 Tested on x86_64-linux.
28324 Tested on x86_64-linux.
28374 When running test-case gdb.reverse/getrandom.exp on a system with eglibc 2.19,
28398 Tested on x86_64-linux and i686-linux.
28425 Tested on x86_64-linux.
28442 various loops working on the ZMM XSAVE region so that all of the
28447 X86_XSTATE_ZMM was set on i386 (e.g. a 32-bit process on a 64-bit
28587 set offsets based on known combinations of XCR0 masks and total state
28622 To date, GDB has assumed the layout used on current Intel processors
28625 fails on recent AMD processors which use a different layout.
28669 Tested on x86_64-linux.
28739 Tested on x86_64-linux.
28746 Tested on x86_64-linux.
28763 Tested on x86_64-linux.
28889 For one thing, there are no build dependencies on it, so there's no
28917 The included test fails without the patch on my system. However, I
28921 Regression tested on x86-64 Fedora 38.
28983 Fix gdb/coffread.c build on 32bit architectures
28985 uintptr_t argument. Use PRIxPTR instead. Which works on any architecture
29136 While touching the function invocation, stop using |= on the result of
29199 However, when listing shared objects loaded on the AMDGPU devices, we
29200 might list SOs loaded on the unsupported devices. If such SO is
29245 Tested on x86_64-linux.
29317 code checks for an infinite loop by seeing if we land on the line that
29460 [gdb/build] Run black on make-target-delegates.py
29461 Run black on make-target-delegates.py to fix buildbot build breaker.
29463 Tested on x86_64-linux.
29491 Tested on x86_64-linux.
29594 gdb: MI stopped events when unwindonsignal is on
29621 However, while working on another patch I realised that there was a
29623 commits considered 'set unwindonsignal on'. With this setting on,
29630 This commit fixes this by ensuring that when unwindonsignal is 'on',
29655 unwindonsignal on' is in effect, and
29658 exception, and 'set unwind-on-terminating-exception on' is in
29679 -ex 'set unwindonsignal on' \
29709 -ex 'set unwindonsignal on' \
29739 -ex 'set unwindonsignal on' \
29765 -ex 'set unwindonsignal on' \
29789 worth the effort. If the user has selected to unwind on signal, then
29934 - None of the interpreter ::on_thread_exited functions rely on the
29937 - None of GDB's thread_exit observers rely on the silent parameter
29953 does depend, at least a little, on this commit. In order to get the
29976 on the list the reasons for seem to have been lost[1]. Given there
30010 std::make_unique later on.
30032 Though the changes that were added were not wrong, while working on a
30144 It is generally a good idea to avoid signed arithmetic on values
30145 extracted from object files, to avoid ubsan warnings on overflow.
30248 Tested on x86_64-linux.
30263 This patch removes this call. Regression tested on x86-64 Fedora 36.
30398 anyway, and it doesn't make much sense to error on unexpected arch or
30408 * kvx-dis.c (kvx_dis_init): Return void. Don't error on
30424 Add files submitted on the mailing list but somehow not committed.
30433 The BPF virtual machine does not support neg instructions operating on
30441 source bit, despite operating on registers. If BPF_SRC_X (=1) is set,
30445 on immediates, so remove them.
30460 neg32 instructions operating on immediates.
30828 A final note on the implementation: currently, inferior specific
30840 I have a series on the mailing list[1] that implements this
30853 When building gdb with -O2 -flto on openSUSE Tumbleweed (using bison 3.8.2) I
30868 Tested on x86_64-linux.
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.
30927 Tested on x86_64-linux.
30947 Tested on x86_64-linux.
30964 Tested on x86_64-linux.
30973 10713 | auto do_op = [=] (LONGEST x, LONGEST y)
30982 Tested on x86_64-linux.
30999 Tested on x86_64-linux.
31016 Tested on x86_64-linux.
31034 Tested on x86_64-linux.
31051 - making the copy-to-remote conditional on is_remote target, and
31057 Tested on x86_64-linux.
31130 While working on a dwarf assembly test-case I accidentally created the
31162 Tested on x86_64-linux.
31219 I ran into a test failure on gdb.python/py-thread-exited.c. The test
31227 When running on a loaded system I ran into a case where the threads
31240 It was pointed out on the mailing list[1] that after this commit:
31255 The reason that these failures don't show up when run on the standard
31257 so for Linux this will be all-stop on top of non-stop.
31260 with target-non-stop turned off, then we see the same failures on the
31264 possible to turn on non-stop mode and have the test still work, so
31277 In the test that fails, GDB sets 'detach-on-fork off' and then runs to
31284 The test script then sets 'schedule-multiple on' and once again
31296 1. All-stop-on-non-stop before commit b1e0126ec56e,
31298 2. All-stop-on-non-stop after commit b1e0126ec56e,
31300 3. All-stop-on-all-stop before commit b1e0126ec56e, and
31302 4. All-stop-on-all-stop after commit b1e0126ec56e.
31309 For #1 All-stop-on-non-stop before commit b1e0126ec56e, what happens
31313 multiple is on user_visible_resume_ptid returns -1 (everything)
31316 2. As this is all-stop-on-non-stop, every thread is resumed
31326 5. At this point we might take two paths depending on which event
31346 For case #2, all-stop-on-non-stop after commit b1e0126ec56e, the
31361 If we now consider case #3, all-stop-on-all-stop before commit
31365 multiple is on user_visible_resume_ptid returns -1 (everything)
31368 2. As this is all-stop-on-all-stop, the resume is passed down to the
31384 all-stop-on-non-stop above, GDB selects one of the events to
31388 And so, finally, we can consider #4, all-stop-on-all-stop after commit
31392 -1 (resume everything), due to schedule multiple being on. And just
31409 and place it in proceed, but only on the all-stop-on-non-stop
31421 What I noticed was that for the all-stop-on-non-stop, after commit
31429 the parent and child based on which the user wishes to follow. So, I
31435 Having done that, now the process is for all-stop-on-all-stop after
31456 all-stop-on-non-stop after commit b1e0126ec56e, that is, the
31504 Added inferior 2 on connection 1 (native)
31534 the *_current_source function always looks up a location based on the
31569 18446744073709551615 (2**64-1) to detect invalid immediate errors on -1.
31570 However, it heavily depends on the fact that the value used to print
31626 This is based on:
31644 including auto-compression without C prefix and explicit C prefix.
31706 Tested on x86_64-linux. Also tested with byacc rather than bison on
31786 stopped rather than individual LWPs. In FreeBSD one can only wait on
31853 Tested on x86_64-linux.
31879 Tested on x86_64-linux.
31903 Tested on x86_64-linux.
31925 Tested on x86_64-linux.
31964 Tested on x86_64-linux.
32060 Tested on x86_64-linux, with target boards unix and cc-with-gdb-index.
32134 Test results were otherwise very good, so Zhiyong was definitely on
32154 "on" from the loop for non-stop as it was failing on all architectures
32163 Running the new test on a Raspberry Pi w/ a 32-bit (Arm) kernel and
32167 …exec-other-thread.exp: fork_func=fork: target-non-stop=auto: non-stop=off: displaced-stepping=auto…
32168 …-exec-other-thread.exp: fork_func=fork: target-non-stop=auto: non-stop=off: displaced-stepping=on:…
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…
32171 …exp: fork_func=fork: target-non-stop=off: non-stop=off: displaced-stepping=on: i=11: next to other…
32173 …xec-other-thread.exp: fork_func=vfork: target-non-stop=auto: non-stop=off: displaced-stepping=auto…
32174 …exec-other-thread.exp: fork_func=vfork: target-non-stop=auto: non-stop=off: displaced-stepping=on:…
32175 …FAIL: gdb.threads/next-fork-exec-other-thread.exp: fork_func=vfork: target-non-stop=auto: non-stop…
32176 …exec-other-thread.exp: fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=auto:…
32177 …-exec-other-thread.exp: fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=on: …
32178 …p: fork_func=vfork: target-non-stop=off: non-stop=off: displaced-stepping=auto: i=1: next to break…
32179 …xp: fork_func=vfork: target-non-stop=off: non-stop=off: displaced-stepping=on: i=10: next to break…
32195 …exec-other-thread.exp: fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=auto:…
32196 …-exec-other-thread.exp: fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=on: …
32218 Running the new test on x86-64 and aarch64, both native and
32243 implemented this change, but only on the generated file rather than in
32266 PR bootstrap/106472: Add libgo depends on libbacktrace to Makefile.def
32290 Tested on x86_64-pc-linux-gnu.
32310 Tested on x86_64-pc-linux-gnu.
32323 Tested on x86_64-pc-linux-gnu.
32338 in D itself. Because the compiler front-end only depends on the core
32354 development on the D programming language and run-time libraries.
32373 on it.
32406 * libtool.m4 (archive_cmds): Add +nodefaultrpath ld option on
32411 Generic configury support for shared libs on VxWorks
32413 shared libs on VxWorks ports configured with --enable-shared,
32420 on accurate dependency information between libstdc++ and libgcc_s
32585 all-target-libgm2 and on=all-target-libatomic. (languages)
32640 The latest versions of Darwin on the Aarch64 platform mandate PIE executables.
32645 host_shared on (we issue a diagnostic if the user tries to configure them
32654 override the setting. These versions must also switch host_pie on even if it
32712 However, on at least Darwin, the shared version will be picked
32737 Bootstrapped and regtested on loongarch64-linux-gnu.
32782 on the value of VAROBJ_UPDATE_RESULT.TYPE_CHANGED. If the value is true,
32786 The VAROBJ_UPDATE_RESULT.TYPE_CHANGED value is true on PowerPC which
32802 is true on PowerPC and false on X86-64.
32804 Fixes 2 failures on PowerPC.
32821 While working on a GNAT bug, I wanted to also test
32825 Tested on x86-64 Fedora 36. I am checking this in.
32831 function based on the actual valid range of vlen. In bytes, vlen is 0,
32960 Since this "extension" does not exist (on the other hand, 'Zve64d' exists)
33017 for (const auto &entry : m_deferred_entries)
33057 Tested on x86_64-linux.
33113 Tested on x86_64-linux.
33120 The frame command on Power pc prints the address in hex between the
33131 address. Currently, SAL.IS is false on PowerPC and true on X86-64.
33135 Fixes two failures on PowerPC.
33137 Patch tested on Power10 with no new regressions.
33145 I'm not sure if this is documented anywhere, but it is mentioned on
33153 better to arrange for such notification if something on the gdb side
33175 No regressions on aarch64-none-elf.
33199 Tested on x86_64-linux.
33216 Tested on x86_64-linux, with target boards unix and cc-with-debug-names.
33241 Tested on x86_64-linux, using target boards unix and cc-with-debug-names.
33274 set debug breakpoint on|off
33282 (gdb) set debug breakpoint on
33351 Tested on x86_64-linux.
33375 When testing current gdb trunk on Solaris/amd64, the whole session was
33379 FAIL: gdb.arch/amd64-disp-step.exp: add into rcx: send_signal=on: get
33381 Executing on target: kill -ALRM -1 (timeout = 300)
33389 Tested on amd64-pc-solaris2.11 and x86_64-pc-linux-gnu.
33412 Tested by building with and without -stdc=++11 on x86_64-linux.
33480 not break any existing scripts which rely on it. Unless of course they
33481 rely on SIZEOF being rejected.
33524 Tested on x86_64-linux.
33572 Regression tested on x86-64 Fedora 38.
33629 Tested on x86_64-linux.
33633 [gdb/symtab] Fix data race on dwarf2_per_cu_data::{files_read,is_debug_types}
33638 gdb -q -batch -iex "set index-cache enabled on" index-cache \
33719 Tested on x86_64-linux.
33726 [gdb/symtab] Fix data race on dwarf2_per_cu_data::{mark,is_debug_types}
33731 gdb -q -batch -iex "set index-cache enabled on" index-cache \
33810 Tested on x86_64-linux.
33838 Tested on x86_64-linux.
33846 [gdb/symtab] Fix data race on dwarf2_per_cu_data::{m_header_read_in,is_debug_type}
33964 Tested on x86_64-linux.
33973 [gdb/symtab] Fix race on dwarf2_per_cu_data::{queued,is_debug_type}
34075 Tested on x86_64-linux.
34084 [gdb/symtab] Fix data race on bfd::{cacheable,format}
34188 Tested on x86_64-linux.
34197 [gdb/symtab] Fix data race on index_cache::m_enabled
34206 set index-cache enabled on
34271 "set index-cache enabled on" command.
34278 (due to command "set index-cache enabled on").
34283 Tested on x86_64-linux.
34300 This fixes miscounting of dynamic relocations on GOT entries when
34339 Make breakpoint pending on future shared library load? (y or [n]) n^M
34438 Tested on x86_64-linux, with target boards unix and cc-with-gdb-index.
34468 What is happening is that FrameDecorator falls back on returning the
34469 PC when the frame's function symbol cannot be found, relying on the
34475 appear to be in the next function in memory. For more on this, see:
34553 &"To change this behavior use \"set unwindonsignal on\".\n"
34582 and we should rely on whoever announced the stop to ensure that we
34591 state based on whether the inferior call completed successfully
34610 And on return from fetch_inferior_event GDB will display the prompt
34668 is just wrong. There needs to be a check on the return value in order
34737 * config/tc-xtensa.c (xtensa_add_config_info): Use auto buffer
34749 auto rather than malloc'd buffer. Use sprintf count.
34769 on xmalloc.
34789 Seen on Ubuntu 23.04 x86_64-linux using gcc-12.2 and gcc-12.3 with
34823 While working on another patch I triggered a segfault from within the
34850 This is based on:
34879 See related issue (the author raised) on the vector specification:
34903 - on an earlier first use.
34905 Tested on x86_64-linux.
34943 gprofng: Fix build with 64bit file offset on 32bit machines
35015 However, it's clear from gdb.log on Linux:
35043 output is gated on the client "supportsMemoryReferences" capability.
35168 gas: rework timestamp preservation on doc/asconfig.texi
35173 can be observed on e.g. Cygwin. Replace the use of -p by a use of touch,
35211 Tested on x86_64-linux.
35304 point) and eventually pushes the amd-dbgapi-target on the inferior's
35318 amd-dbgapi-target is pushed on the inferior target stack. This implies
35342 This patch has been tested on a system with multiple GPUs which had more
35343 chances to reproduce the original bug. It has also been tested on top
35352 It is not possible to debug multiple processes simultaneously on all
35625 Tested on x86_64-linux.
36149 on the per-ABI framework to get things right, removing this regression:
36166 targets, however the unaligned JALX tests insist on running across all
36328 The 'Zvkt' extension is listed on the added extensions in the GNU Binutils
36601 Tested on x86_64-linux.
36637 Tested on x86_64-linux.
36667 gdb.dwarf2/typeddwarf.exp with target board native-gdbserver on Ubuntu
36712 Tested on x86_64-linux.
36743 Tested on x86_64-linux.
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
36767 -flto=auto and gcc 7.5.0").
36771 Tested on x86_64-linux.
36803 However, when building gdb with -O2 -flto=auto, the static destructor calling
36817 Tested on x86_64-linux.
36858 Tested on x86_64-linux.
36934 Don't warn on .attach_to_group to same group
37011 RISC-V: Enable RVC on ".option arch, +zca" etc.
37048 RISC-V: Prohibit the 'Zcf' extension on RV64
37051 the 'Zcf' extension does not exist on RV64. This is reflected on the
37284 While working on an experiment, I realized that I needed the DAP
37304 operating on the sibling thread, so I think it makes sense, for
37330 For *reasons* I was hacking on gdb.base/foll-vfork.exp and wanted to
37360 Tested on x86_64-linux.
37367 Tested on x86_64-linux, with target boards unix and readnow.
37541 Ada 2022 adds the "target name symbol", which can be used on the right
37585 based on CGEN. Please see that commit log for more information.
37588 implementation is much simpler and it is based on the new BPF opcodes.
37680 ROCm programs can load a high number of compute kernels on GPU devices,
37693 the same file is re-opened every time a code object is loaded on a GPU.
37704 I have tested this patch on downstream ROCgdb's full testsuite and
37711 x86: adjust disassembly of insns operating on selector values
37742 There's a difference in behaviour depending on symtab expansion state:
37769 Regression tested on x86_64-linux.
37880 Tested on x86_64-linux, no regressions.
37918 failed assert if they are run on an inferior that is not yet started.
37940 While on some ports like on AMD GPU we have thread-specific address
37960 No regressions on native and extended-gdbserver x86_64 GNU/Linux.
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:
38009 Tested on x86_64-linux.
38017 It is possible to build huge binaries on powerpc64, where 32-bit
38021 * powerpc.cc (Target_powerpc::Relocate::relocate): Warn on
38068 some instructions depend on other existed extension, like 'zba', 'zbb'
38182 While working on some of the recent patches relating to vfork handling
38192 While working on gdb.base/foll-vfork.exp I noticed that there are
38217 * target-non-stop on/off
38218 * non-stop on/off
38219 * schedule-multiple on/off
38221 We don't test with schedule-multiple on if we are using a remote
38228 when running this test on a very loaded machine -- I usually run ~8
38258 In this case the issue occurs when target-non-stop is on, but non-stop
38259 is off, and again, schedule-multiple is on. As with the previous
38280 schedule-multiple is on we select minus_one_ptid (see
38283 5. As GDB is running in all-stop on top of non-stop mode, in the
38312 10. Depending on timing both of these events might seem to arrive in
38318 in target/waitstatus.h on TARGET_WAITKIND_VFORK_DONE indicates that
38335 13. While this has been going on the vfork parent is executing, and
38340 request will be cached on the lwp_info object,
38396 … gdb: fix handling of vfork by multi-threaded program (follow-fork-mode=parent, detach-on-fork=on)
38401 (gdb) set non-stop on
38481 This is the same condition that already exists in the all-stop on a
38487 what's going on, and second, instead of checking 'non_stop' I've
38511 While working on a later patch, which changes gdb.base/foll-vfork.exp,
38517 mode being on, target-non-stop being off, follow-fork-mode being set
38527 2. GDB resumes the vfork child process. As schedule-multiple is on
38556 9. Depending on timing both of these events might seem to arrive in
38562 in target/waitstatus.h on TARGET_WAITKIND_VFORK_DONE indicates that
38579 12. While this has been going on the vfork parent is executing, and
38584 request will be cached on the lwp_info object,
38738 having two .plt sections (marked SPECIAL) on some backends foils that
38791 Tested on x86_64-linux.
38800 This commit builds on this earlier work:
38878 Tested on x86_64-linux.
38941 While working on this series, I noticed a some oddities in
38960 Regression tested on x86-64 Fedora 36.
38966 on a "bare" native target inferior without an attached process.
38969 Move logic from auto-connect-native-target.exp into this helper.
38980 For example on Linux x86-64:
38996 For example on FreeBSD/amd64:
39070 gprofng: 30602 [2.41] gprofng test hangs on i686-linux-gnu
39110 * objcopy.c (copy_archive): bfd_close ibfd and obfd on error
39117 Making target code depend on a host define like _AIX52 is never
39121 in binutils. The gas define of AIX_WEAK_SUPPORT on the other hand was
39122 wrong, so fix that. Finally, fix some testsuite fails on aix < 5.2 by
39126 * coff/internal.h (C_WEAKEXT): Don't depend on _AIX52.
39128 * coffcode.h (coff_slurp_symbol_table): Don't depend on _AIX52.
39166 This fixes an uninitialised memory access on a fuzzed file:
39176 program headers are swapped in. Do not fail on eu-strip debug
39193 Tested on x86_64-linux.
39207 Tested on x86_64-linux.
39223 Tested on x86_64-linux.
39245 Tested on x86_64-linux.
39269 Tested on x86_64-linux.
39309 * bfdtest1.c: Enhance to catch errors on second scan.
39321 * bs15503.exp - these have been commented out forever and rely on
39330 * exception.exp - the code relying on the line numbers can't work,
39365 x86: various operations on mask registers can avoid going through mod_table[]
39435 glibc on a 32-bit distro.
39454 Regression tested on x86-64 Fedora 38.
39470 check is_constant on the symbols it returns.
39505 discovered when working on related DAP changes.
39683 early return, so the test would then carry on and try to actually
39735 The main name was extracted by trying to set breakpoints on both MAIN_
39748 logical.exp: fortran_character1. Ran ptype on "c".
39821 failure when attempting to set a breakpoint on a malformed symbol name.
39829 Make breakpoint pending on future shared library load? (y or [n]) y
39857 Regression tested on F38 x86_64.
39896 Regression tested on x86-64 Fedora 36.
39943 small strings are stored on the stack.
39968 however, there was push back on that thread due to it adding extra
39969 dynamic allocation, i.e. moving the memory buffers off the stack on to
39977 could be any size, and so should not be placed on the stack.
39986 memory... but I'm leaving that for a follow on patch.
40030 comment on type::length() we see this:
40073 The ARC HS5x and ARC HS6x processors are based on the new ARCv3 ISA
40090 gdb/testsuite: fix license on recently added file
40091 The license header on a file I recently contributed was incorrect.
40123 instead of ptrace. That change broke reading shared libraries on
40125 libraries on SPARC64").
40151 Tested on a SPARC64 GNU/Linux and x86-64 GNU/Linux.
40161 target is LE, but on BE arch it will byte swap the
40169 PR tdep/30252 reports that using GDB on Solaris fails an assertion in
40213 target_wait (which leads to procfs_target::wait on Solaris) is called
40214 with inferior_ptid == null_ptid on entry exactly to help catch such
40230 on inferior_ptid.
40412 The new use is still not on a hot path -- it's going to be a Python
40460 PyModule_AddObject steals a reference on success, but not on error,
40462 calling the former, which could in theory leak memory on failure.
40488 Here is a GDB session on an x86-64 machine which loads the core file
40564 support in this area, but these problems were discussed on the mailing
40584 non-idle cores will have the pid of whichever process was running on
40670 To understand what's going on we need some background; a vmcore file
40676 process currently running on that core as the thread's lwpid.
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.
41401 This patch is based on an earlier version from Tsukasa OI:
41702 be realized on LA64 with any of `addi.w`, `addi.d` or `ori`. If we tie
41767 SFrame stack trace format has an unaligned on-disk representation. Add
41880 For a toy application on x86_64, for example, following is the SFrame
41889 is of type SFRAME_FDE_TYPE_PCMASK (denoted by the [m] on LHS).
42055 Section header isn't mandatory on ELF executable nor shared library.
42450 to fall back on the libtool's -export-symbols option for platforms where
42785 Tested on x86_64-linux.
42912 A user on irc noticed a missing backslash on one line in
42933 This is on a CentOS 7 distro for powerpc64le.
42946 Tested on powerpc64le-linux and x86_64-linux.
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
42977 Tested on x86_64-linux.
43022 tuiterm session look less like a session on an actual xterm.
43035 Tested on x86_64-linux.
43043 # a regexp matching the line to wait for. Return 0 on timeout, 1
43044 # on success.
43055 Tested on x86_64-linux.
43077 Only %LV should continue on to S handling; avoid emitting a stray 'l'
43086 also leaks on closing the bfd.
43094 * mach-o.c (bfd_mach_o_write_symtab_content): Free strtab on
43172 on such AVX512 templates.
43229 * elf32-mips.c (gprel32_with_gp): Don't segfault on NULL
43368 Tested on x86_64-linux.
43379 Tested on x86_64-linux.
43415 Tested on x86_64-linux.
43446 Tested on x86_64-linux.
43458 on openSUSE Leap 42.3, with python 3.4, I run into a
43464 Tested on x86_64-linux.
43480 Tested on x86_64-linux.
43488 # This test can only be run on x86 targets.
43496 Tested on x86_64-linux.
43527 Tested on x86_64-linux.
43536 Tested on arm-linux-gnueabihf.
43665 and on looking into the bfin targets a little, discovered we have two
43691 In test-case gdb.base/step-over-exit.exp, we set a breakpoint on _exit and
43733 Tested on x86_64-linux.
43760 buffer and goes further in freeing the buffer on any bfd_close.
43780 (do_s_func): Likewise on error path. strdup label.
43793 on error paths.
43817 output match on a different line.
43825 Tested on x86_64-linux.
43862 Tested on x86_64-linux.
43871 Tested on x86_64-linux.
43893 Tested on x86_64-linux.
43899 symbol_needs_eval_timeout.exp invalidly dereference an int (4 bytes on
43925 is the size of an address on the target machine."
43939 Tested on x86_64 Linux.
43984 >From what I can understand, the auto detection leverages the
44069 Co-workers who work on a program that uses DAP asked for the ability
44168 Note that the copyright dates on the new test source file are not
44184 This patch relies on the new MI command execution support to do its
44234 With a gdb 13.2 based package on SLE-15 aarch64, I run into:
44264 Tested on x86_64-linux.
44272 With a gdb 13.2 based package on openSUSE Tumbleweed i586, I ran into:
44285 I can reproduce the same issue with gdb trunk on x86_64, by using optimize=-O3
44290 Tested on x86_64-linux.
44300 Tested on x86_64-linux.
44318 This commit implements a fix for a bug reported against GDB on
44324 program (which is a command-line JSON processor) on Fedora 37. Since
44328 on Fedora 38, GDB says that the value of 'value' has been optimized
44332 That said, on Fedora 37, the bug could be reproduced as follows:
44337 This GDB supports auto-downloading debuginfo from the following URLs:
44341 To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
44344 Make breakpoint pending on future shared library load? (y or [n]) y
44410 DWARF assembler, the test case does not depend on a specific compiler
44413 Tested on Fedora 37 and Fedora 38.
44459 pltN entries on x86_64.
44481 Tested on x86_64-linux.
44511 Tested on x86_64-linux.
44523 Tested on x86_64-linux.
44530 A GDB crash was discovered on Fedora GDB that was tracked back to an
44533 The bug was reported on Fedora 37, 38, and 39. Here are the steps to
44567 > gdb -nx -q -iex 'set trace-commands on' \
44568 -iex 'set debuginfod enabled on' \
44571 +set debuginfod enabled on
44655 …==80377==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x603000068034 at pc 0x564785cba…
44749 Regression tested on x86-64 Fedora 36.
44819 Tested on x86_64-linux.
44851 There was a comment in the code assuming that if the file was found on
44893 we try to call bfd_make_section_anyway on an already closed BFD, which
44973 Tested on x86_64-linux.
44998 Tested on x86_64-linux, against system readline 7.0 on openSUSE Leap 15.4.
45005 Fix PR30369 regression on aarch64/arm (PR30506)
45018 Regression-tested on aarch64-linux/arm-linux Ubuntu 20.04/22.04 and
45029 While working on PR tui/30526, I noticed a bug in test-case
45041 Tested on x86_64-linux.
45053 (gdb) PASS: gdb.threads/step-N-all-progress.exp: non-stop=on: \
45054 target-non-stop=on: continue to breakpoint: break here
45059 FAIL: gdb.threads/step-N-all-progress.exp: non-stop=on: target-non-stop=on: \
45071 Tested on x86_64-linux.
45077 test still fails on hpp64-linux. Let's make it pass for hppa64-linux
45083 While running this test on an emulator, I noticed we're failing to match the
45090 Tested on aarch64-linux Ubuntu 20.04/22.04.
45115 * vms-lib.c (vms_lib_read_index): Free malloc'd memory on error
45121 on set_group_contents failure return path.
45286 variation on the first.
45445 Tested on x86_64-linux.
45479 Tested on x86_64-linux.
45499 csym against remaining space for symbols. Error on out of bounds
45566 4. ld-elf/shared.exp: non-run on mips: Build libpr16496b.so
45569 no-run on mips: vers24a, vers24b, vers24c
45574 no-run on mips/linux: PR ld/12982
45592 Test on:
45773 Tested on x86_64-linux.
45900 Tested on x86_64-linux.
45935 Tested on aarch64-linux Ubuntu 20.04/22.04.
45942 * opncls.c (_bfd_delete_bfd): Don't segfault on NULL xvec.
46077 other hand, if bfd_free_cached_info is called we can't do much on the
46099 (coff_real_object_p): Return coff_object_cleanup, and call on
46205 Tested on x86_64-linux.
46228 Tested on x86_64-linux.
46234 …* coffcode.h (coff_write_object_contents): Handle base64 encoding on PE. Also check for too large…
46279 Tested on x86_64-linux.
46355 options are the print formatting options. However, this relies on
46357 functions handle. We could possibly rely on strictly positional
46371 and printed entirely on the GDB side, we are able to print arrays as
46399 depending on it, but I am proposing that we don't push $_as_string in
46405 function in the inferior), or 'agent' (perform the dprintf on the
46413 support for '%V' will depend on the inferior function being called.
46416 any restrictions on the format string when operating in 'call' style.
46689 over all UIs and calls the signal_received method on the interpreter.
46709 approach of using virtual methods on the interpreters seems like a good
46738 Tested on x86_64-linux.
46828 * testsuite/gas/all/align.d: Mark as unsupported on LoongArch.
47019 Tested on x86_64-linux.
47024 I stumbled on the mi_proceeded and running_result_record_printed
47031 3. Use -exec-run on the second interpreter
47033 This is the output I get on the first interpreter:
47044 And this is the output I get on the second intepreter:
47054 is printed on the wrong UI. It is printed on the first one, it should
47055 be printed on the second (the one on which we sent the -exec-run).
47173 Tested on x86_64-linux.
47270 Tested on x86_64-linux.
47279 Tested on x86_64-linux.
47299 Tested on x86_64-linux.
47343 This first of all removes a dependency on bfd_byte and unsigned char
47415 ia64-linux-gnu: "Explicit stops are ignored in auto mode"
47432 xfail the linker optimisation on targets known to fail.
47441 Regression tested on x86-64 Fedora 36.
47568 - Add methods for the various manipulations that need to be done on the
47744 to implement the new overload based on that, but it seemed simpler to
47749 amd-dbgapi-target.c, on needs the amd-dbgapi library, which I don't
47861 performed on the associated stream. However, the application shall
48102 based on rbp, while clang adds the same constant to rsp that it
48216 Tested on x86_64-linux.
48252 on x86_64-linux.
48260 on x86_64-linux.
48323 for coff_set_section_contents. This is all quite OK, but I was on a
48324 mission to remove unnecessary declarations in coffcode.h, and on
48327 ATTRIBUTE_UNUSED or written "static bool ATTRIBUTE_UNUSED" on the
48396 Tested on x86_64-linux.
48429 While working on the previous patch I reverted this commit:
48504 However, both of those tests are really focused on other issues, so I
48543 It was pointed out on the mailing list that the new tests added in
48716 running on boards where the inferior I/O is on a separate TTY than
48781 In the current code, when execute the following test on LoongArch:
48794 not a real function addresss. Depending on the compiler implementation,
48815 by calling elf_gnu_ifunc_record_cache(). Based on the IFUNC working
48908 on x86_64-linux.
48974 Well, it doesn't work on x86 or ppc, which both have # starting
48975 comments anywhere on a line. I think it is therefore only useful on
48980 (obj_elf_section): Only support solaris .section directive on
49020 Found when attempting to build binutils on sparc sunos-5.8 where
49095 Tested on x86_64-linux.
49124 Run black on gdb.python/py-disasm.py file and commit the changes.
49152 buildbot notified me of a regression on s390 in the test:
49172 munmap on a page of the inferior's code. The test is checking that
49187 If this location happens to be on the same page as the page that the
49206 After this the test should pass again on the impacted targets.
49268 methods on the DisassembleInfo class: DisassembleInfo.text_part and
49291 The reason that parts are created by calling methods on
49321 The current API relies on returning a DisassemblerResult object to
49324 user tries to override the various attributes that exist on the
49430 cases INSERT handling looks for the specified output section later on
49527 Regression tested on x86-64 Fedora 36.
49556 sometimes depending on how the user is trying to print the object.
49614 While working on this patch I realised that I could actually improve
49662 The DW_OP_constu pushes a value with "generic type" on to the DWARF stack, and
49663 the "generic type" has the size of an address on the target machine, which for
49678 Tested on x86_64-linux.
49706 Tested on x86_64-linux.
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.
49781 IV. gdb output wrapping, auto-detected screen size
49794 So what happened here? With TERM=ansi, the width setting is auto-detected to
49828 Tested on x86_64-linux.
49947 Calling `breakpoint_auto_delete' on all kinds of stops (in
50059 Tested on x86_64-linux.
50067 While working on another patch I did this:
50119 * debug.c (debug_write_type): Don't segfault on NULL indirect.
50155 -ex "maint set tui-left-margin-verbose on" \
50170 but with compact-source on:
50247 With the fixes, we get for compact-source on:
50262 Tested on x86_64-linux.
50284 check_longjmp_breakpoint_for_call_dummy iterates on all breakpoints,
50313 …==47472==ERROR: AddressSanitizer: heap-use-after-free on address 0x611000034980 at pc 0x563f7012c7…
50490 This was regression-tested on X86-64 Linux.
50634 Now from python.c we can call static functions on the
50718 newline sequence. Now we rely on gdb.exp to match the complete
50742 Tested on x86_64-linux.
50751 While working on some other patch I broke GDB such that this warning:
50797 Regression tested on x86-64 Fedora 36.
50810 Regression tested on x86-64 Fedora 36.
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
50821 Tested on x86_64-linux.
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
50832 Tested on x86_64-linux.
50870 '-stack-list-variables' and so on) take a PRINT-VALUES argument which
50919 There are two ways we could fix this problem, depending on whether we
50983 gas: fix building tc-bpf.c on s390x
50984 char is unsigned on s390x, so there are a lot of warnings like:
51048 is called first, adding a check on is_linked ():
51073 Tested on x86_64-linux.
51116 Each new frame_info_ptr is being pushed on a static frame list and g++
51216 * auto-load.c (auto_load_objfile_script): Update type of
51370 I'd like to move some things so they become methods on struct ui. But
51383 Regression tested on x86-64 Fedora 36.
51392 evaluate_expression is just a little wrapper for a method on
51411 This changes field_is_static to be a method on struct field, and
51414 Regression tested on x86-64 Fedora 36.
51440 cannot auto-wrap lines, and reserves one column to deal with that, and as a
51495 Tested on x86_64-linux.
51513 Since readline can't detect very basic terminal support, it falls back on
51519 Tested on x86_64-linux.
51567 Tested on x86_64-linux.
51588 Tested on x86_64-linux.
51599 maint set tui-left-margin-verbose on^M
51600 Undefined maintenance set command: "tui-left-margin-verbose on". \
51602 (gdb) FAIL: gdb.tui/main.exp: maint set tui-left-margin-verbose on
51607 Tested on x86_64-linux.
51620 =cmd-param-changed,param="print pretty",value="on"
51674 place a breakpoint on a non-existent thread. The only test we had
51675 that depended on the old behaviour was
51683 I certainly didn't intend for this test to rely on this feature of the
51700 we should treat requests like this, on both the MI and CLI, as another
51705 Make breakpoint pending on future thread creation? (y or [n]) y
51786 While working on set/show args I also rewrote show_args_command to
51952 Regression tested on x86-64 Fedora 36.
52173 it should otherwise have been equivalent to the old code relying on
52176 populates the tree and only then does lang_add_section on the sorted
52191 based on section flags is now done last, and only in lang_add_section).
52212 register does not update any auxiliary state, e.g. $npc on SPARC,
52329 on this. In this commit I've removed all these unneeded trailing '.'
52362 However, I'm not a fan of (relying on) this implicit return value
52364 this commit I have extended the comment on gdb_test_no_output to
52371 The two tests gdb.base/auxv.exp and gdb.base/list.exp both rely on the
52383 While working on a later patch in this series, which tightens up some
52660 Tested on x86_64-linux.
52670 failure on amd64 macOS. It turns out to be somewhat difficult to
52690 I can't test this on native fbsd, but I'm fairly confident it should
52700 Regression-tested on aarch64-linux Ubuntu 20.04/22.04.
52706 Bit twiddling is best done unsigned, due to UB on overflow of signed
52723 accesses everywhere. I don't expect binutils will work on anything
52733 That doesn't work. Those variables ought to be passed on the runtest
52744 * Makefile.am (check-DEJAGNU): Pass $CC and other variable on
52767 input_radix. Note that the current code may fail to restore it on
52776 them cleans up the code. Regression tested on x86-64 Fedora 36.
52785 on a long list of loaded files. I've originally retained using
52822 With my_getSmallExpression() consistently and silently failing on
52847 with the same O4 or O2, so avoiding errors earlier on doesn't really
52886 Tested on x86_64-linux.
52909 Tested on x86_64-linux.
52987 The first part fails to match on a line:
53022 Tested on x86_64-linux.
53051 Tested on x86_64-linux.
53073 Tested on x86_64-linux.
53082 # expected result, and carry on.
53104 Tested on x86_64-linux.
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
53134 Tested on x86_64-linux.
53140 -O2 -g -flto=auto, I run into:
53165 -O2 -g -flto=auto, I run into timeouts due to the breakpoint in c_print_type
53168 Tested on x86_64-linux.
53179 Tested on x86_64-linux.
53215 Tested on x86_64-linux.
53223 Tested on x86_64-linux.
53227 [gdb/testsuite] Fix gdb.multi/multi-arch.exp on powerpc64le
53228 When running test-case gdb.multi/multi-arch.exp on powerpc64le-linux, I run into:
53248 Tested on:
53266 Tested on x86_64-linux.
53282 Tested on x86_64-linux.
53327 When running the dap tests on a system with tcl 8.5, we run into:
53343 Tested on x86_64-linux.
53366 -mfix-looongson3-llsc may add sync instructions not needed on some
53424 Tested on x86_64-linux.
53430 - rebase on trunk
53445 Tested on x86_64-linux.
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.
53486 depends on current_language being set, but my testsuite runs haven't
53494 appears to "normalize" this value from "unknown" to "auto", remove
53506 language_mode (auto vs manual), which are set by the
53562 Shell-checked and tested on x86_64-linux.
53570 While working on PRs tui/30337 and cli/30346 I came across various notions of
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
53648 Tested on x86_64-linux.
53656 A recent change in opcodes/i386-dis.c caused a build failure on my
53683 guarantees that r3 will be preserved by the callee, so checking r3 on
53728 I've added a new test case that is based on the internal AdaCore test
53729 that provoked this bug. However, I'm unable to test it as-is on
53875 on xcoff archives generated by binutils/ar. I agree there might still
53920 Add a SECURITY.txt file describing the GNU Binutils' project's stance on security related bugs.
54122 gdb.base/whatis-ptype-typedefs.exp on PowerPC with IEEE float 128 as the
54123 default on GCC. It fixes one regression test failure in
54126 The patch has been tested on Power 10 where GCC defaults to IEEE Float
54127 128-bit and on Power 10 where GCC defaults to the IBM 128-bit float. The
54128 patch as also been tested on X86-64 with no new regression failures.
54253 The dependence on help2man to create the man pages has been eliminated.
54264 The work on the documentation has not been completed, but this is
54323 inferiors when they appear, but won't push itself on the inferior's
54348 inferior having an additional target on top:
54374 context_switch will be done on the full target stack that reported the
54430 ... since linux-nat tries to do a ptrace call on tid 1.
54524 that the amd-dbgapi target isn't pushed on the inferior's target stack
54525 right away. It attaches itself to the process and only pushes itself on
54544 same, depending on the `set follow-exec-mode` setting. But even if they
54635 Tested on x86_64-linux.
54708 there that will crash on connection to the above targets.
54740 Regression-tested on aarch64-linux Ubuntu 20.04/22.04.
54747 In the current code, when execute the following test on LoongArch:
54757 These tests passed on the X86_64,
54777 We check the "&intarray" on different target as follow:
54829 Tested on x86_64-linux.
54843 seems to assume that symfile_bfd_open will return NULL on error,
54926 Tested on x86_64-linux.
54933 With a hello world a.out, and maint set tui-left-margin-verbose on, we have
54991 Tested on x86_64-linux.
55032 set to on replaces the spaces in the left margin with either '_' or '0',
55074 Tested on x86_64-linux.
55226 encoding on RISC ISAs than masking with '0xf0 << 24' before shifting.
55363 different set of options for limiting hardware watchpoints on remote
55372 on a riscv64 target. It turns out the cause of the problem is that I
55401 Tested for regressions on native aarch64-linux.
55407 Handle unwinding from SEGV on Windows
55409 leave gdb unable to "bt" on Windows.
55418 No test case because I can't run dejagnu tests on Windows. I tested
55481 No impact on ld, which does not do cu-mapped links or pass
55494 are set on error and left unchanged on success. This means that all
55499 There are many places in libctf where we carry out operations on parent
55500 dicts as a result of carrying out other user-requested operations on
55501 child dicts (e.g. looking up information on a pointer to a type will
55503 type it's a pointer to in the parent). Those operations on the parent
55504 might fail; if they do, the error must be correctly reflected on the
55505 child that the user-visible operation was carried out on. In many
55520 (ctf_func_type_info): Set the error on the right dict.
55530 generating CTF for it. This only works if the host, on which
55604 Tested on x86_64-linux.
55621 Tested on x86_64-linux.
55669 gdb: fix reg corruption from displaced stepping on amd64
55681 entry on the stack. This is also fixed in this commit.
55691 removing some manual memory management. Regression tested on x86-64
55731 gdb: run black code formatter on gdbarch_components.py
55738 gdb: fix reg corruption from displaced stepping on amd64
55740 This commit just runs black on the file and commits the result.
55759 which allows the argument type to be checked early on. Currently, if
55781 as user code _could_ be relying on this, but I think the improvement
55782 is worth the risk, user code relying on the exact exception type is
55810 For existing code that doesn't use named arguments and doesn't rely on
55818 Following on from the previous commit, this updates
55826 possibility that the user has some code that can operate on either a
55900 gdb: fix reg corruption from displaced stepping on amd64
55904 Displaced stepping is currently supported on AArch64, ARM, amd64,
55982 This commit only aims to address the issue on amd64 for now, though I
56027 patch relied too much on checking the program-counter value in order
56063 objdump -g on gcc COFF/PE files
56087 syms on failure to create sections.
56095 strings in auto buffers.
56100 (stab_method_type): Free args on error return. Correct
56106 (stab_class_method_var): Free memory on error return.
56165 Tested on native aarch64-linux.
56234 under bfd/po/, i.e. in maintainer mode.
56238 slightly wrong too: BLD-POTFILES.in depending on $(BLD_POTFILES) isn't
56283 (parse_coff_struct_type): Don't leak on error return. Copy
56290 Adjust parse_stab call. Call finish_stab on error return.
56321 (stab_demangle_args): Tidy pvarargs refs. Copy *pargs on
56322 success to debug_xalloc memory, free on failure.
56496 To change this behavior use "set unwindonsignal on".
56599 breakpoints on the target, and have also extended the test so that it
56613 return value, so this commit will have no effect on anything. In the
56617 I've also updated the header comments on agent_mem_read to better
56671 To change this behavior use "set unwindonsignal on".
56717 I've added a new test that doesn't rely on Python that checks the
56720 While working on the new test, I spotted that it would fail when run
56736 gdb/riscv: fix regressions in gdb.base/unwind-on-each-insn.exp
56737 This commit builds on the previous one to fix all the remaining
56738 failures in gdb.base/unwind-on-each-insn.exp for RISC-V.
56740 The problem we have in gdb.base/unwind-on-each-insn.exp is that, when
56786 With this implemented then gdb.base/unwind-on-each-insn.exp now fully
56807 After this commit gdb.base/unwind-on-each-insn.exp passes with no
56808 failures on RV64.
56816 This fixes some of the failures in gdb.base/unwind-on-each-insn.exp,
56820 in gdb.base/unwind-on-each-insn.exp, however, that wider fix needed
56824 that some of the failures in gdb.base/unwind-on-each-insn.exp resolved
56827 Here's what's going on:
56854 'foo'. As such, we can't usually rely on scanning right up to the end
56877 There should be no visible change for anyone not turning on debug.
56882 While I was working on the disassembler styling for ARM I noticed that
56898 This commit follows on from the following two commits:
56917 remote-gdbserver-on-localhost board file.
56921 correctly with the remote-gdbserver-on-localhost board file.
56969 Executing on target: kill -9 4513 (timeout = 300)
56989 pattern varies depending on which Python version GDB is linked
57020 for backwards compatibility, the detection should be based on the size of
57030 Tested on AArch64/Linux Ubuntu 20.04.
57090 * dwarf.c (process_abbrev_set): Call free_abbrev_list on errors.
57133 Regression tested on armv7l kernel 5.15.32-v7l+ (Raspbian 11).
57183 Tested on x86_64-linux.
57191 With test-case gdb.threads/threadapply.exp and editing set to on, we have:
57234 Tested on x86_64-linux.
57249 Regression tested on x86-64 Fedora 36.
57329 operand types that are so minor (e.g. only useful on a few instructions)
57373 is invalid on its own), but then it also clears EVEX.B and EVEX.R' plus
57410 on whether BFD64 is enabled), and only if supplied expressions can be
57448 Note that on targets where / starts a comment, --divide needs passing to
57587 - SQRSHR, SQRSHRU and UQRSHR, which operate on lists of two
57590 - SQRSHRN, SQRSHRUN and UQRSHRN, which operate on lists of
57603 - SQCVT, SQCVTU and UQCVT, which operate on lists of two or
57606 - SQCVTN, SQCVTUN and UQCVTN, which operate on lists of
57722 The instructions are predicated on a predicate-as-counter register in
57761 Some SME2 instructions operate on a range of consecutive ZA vectors.
57773 Many SME2 instructions operate on groups of 2 or 4 ZA vectors.
57860 Similarly, the _10 suffix on FLD_SME_size_10 was nonobvious.
57891 on internal libopcodes routines.
57921 based on operand index first, then by error code. Post-parsing
58030 entry to another, depending on the exact nature of the problem.
58067 class. I then looked for cases where the new routines fell back on the
58132 report that directly as a syntax error, rather than rely on the
58214 This patch moves the range checks on ZA vector select offsets from
58219 syntax errors, on the basis that parsing must have succeeded if we get
58541 header comment on value_as_address. The existing header refers to
58546 I've just trimmed the comment on value_as_address to be a brief
58794 buffer is NULL on error return.
58801 syms on error return.
58803 Tidy memory on addr2line failures
58804 * addr2line.c (process_file): Close bfd on error paths.
58972 Tested on x86_64-linux.
59039 Here's an example of what the output looks like on x86-64 (this is
59040 with 'set debug displaced on'). The two interesting lines contain the
59061 single instruction. But on ARM the replacement could actually be a
59090 Tested on x86_64-linux.
59098 Tested on x86_64-linux.
59105 Tested on x86_64-linux.
59112 Tested on x86_64-linux.
59119 Tested on x86_64-linux.
59126 Tested on x86_64-linux.
59204 Tested on x86_64-linux.
59212 Tested on x86_64-linux.
59218 remote-gdbserver-on-localhost using gdb_remote_download.
59220 Tested on x86_64-linux.
59264 Tested on x86_64-linux.
59274 Tested on x86_64-linux.
59280 it uses "spawn -pty", which creates a pty on build, which gdb cannot use on
59283 Tested on x86_64-linux.
59293 Tested on x86_64-linux.
59301 Tested on x86_64-linux.
59314 Listening on port 2346^M
59335 board are the same, spawning something on the target overwrites the fileid on
59340 Tested on x86_64-linux.
59350 When running update-freebsd.sh on FreeBSD, I see the following
59356 It means that each time, when we running the update-freebsd.sh on
59360 Tested by regenerating freebsd.xml on FreeBSD/amd64.
59367 [gdb/testsuite] Fix gdb.server/non-existing-program.exp with remote-gdbserver-on-localhost
59378 But with target board remote-gdbserver-on-localhost I sometimes have:
59393 Tested on x86_64-linux.
59423 Tested on x86_64-linux.
59443 Tested on x86_64-linux.
59450 Executing on host: gcc watch.rs -g -lm -o watch (timeout = 300)
59462 Tested on x86_64-linux.
59484 Tested on x86_64-linux.
59490 value of SIGTRAP on FreeBSD matches the value of GDB_SIGNAL_TRAP, but
59529 Tested on x86_64 and aarch64 (OL8/OL9). No regression.
59593 Tested on x86_64-linux.
59609 Tested on x86_64-linux.
59613 [gdb/testsuite] Skip do_self_tests on remote host
59617 In principle, the host board specifies the location of GDB, on host.
59626 It seems easier to just skip this on remote host.
59632 Tested on x86_64-linux.
59656 While working on 128-bit integer support, I found one spot in Ada that
59732 Tested on x86_64-linux.
59737 Fix test-case gdb.dwarf2/imported-unit-bp-c.exp on remote by removing a
59740 Tested on x86_64-linux.
59748 Tested on x86_64-linux.
59756 Tested on x86_64-linux.
59764 Tested on x86_64-linux.
59768 [gdb/testsuite] Fix gdb.dwarf2/gdb-index.exp on remote host
59769 Fix test-case gdb.dwarf2/gdb-index.exp on remote host using
59774 Tested on x86_64-linux.
59784 Tested on x86_64-linux.
59795 Executing on host: sh -c rm /tmp/tmp.m3L7m2AVkL/*.gdb-index (timeout = 300)
59804 Tested on x86_64-linux.
59813 which doesn't work on remote host.
59821 Tested on x86_64-linux.
59829 Fix this by using "file tail" on the proc argument.
59831 Tested on x86_64-linux.
59869 Tested on x86_64-linux.
59900 segfault on an unmapped 4G array index than silently reading bogus
59953 Sort and comment on union selectors.
59966 * dwarf2.c (scan_unit_for_symbols): Don't leak on duplicate
60001 Tested on x86_64-linux, on openSUSE Leap 15.4 and Fedora 37.
60022 Tested on x86_64-linux.
60049 "set auto-connect-native-target off".
60051 Tested on x86_64-linux.
60092 was a silent regression on openSUSE Leap 15.4 for test-case
60127 Tested on x86_64-linux.
60190 Internal AdaCore DAP testing on Windows has had occasional failures
60196 set on return from start_thread, but it seems possible that the thread
60206 inferior_thread ()/get_current_regcache () on a system with
60291 We also see failures across the testsuite if the tests get executed on a target
60357 opposed to relying on the current register cache. Though we need to make sure
60382 Regression-tested on aarch64-linux Ubuntu 20.04.
60433 Tested on x86_64-linux.
60437 [gdb/testsuite] Fix gdb.cp/m-static.exp regression on Ubuntu 20.04
60460 on Ubuntu 20.04, where the output was instead:
60470 which manifests on openSUSE Leap 15.4 for native and readnow, and on Ubuntu
60481 Tested on x86_64-linux, both on openSUSE Leap 15.4 and Ubuntu 20.04, both with
60547 Tested on x86_64-linux.
60612 The comment on the gdbarch_displaced_step_fixup gdbarch method
60650 failed to adjust some test cases that relied on it. This patch fixes
60667 Tested on x86_64-linux.
60678 Tested on x86_64-linux.
60686 Tested on x86_64-linux.
60693 instead of relocated. This breaks a few tests on systems where that
60728 We can't free "internal" on errors, since bfd_coff_swap_sym_in may
60733 * coffgen.c (coff_get_normalized_symtab): Don't bfd_release on
60773 * peXXigen.c (_bfd_XXi_swap_sym_in): Set SEC_LINKER_CREATED on
60780 Free memory on closing bfds. The COFF close_and_cleanup does more
60792 * macro.c (expand_irp): Free memory on error return paths.
60834 Is causing regression failures on on PowerPC platforms. The regression
60854 The patch has been tested on Power10 and on X86.
60862 Tested on x86_64-linux.
60866 [gdb/testsuite] Add missing quote in remote-gdbserver-on-localhost.exp
60883 Tested on x86_64-linux, by running gdb.testsuite/board-sanity.exp.
60892 Tested on x86_64-linux.
60900 Tested on x86_64-linux.
60908 Tested on x86_64-linux.
60924 Tested on x86_64-linux.
61012 Tested on x86_64-linux.
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
61104 occurs on the last iteration of the loop, when we are comparing to
61224 initial bug report, and a C++ test. The rust example depends on which
61228 depends on symbols from within the C++ source code.
61339 Recent BPF patch removed and renamed the list of relocations based on
61383 After some discussion on the mailing list it was suggested that the
61463 Regen ld/po/BLD-POTFILES.in
61544 should generally allocate on the relevant objfile, regardless of the
61554 should generally allocate on the relevant objfile, regardless of the
61565 should generally allocate on the relevant objfile, regardless of the
61680 Tested on x86_64-linux.
61687 Tested on x86_64-linux.
61694 Tested on x86_64-linux.
61722 Regression tested on x86-64 Fedora 36, though note this setup never
61723 reproduced the bug in the first place. I also tested it by hand on
61854 The patch fixes the behavior of the reverse-finish command on PowerPC to
61855 match the behavior of the command on other platforms, specifically X86.
61856 The patch does not change the behavior of the command on X86.
61858 A new test is added to verify the reverse-finish command on PowerPC
61864 The patch has been tested on Power 10 and X86 processor with no new
61902 Tested on x86_64-linux.
61921 Tested on x86_64-linux.
61928 Tested on x86_64-linux.
61934 REMOTE_TARGET_USERNAME in remote-gdbserver-on-localhost.
61938 Since the setup makes $build/gdb/testsuite on build unreadable for the remote
61942 Tested on x86_64-linux.
61954 Fix/workaround this on some target boards by setting remotedir by default, and
61959 Tested on x86_64-linux.
61965 on build, and then attempt to execute it on target:
61974 Tested on x86_64-linux.
61992 Tested on x86_64-linux.
62015 Tested on x86_64-linux.
62035 Tested on x86_64-linux.
62054 Tested on x86_64-linux.
62059 Even a unary '+' has to be considered arithmetic; at least on x86 in
62113 Tested on x86_64-linux.
62125 on the stack, or how GDB behaves when the inferior is continued and
62140 The test results on LoongArch as follows:
62209 need to be performed are both architecture specific, and dependent on
62222 on aarch64elf32. It does work but some extra warnings are being
62335 This target has its own ld emulation based on aarch64elf.em.
62375 * scripttempl/ft32.sc: Fix breakages from last edit.
62427 forever. We therefore can't use them on dynamic relocations. Fixing
62448 * rddbg.c (read_section_stabs_debugging_info): Don't segfault on
62475 Tested on x86_64-linux.
62485 Make breakpoint pending on future shared library load? (y or [n]) n^M
62499 Tested on x86_64-linux.
62513 Tested on x86_64-linux.
62515 Also tested on openSUSE Tumbleweed, where all tests in the test-case pass.
62519 [gdb/testsuite] Unset DEBUGINFOD_URLS on remote host
62521 local-remote-host-notty and target board native-gdbserver on openSUSE
62524 This GDB supports auto-downloading debuginfo from the following URLs:^M
62536 doesn't work on remote host.
62540 Tested on x86_64-linux.
62549 If a test-case compiles the .S file when executing on remote host,
62567 Tested on x86_64-linux, with host+target board local-remote-host-native.
62644 Tom de Vries pointed out that one DAP test failed on Python 3.6
62670 Tested on x86_64-linux, with all relevant gdb/testsuite/boards/*.exp boards.
62681 Tested on x86_64-linux.
62717 (read_a_source_file): Make last_eol an auto var.
62778 example, it's used in the Python disassembler API, and it is used on
62792 exactly what it says on the tin; represent the required displaced step
62825 based on which is least likely to introduce bugs. I think assuming
62928 pointers that don't depend on other fields within the gdbarch, then I
63028 Following on from the previous commit, this commit removes yet more
63034 be generated for the component, as such setting 'invalid=True' on the
63110 Tested on x86_64-linux.
63124 Tested on x86_64-linux.
63141 Tested on x86_64-linux.
63158 Tested on x86_64-linux.
63174 Tested on x86_64-linux.
63187 effect on remote host.
63199 Tested on x86_64-linux.
63219 Tested on x86_64-linux.
63254 Tested on x86_64-linux.
63275 Tested on x86_64-linux.
63287 only valid on some objfiles, rather than being a global typeprinter. The
63307 Regression tested on x86-64 Fedora 36.
63361 noticed this while working on an earlier patch in this series. This
63424 (e.g. /usr/local/include on FreeBSD) which may also include headers
63535 Tested on x86_64-linux.
63593 Tested on x86_64-linux.
63599 and target board remote-gdbserver-on-localhost, I run into:
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:".
63625 Tested on x86_64-linux.
63631 remote-gdbserver-on-localhost using gdb_download_shlib.
63633 Tested on x86_64-linux.
63801 remote-gdbserver-on-localhost using gdb_remote_download for $touch_file_bin.
63805 on target using remote_download, and using the resulting path.
63807 Tested on x86_64-linux.
63816 * objdump.c (read_section): Report and return an error on
63835 [gdb/testsuite] Fix gdb.threads/multiple-successive-infcall.exp on native-gdbserver
63858 Tested on x86_64-linux.
63862 [gdb/testsuite] Fix gdb.threads/thread-specific-bp.exp on native-gdbserver
63892 broke testing on native-gdbserver.
63897 Tested on x86_64-linux.
63902 Fix test-cases for target board remote-gdbserver-on-localhost by using
63905 Tested on x86_64-linux.
63929 Tested on x86_64-linux.
63957 Tested on x86_64-linux.
63963 remote-gdbserver-on-localhost, by:
63967 Tested on x86_64-linux.
63973 remote-gdbserver-on-localhost with REMOTE_TARGET_USERNAME=remote-target:
63976 Executing on target: kill -9 6447 (timeout = 300)
63988 user (remote-target on localhost) to kill a pid owned by the the build user
63989 ($USER on localhost).
63996 Tested on x86_64-linux.
64012 for target board remote-gdbserver-on-localhost, it returns the
64020 remote-gdbserver-on-localhost.
64022 Tested on x86_64-linux.
64028 remote-gdbserver-on-localhost.
64054 Tested on x86_64-linux.
64087 The test fails on Power 10 with the RHEL9 distro. It also fails on
64093 stop again on the same line where it is stopped, but rather continues to
64096 Initialize variable A to zero so the break on main will stop before setting
64097 a break point on line a = 9; /* start here */.
64099 Make the match on the breakpoint number generic.
64101 Patch has been tested on Power 10 with RHEL 9, Power 10 with Ubuntu 22.04,
64117 Correct test target/skip lines to fix fails on alpha-dec-vms,
64127 Commit e3f450f3933d resulted in a nm -l segfault on object files
64132 (free_lineno_cache): Don't segfault on NULL lc->relocs.
64146 check for reloc overflow. Don't abort on unexpected reloc type,
64211 Regression tested on x86-64 Fedora 36.
64256 This patch fixes the error. I did a full regression test on x86-64
64269 Tested on aarch64-linux/x86_64-linux.
64306 Fix test-case gdb.threads/execl.exp on target board
64307 remote-gdbserver-on-localhost using gdb_remote_download.
64309 Tested on x86_64-linux.
64328 remote-gdbserver-on-localhost using gdb_load_shlib.
64330 Tested on x86_64-linux.
64349 Tested on x86_64-linux.
64355 remote-gdbserver-on-localhost.exp by using gdb_download_shlib and gdb_locate_shlib.
64357 Tested on x86_64-linux.
64363 remote-gdbserver-on-localhost (using REMOTE_TARGET_USERNAME) we run into some
64368 Tested on x86_64-linux.
64372 [gdb/testsuite] Fix gdb.dwarf2/dw2-zero-range.exp for remote-gdbserver-on-localhost
64374 remote-gdbserver-on-localhost using gdb_load_shlib.
64376 Tested on x86_64-linux.
64417 [gdb/testsuite] Fix gdb.base/signals-state-child.exp for remote-gdbserver-on-localhost
64418 With test-case gdb.base/signals-state-child.exp on target board
64419 remote-gdbserver-on-localhost I run into:
64429 The problem is that we're trying to run an executable on the target board using
64441 Fix this by using an absolute path name for the exec on the target board.
64444 boards, so add an implementation in remote-gdbserver-on-localhost.exp.
64448 - cleanup gdb.txt and standalone.txt on target board
64450 Tested on x86_64-linux.
64454 [gdb/testsuite] Fix gdb.cp/breakpoint-shlib-func.exp with remote-gdbserver-on-localhost
64456 remote-gdbserver-on-localhost.
64460 Tested on x86_64-linux.
64472 [gdb/testsuite] Fix gdb.mi/*.exp with remote-gdbserver-on-localhost
64474 remote-gdbserver-on-localhost, we run into a few fails.
64485 Tested on x86_64-linux, with and without target board
64486 remote-gdbserver-on-localhost.
64580 auto result = true ? A() : B();
64619 tests on non-Linux systems. FreeBSD kernels for example use the
64620 same system call numbers on all platforms, so the test is also not
64621 relevant on FreeBSD.
64627 stack on FreeBSD rather than raising it causing non-main threads in
64636 registers to support TLS on other architectures (tpidr* on ARM and
64637 AArch64, tp on RISC-V) are treated as general purpose registers.
64646 system registers in other OS ABIs. This allows the test to pass on
64680 Tested on x86_64-linux.
64711 Tested on x86_64-linux.
64740 Tested on x86_64-linux.
64750 Tested on x86_64-linux.
64770 This patch removes the method. Regression tested on x86-64 Fedora 36.
64786 The main problem here was not returning -1 from canonicalize_symtab on
64790 * mach-o.c (bfd_mach_o_canonicalize_symtab): Return -1 on error,
64823 set exit_status. Don't error on non-existent dynamic relocs.
64824 Don't call bfd_fatal on bfd_canonicalize_dynamic_reloc error.
64827 (dump_relocs_in_section): Don't call bfd_fatal on errors.
64832 * addr2line.c (slurp_symtab): Don't exit on errors.
64843 on a corrupted archive symbol table.
64847 (display_rel_file): Don't give a fatal error on
64848 bfd_read_minisymbols returning an error, or on not being able
64852 (display_file): Don't bomb on a bfd_close failure.
64861 this is possible. Also don't bomb via bfd_fatal on errors getting
64868 on errors.
64871 call bfd_fatal on errors reading symbols, just omit the line
64882 (main): Use non_fatal and call usage on unrecognized arg errors.
64921 and gdb.threads/detach-step-over.exp). Those were not problematic on my
64929 and on my Ubuntu:
64961 [gdb/testsuite] Use set always-read-ctf on instead of --strip-debug
64962 Use "set always-read-ctf on" instead of --strip-debug in the ctf test-cases.
64964 Tested on x86_64-linux.
64981 Small cleanup to use std::string::size instead of calling strlen on
65056 with -O2, with g++ 11.3.0 on Ubuntu 22.04, I see:
65068 1933 | auto pair = internalvars.emplace (std::make_pair (name, internalvar (name)));
65164 [gdb/symtab] Add set/show always-read-ctf on/off
65185 Add a new command "set/show always-read-ctf on/off", that when on forces
65188 (gdb) set always-read-ctf on
65196 A bit of background on the relevance of reading order: the formats have a
65209 908a926ec4e ("[gdb/testsuite] Fix ctf test-cases on openSUSE Tumbleweed") by
65210 uses of "set always-read-ctf on", but I've left that for another commit.
65212 Tested on x86_64-linux.
65332 Tested on x86_64-linux.
65360 * read.c (do_repeat): Free sb on error path.
65407 Tested on x86_64-linux and powerpc64le-linux.
65418 [gdb/testsuite] Fix gdb.rust/watch.exp on ppc64le
65425 but on powerpc64le-linux, I run into:
65438 Tested on x86_64-linux and powerpc64le-linux.
65673 out_of_scope method on.
65689 Tested on x86-64/Linux with unix, native-gdbserver, and
65706 …FAIL: gdb.mi/mi-pending.exp: MI pending breakpoint on mi-pendshr.c:pendfunc2 if x==4 (unexpected o…
65732 'maint show target-non-stop' command, and then switch based on the
65748 once with the MI on a separate UI.
65758 based on the current UI mode.
65794 Building on the previous commit, now that the breakpoint related
65848 on.
65869 And then this comment is located on one random place where
65886 Seen when building binutils with gcc -m32 on x86_64-linux.
65916 (_bfd_mips_elf_find_nearest_line): Likewise on error paths,
66210 for gdb.base/gdb-sigterm.exp when run on a machine with glibc-2.34.
66286 (the Value.cast one comes earlier on the chain than the
66297 for him, I can't make it fail on this machine; nevertheless, he tried
66343 matter -- it can go on running free, be detached, etc., depending on
66344 "set schedule-multiple", "set detach-on-fork", etc. That does not
66357 As I was working on this, I managed to end up calling target_resume
66377 Make follow_fork not rely on get_last_target_status
66387 parent/child, depending on "set follow-fork" mode.
66394 off", which is the default, or "set scheduler-locking on", gdb will
66402 (gdb) set scheduler-locking on
66422 Another issue is that, because follow_fork relies on
66487 That may have happened on a thread different from the selected
66562 I originally wrote this patch, because while working on some other
66576 tweak "info program" to not rely on get_last_target_status returning a
66619 Tested on GNU/Linux native, gdbserver and gdbserver + "maint set
66620 target-non-stop on".
66642 Currently, "info files" and "info program" on a few native targets
66756 While working on other projects, I found the pyright type checker very
67237 <!-- The group field information was based on strace. -->
67480 objects when writing -- it's entirely based on the objfile-independent
67544 The feature isn't universally available on 64-bit CPUs.
67552 x86: have insns acting on segment selector values allow for consistent operands
67737 gdb_breakpoint. Tested on x86-64 Fedora 36.
67879 Instead of only testing this on systems that have a SYS_time syscall,
67887 The explicit syscall variant is useful on platforms where the C
67888 function does not call a syscall at all by default, e.g., on some
67915 set bfd_error on make_tempname or make_tempdir failure
67916 * bucomm.c (make_tempname, make_tempdir): Set bfd_error on error.
67953 Issue error on erroneous expression
67962 Regression tested on x86-64 Fedora 36.
67987 While at it, remove the condition on 'ac_cv_search_waddstr' and set
68007 Tested on aarch64-linux.
68030 Tested on x86_64-linux and aarch64-linux.
68048 Tested on x86_64-linux and aarch64-linux.
68074 Tested on x86_64-linux and aarch64-linux.
68092 Tested on x86_64-linux, both with a gdb without and with python.
68173 resulting in them being disabled on mingw hosts.
68185 continue on with rest of test past first fail.
68187 ld-libs test on alpha-vms
68302 the first ":". However, on Windows, a path can start with "C:". Adjust
68313 In some tests, the path reported on Windows will have a \ instead of a
68379 This has effect both on the amd64 and i386 targets, but only add amd64
68380 test-case gdb.base/unwind-on-each-insn-amd64-2.exp.
68491 Tested on x86_64-linux, although sofar I was not able to trigger the warning
68499 Since commit 9af467b8240 ("[gdb/testsuite] Fix gdb.threads/schedlock.exp on
68530 Tested on x86_64-linux, using compilers:
68572 mdebugread.c allocates blocks on the heap. However, this is a memory
68599 initialization API decide which to use based on an optional parameter.
68704 The Rust compiler, on the other hand, uses DW_AT_main_subprogram.
68779 The test relied on an invalid target description being stored within
68799 gprofng: PR30036 Build failure on aarch64 w/ glibc: symbol `pwrite64' is already defined
68885 initialization for calling glibc's _exit on the test-case itself.
68929 Tested on x86_64-linux.
69006 …* testsuite/ld-scripts/asciz.t: Adjust to work on more architectures and to test more aspects of t…
69230 However, when the inferior is running on the background, say with
69264 and we should see 10 "Quit" being printed on the screen. As if the
69265 user typed Ctrl-C on the prompt a number of times with no inferior
69363 Returns the command's exit code: zero on success, non-zero otherwise.
69449 out how to. ptype on an xmethod isn't treated specially, it just
69540 …==1527735==ERROR: AddressSanitizer: heap-use-after-free on address 0x6210003392a8 at pc 0x55e4c26e…
69591 to something that used to be allocated on the frame obstack, that has
69595 by iterating on the frame chain, starting with the sentinel frame, like
69607 After that patch, we relied on the fact that all frames are (supposedly)
69619 corresponding to frames in the "bfcache" hash table. It then relies on
69628 The proposed solution is to explicitly call frame_info_del on frame 0,
69691 in the end decided on an ad hoc approach).
69740 pointer-sized integer on the stack. To this end, use intptr_t rather
69787 Makeinfo can figure out the node structure on its own now, so simplify
69915 Return asection pointer. Don't unnecessarily free contents on
69929 … of .string in order to avoid the special behaviour of the .string directive on HPPA architectures.
70061 There's a HW bug affecting Processor Trace on some Intel processors
70070 The bug manifests (on a Performance-core of an i7-1250U, an Alder Lake cpu) in
70082 Note that the i7-1250U has both Performance-cores and Efficient-cores, and on
70086 Tested on x86_64-linux:
70103 Tested on x86_64-linux.
70130 nothing else on the line needs to move ahead, which luckily is easily
70160 Rely on value_ref_ptr::operator->
70166 Now that value.h is using methods, we can instead rely on operator->.
70181 Introduce set_lval method on value
70182 This introduces the set_lval method on value, one step toward removing
70353 on value. It is temporarily public, until some users are converted.
70371 value_contents_all_raw into methods on value. The remaining functions
70424 into methods on value.
70448 to be methods on value.
70614 The previous commit relied on spotting when a Python defined TUI
70701 This is pretty useful in practice, as it allows users to iterate on
70743 Fix PR30079: abort on mingw
70748 Tested on all targets.
70772 It was pointed out on the mailing list, that for microMIPS it would be
70787 gdb: only allow one of thread or task on breakpoints or watchpoints
70804 notice the extra 'ERROR: ' on the second line of output. This commit
70811 in order to tidy memory on exit and to reinit everything for that
70870 detect identify targets if this is not specified on the comand line).
70934 Regression tested on x86-64 Fedora 36.
70961 gdb/c++: fix handling of breakpoints on @plt symbols
70968 When the current language is C++, and the user places a breakpoint on
71018 When the user creates a breakpoint on 'foo' GDB eventually ends up in
71034 matching function by calling the get_symbol_name_matcher method on the
71132 relied on the value of 0, and I see no test regressions, especially in
71141 gdb: only allow one of thread or task on breakpoints or watchpoints
71290 I recreated the above crash by a little light hacking on GDB, and then
71409 unwinders at once using "maint set dwarf unwinders on/off".
71415 that as evidence that on amd64, the "i386 epilogue" is not only unnecessary,
71427 Tested on x86_64-linux, -m64 and -m32. Not tested with -mx32.
71438 objdump -s, both supposedly operating on all sections by default.
71489 open_source_file relies on errno to communicate the reason for a missing
71623 report a conversion overflow on byte ranges that cannot be expressed in
71746 PR testsuite/30103 reports the following failure on aarch64-linux
71767 Make breakpoint pending on future shared library load? (y or [n]) n
71772 The test-case intends to set the breakpoint on line number 63 in
71785 I've managed to reproduce the FAIL on x86_64/-m32, by installing the
71795 Tested on x86_64-linux, target boards unix/{-m64,-m32}.
71847 Tested on x86_64-linux.
71885 lop_stab_symbol. Don't free/release on error.
71888 (mmo_scan): Free fname on another error path.
72035 gdb, testsuite: Remove unnecessary call of "set print pretty on"
72051 affect the size of main_type on x86-64 Fedora 36. And, if it does
72085 seem to be a better way to interrupt a wait on a std::future.
72138 uncompressed_buffer on error return.
72146 the file size is no longer valid. Found when attempting objdump -t on
72148 781152ec18f5). So, clear file size when setting BFD_IN_MEMORY on bfds
72156 file size. That's only valid if on-disk symbols are larger than a
72183 The test gdb.base/frame-view.exp fails like this on AArch64:
72205 argument), the auto-reinflation mechanism re-creates the user frame
72334 With this fix applied, the gdb.base/frame-view.exp now passes for me on
72347 Currently, some frame resources are deallocated by iterating on the
72367 that some dealloc_cache would need to access some data on that obstack,
72496 Many gdb.compile C++ tests fail for me on Fedora 36. I think these
72596 depend on the type of the symbol -- i.e., default data symbols to
72619 Tested on x86_64-linux.
72663 Tested on x86_64-linux, with and without glibc debuginfo installed.
72712 1' condition is printed, but this is then repeated on the next line
72720 There's two things going on here. First the randomly placed 'thread
72807 Tested on x86_64-linux.
72815 gdb: adjust comment on target_desc_info::from_user_p
72849 no_warn_rwx_segments on generating a bss plt, unless explicity
72861 [gdb/testsuite] Fix gdb.threads/schedlock.exp on fast cpu
72864 (gdb) PASS: gdb.threads/schedlock.exp: schedlock=on: cmd=continue: \
72865 set scheduler-locking on
72868 PASS: gdb.threads/schedlock.exp: schedlock=on: cmd=continue: \
72873 (gdb) FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=continue: \
72886 finishes after 0x7fffffff iterations (when a signed wrap occurs), which on my
72902 Tested on x86_64-linux.
72962 first call left entries on mips_hi16_list pointing at buffers
72995 gdb/testsuite: don't try to set non-stop mode on a running target
72997 on a running target, something which the manual makes clear is not
73024 aligned to 4, which would cause firmware load failure on AARCH64 hosts.
73052 The legacy non-mainline PRU host driver relied on the default
73067 This change has been tested on Beaglebone AI-64 [4]. Static counter
73174 Like with segment overrides on LEA, optimize away such a redundant
73221 execution on GPUs or similar accelerators. The programs running on GPUs
73226 language [2], OpenCL and OpenMP, but we're going to focus on HIP here.
73248 /* Run `do_an_addition` on one workgroup containing one work item. */
73286 GPU's memory and spawned an execution thread on it. The goal of this
73295 Make breakpoint pending on future shared library load? (y or [n]) y
73340 think of the threads running on the GPU as part of the same program as
73367 talk to the library, as show on the following diagram:
73383 (AMD Debugger API on the diagram).
73387 on that later.
73396 code objects loaded on the device from the amd-dbgapi library, and
73399 libraries are the pieces of code loaded on the device.
73408 the target stack, on top of the linux-nat target. Doing so allows the
73431 incrementing integer). The idea is that on Linux systems, the
73452 notified through that fd, and pushes itself on the target stack of the
73462 support for the amdgpu architecture (amdgpu-tdep.c) depends on the
73513 In ROCm-GDB, we install an solib provider for the GPU code objects on
73547 Add a gdbarch_up unique pointer type, that calls gdbarch_free on
73558 detach method on the inferior's target stack. This allows observer to
73559 do some work on the inferior while it's still ptrace-attached, in the
73693 The merge test fais on numerous targets because they don't support the
73816 about some out of date debug information on my machine, but then GDB
73826 This diagnostic was printed on Fedora 33 even when the correct
74074 copy" and "pr25662" on sh-*-coff. Remove all non-ELF xfails
74075 on "ELF unknown section type" test.
74083 "undefined line" depending on gcc version for s390.
74097 gdb: fix dwarf2/cooked-index.c compilation on 32-bit systems
74119 gdb: Replace memcpy with std::copy to avoid some g++ warnings on sparc
74120 For some reason g++ 12.2.1 on sparc produces spurious warnings for
74178 Note that this patch depends on Pedro Alves' patch "enum_flags
74242 on irc, Simon pointed out that it could perhaps be solved if the
74262 I regression tested this in libstdc++ debug mode on x86-64 Fedora 36.
74266 the 'enum class' change, as I mentioned in email on the list.
74403 (gdb) set range-stepping on
74407 (gdb) set range-stepping on
74424 (gdb) set range-stepping on
74428 (gdb) set range-stepping on
74441 target array is constructed based on the global remote_protocol_packets
74514 [gdb/testsuite] Simplify gdb.base/unwind-on-each-insn.exp.tcl
74516 gdb.base/unwind-on-each-insn-{amd64,i386}.exp") broke commit eb015bf86b6
74517 ("[gdb/testsuite] Avoid using .eh_frame in gdb.base/unwind-on-each-insn.exp"),
74518 in the sense that gdb.base/unwind-on-each-insn.exp no longer uses
74528 Fix this by simplifying gdb.base/unwind-on-each-insn.exp.tcl, completely
74532 Tested on x86_64-linux.
74548 working on the previous set of patches.
74550 Unless tui debug is turned on, then there should be no user visible
74555 gdb/tui: avoid extra refresh_window on vertical scroll
74556 While working on the previous couple of patches I noticed that when I
74582 gdb/tui: avoid extra refresh_window on horizontal scroll
74583 While working on the previous patches I noticed that in some cases I
74602 rely on the refresh_window call within it to be our single refresh
74625 is first created, so we already depend on nullptr handling), so all
74788 want to rely on malloc).
74890 one line at a time until the cursor is back on the screen (a single
74927 opcodes: suppress internationalization on build helper tools
74955 * ldmain.c (ld_cleanup): Call bfd_close_all_done on linker bfds.
74962 particularly since bfd_close_all_done is typically called on an output
74964 necessary if bfd_close_all_done is to work on odd bfd's opened by
75006 from macro_hash on attempt to redefined pseudo-op.
75306 [gdb/testsuite] Add gdb.base/unwind-on-each-insn-{amd64,i386}.exp
75331 Tested on x86_64-linux, target boards unix/{-m64,-m32}.
75338 Tested on x86_64-linux.
75436 A few tests work on two different targets that can't be detected with
75474 [gdb/testsuite] Fix gdb.base/unwind-on-each-insn.exp for -m32
75475 With test-case gdb.base/unwind-on-each-insn.exp and target board unix/-m32, I
75485 srcfile2 in gdb.base/unwind-on-each-insn.exp"), due to the test-case trying to match
75490 Tested on x86_64-linux, target boards unix/{-m64,-m32}.
75494 [gdb/testsuite] Allow debug srcfile2 in gdb.base/unwind-on-each-insn.exp
75495 Test-case gdb.base/unwind-on-each-insn.exp compiles $srcfile with debug info, and
75509 Tested on x86_64-linux.
75513 [gdb/testsuite] Allow nodebug srcfile in gdb.base/unwind-on-each-insn.exp
75514 Test-case gdb.base/unwind-on-each-insn.exp compiles $srcfile with debug info, and
75530 FAIL: gdb.base/unwind-on-each-insn.exp: foo: instruction 1: bt 2
75531 FAIL: gdb.base/unwind-on-each-insn.exp: foo: instruction 1: up
75538 Tested on x86_64-linux.
75548 [gdb/testsuite] Analyze non-leaf fn in gdb.base/unwind-on-each-insn.exp
75549 In test-case gdb.base/unwind-on-each-insn.exp, we stepi through function foo
75556 With the updated test-case, on powerpc64le-linux, I run into PR tdep/30049:
75566 Tested on:
75574 [gdb/testsuite] Improve leaf fn in gdb.base/unwind-on-each-insn.exp
75575 In test-case gdb.base/unwind-on-each-insn.exp, we stepi through function foo
75644 Having made foo more complex, we now run into the following fail on
75647 FAIL: gdb.base/unwind-on-each-insn.exp: instruction 1: $sp_value == $main_sp
75661 FAIL: gdb.base/unwind-on-each-insn.exp: insn 7: $fba_value == $main_fba
75662 FAIL: gdb.base/unwind-on-each-insn.exp: insn 7: [string equal $fid $main_fid]
75666 Tested on:
75673 record/16678 on x86_64.
75689 While working on the previous couple of commits, I noticed that the
75701 While working on the previous commit, I realised that there was an
75735 Following on from the previous commit, in this commit I am updating
75760 Following on from the previous commit, in this commit I am updating
75780 box does appear on the screen, which should indicate that tui mode has
75883 the Overfull warnings) are causing undesirable effects on the rendered
75946 Tested by rebuilding on x86_64-linux with clang 16 and gcc 12.
76082 Tested on aarch64-linux.
76090 [gdb/testsuite] Avoid using .eh_frame in gdb.base/unwind-on-each-insn.exp
76091 One purpose of the gdb.base/unwind-on-each-insn.exp test-case is to test the
76092 architecture-specific unwinders on foo, so unwind-on-each-insn-foo.c is
76104 gdb.base/unwind-on-each-insn.exp stops being a regression test for commit
76111 Tested on x86_64-linux, target boards unix/{-m64,-m32}, using compilers
76120 [gdb/testsuite] Simplify gdb.base/unwind-on-each-insn.exp
76121 In test-case gdb.base/unwind-on-each-insn.exp, we try to determine the last
76125 fix for gdb.base/unwind-on-each-insn.exp").
76140 Tested on x86_64-linux.
76156 Tested on x86_64-linux.
76195 gdb: make frame_info_ptr auto-reinflatable
76196 This is the second step of making frame_info_ptr automatic, reinflate on
76206 the logical state of the object, because we re-create it on demand. I
76214 gdb: make frame_info_ptr grab frame level and id on construction
76257 However, on another machine (my Ubuntu 22.04 one), it just passes fine,
76515 Doing so reveals that a bunch of files were relying on frame.h to
76571 gdb.ada/ptype_tagged_param.exp is failing for me on x86-64 Fedora 36.
76582 When running gdb.ada/arrayptr.exp (and others) on Ubuntu 22.04, with the
76649 compiler-dependent, so would rely on having a buggy compiler.
76674 but that depends on many factors to actually go wrong so this is a more
76703 writing on the machine I used was going from 14400 perf samples to 9300
76726 Register names are (including their nul terminators) on average almost 4
76741 Register names are (including their nul terminators) on average almost 4
76761 identifier for the following entry in a number of cases. Re-use that on
76781 on cache occupation of table entries accessed. For PIE builds of gas
76808 i386: Don't emit unsupported TLS relocs on Solaris
76810 R_386_TLS_IE_32, on Solaris.
76814 R_386_TLS_IE on Solaris.
76816 transition on Solaris.
76890 Limit on string chars or array elements to print is 200.
76893 Limit on array elements to print is 200.
76899 Set limit on array elements to print.
77040 Tested on aarch64-linux.
77065 it does on x86_64), but instead it contains 0.
77070 Tested on x86_64-linux and s390x-linux.
77090 toplevel: Makefile.def: add install-strip dependency on libsframe
77161 size set to zero, but I would rather not edit lots of files when it
77239 cleanliness, mostly auto-generated").
77248 one I noticed while working on that -- namely that the "sed" computes
77340 address of the alternate function start address, known as the GEP on
77342 is between the two entry points (the LEP and GEP on PowerPC), the stepping
77343 range is set to execute back to the alternate entry point (GEP on PowerPC).
77344 Otherwise, a breakpoint is inserted at the normal entry point (LEP on
77349 Note, on systems that only support one entry point, the address of the two
77356 The patch has been tested on X86 and PowerPC with no regressions.
77364 Currently on X86, when executing the finish command in reverse, gdb does a
77366 caller. GDB stops on the last instruction in the source code line where
77379 behavior on X86 for the reverse-finish command now matches doing a
77401 The patch has been tested on X86 and PowerPC to verify no additional
77416 `-i $inferior_spawn_id`. On native, the top and bottom GDB are on the
77509 GCC generates a VCVTNE instruction based on the `truncsisf2_vfp`
77521 the instructions are parsed that is conditional on whether we are
77548 While trying to build gdb on latest openSUSE Tumbleweed, I noticed the
77688 on igen, we can move the conditional logic out of configure. We also
77699 port depends on their respective file now, and the ppc port doesn't
77721 things out of SIM_ALL_RECURSIVE_DEPS and rely on finer dependencies,
77726 need to mark the igen tool as a recursive dep. Each port depends on
77732 port depends on their respective header now, and the ppc port doesn't
78060 Declares that a test case depends on some facility that does not exist
78072 on failure. Another is to convert the predicates that need a running
78091 * configure.ac: Remove dependencies on libbfd and libiberty.
78172 IIUC "Aarch32" emulation on an "Aarch64" (arm64) kernel, but
78178 "EXPERT" level set on.
78203 Pass -z max-page-size=0x10000 explicitly to test that rely on
78213 faulty (but happens, by chance, to give the right output on most
78226 flag on and members with it off, and the linker always reserializes (and
78286 on ctfa_ndicts, not another nonexistent field.
78323 Reflects the reality that I haven't done much on hppa32 for years.
78406 Tested on x86_64-linux.
78410 Fix XPASS weak symbols on x86_64-mingw32
78484 Tested on x86_64-linux, with and without LD_PRELOAD="".
78596 If a lazy value is fetched, GDB allocates space based on the enclosing
78601 However, GDB can read the value based on its type. Thus, this patch
78609 * dwarf2/loc.c (rw_pieced_value): Fix check on 'type' and
78619 Convert say_where to method on code_breakpoint
78621 convert it to be a protected method on code_breakpoint.
78937 targets, it generates the list of sources & objects on the fly in the
79244 on setting up stash.
79257 (pe_print_edata): ..and here. Free data on error return.
79298 * po/SRC-POTFILES.in: Regenerate.
79317 Skip ld/pr23169 test on arm.
79318 The test is already skipped on several targets (including AArch64)
79321 * testsuite/ld-ifunc/ifunc.exp: Skip pr23169 on arm.
79457 SFrame FRE type based on the function size. Those constants, however,
79504 leaving them in place on the escaped double quotes inside the parameter
79607 configure: remove dependencies on gmp and mpfr when gdb is disabled
79650 auto res = scoped_debug_start_end<PT &> (pred, module, func, start_prefix,
79739 Make breakpoint pending on future shared library load? (y or [n]) n^M
79786 Tested on x86_64-linux, by successfully running the test-case:
79830 wrapping should be allowed on the 16-bit relocs, and may as well be
79840 depend on generate igen files, all with unknown names ahead of time.
79842 files as built sources so they'll be created early on.
79862 Tested on bpf-*-*:
79916 When running the testsuite in a non-optimized build on a slow machine, I
79973 addr2line out of memory on fuzzed file
80059 This is something I discovered when working on aarch64, though it's
80072 of DLLs, the function pointers won't be aligned on an 8-byte boundary.
80074 Misaligned reads are slower on x86_64, but this is more important on
80152 be on the stack and thus overwritten by the call to "f".
80220 Tested on x86_64-linux.
80289 Tested on x86_64-linux.
80303 Rather than rely on SIM_SUBDIRS being set, add a dedicated variable
80389 The DAP code will accept JSON-RPC messages on stdin and print
80477 Tested on x86_64-linux.
80586 on binutils/bfdtest2.c and ld/testsuite/ld-cygwin/exe-export.exp, and
80735 The decision on whether to call the out_of_scope call back is taken in
80755 using frame_find_by_id () == NULL on that frame instead, such that we have:
80769 we get on x86_64-linux with target board unix/-m64:
80790 Tested on x86_64-linux, with target boards unix/-m32.
80798 [gdb/testsuite] Fix gdb.base/print-symbol-loading.exp on ubuntu 22.04.1
80824 Tested on x86_64-linux.
80844 Tested on x86_64-linux.
80877 Tested on x86_64-linux.
80920 Tested on x86_64-linux.
80938 Tested on x86_64-linux.
80996 line the step lands on, and issuing an extra next if needed.
80998 Tested on x86_64-linux, both with and without -fcf-protection=none.
81011 Tested on x86_64-linux.
81042 RISC-V: Simplify riscv_csr_address logic on state enable extensions
81109 of the Boehm GC that is used by Guile on my machine causes a SEGV
81177 rely on sim_mips_micromips{,16}_{filter,machine} variables that
81230 The following test was failing on ppc64 and s390x:
81234 (on-disk format). When the host is big-endian, the address of the
81350 observed on some systems where the debug information for the
81689 a correctness fix since long will be 64-bits on most 64-bit hosts.
81848 directives on aarch64.
81870 Gather the information from the DWARF FDE on whether frame's return
81933 x86: add dependencies on SVME
81942 x86: add dependencies on VMX
81969 x86: add dependencies on AVX2
81971 on up to 256-bit packed integer vectors.
81975 and KL take SSE2 as a prereq, for operating on packed integers. And
82026 sim: mips: match target on cpu settings
82127 on all-gmp and all-mpfr.
82145 * target-float.c: Make the code conditional on
82158 gdb/c++: validate 'using' directives based on the current line
82384 build-time (via dgen.c that we have to compile & execute on the
82445 Regen opcodes/po/POTFILES.in
82461 that actually tries to detach itself on the fly, so no one noticed
82608 Arm: break gas dependency on libopcodes
82634 in the build path directory. $ld depends on $base_dir which is set
82678 rawsize (the on-disk size for input sections) and size.
82753 otherwise. Print warnings on successful match, or when only one
82775 Add a new test to check that .cfi_negate_ra_state on aarch64 is handled
82866 a warning that depends on whenever GDB writes to inferior memory.
82870 version on the system, and that Gentoo's build process has sandboxing
82884 Fix previous delta to allow for compilation on 32-bit systems
82911 Tested on x86_64-linux.
82930 Only placing a breakpoint on the label worked.
83001 "string" rather than "buffer" since it operates on an std::string rather
83177 There are two places where unaligned loads were seen on aarch64:
83180 - #2. access to the SFrame FRE start address in the on-disk representation
83189 SFrame format is an unaligned on-disk format. As such, there are other blobs
83190 of memory in the on-disk SFrame FRE that are on not on their natural
83192 are provided access to the on-disk SFrame FRE data via libsframe's
83193 sframe_frame_row_entry, the latter has its' struct members aligned on their
83298 Tested on x86_64-linux, with gcc 4.8.5, 7.5.0 and clang 13.0.1.
83318 can do some work depending on the type of target, so it is important
83333 them methods on the inferior class.
83339 Right now, closing a target, in some cases, depends on the current
83465 references to the target_ops objects on the inferior's target_stack.
83485 auto ref = std::move (m_stack[stratum]);
83520 While working on some other target_ops reference count related code, I
83598 The *_SCOPED_DEBUG_ENTER_EXIT mechanism currently relies on capturing
83600 both on entry, and at exit, this is done in the scoped_debug_start_end
83724 The following tests all currently depend on this detection:
83739 gdb.opt/break-on-_exit.exp
83761 Finally, I updated gdb.opt/break-on-_exit.exp to call the `readnow`
83896 Fix control-c handling on Windows
84004 Tested on s390x-linux.
84057 [gdb/testsuite] Fix gdb.python/py-disasm.exp on s390x
84076 The problem is that the test-case expects "nop" but on s390x we have instead
84081 Tested on s390x-linux and x86_64-linux.
84149 hi/lo relocs to leave a stale section pointer on the list. That can
84223 In contrast, on x86_64-linux, we have:
84239 That's easy to fix, but after that we have on s390 (big endian):
84244 and on x86_64 (little endian):
84256 Tested on x86_64-linux and s390x-linux.
84286 In contrast, on x86_64-linux (little endian), we have the expected:
84308 Tested on x86_64-linux and s390x-linux.
84348 The need for them on the operand-less string insns has gone away with
84394 only supported in 64-bit mode" on the SIMD forms of MOVQ) we need to
84517 make output (depending in particular on the verbosity level).
84519 x86: break gas dependency on libopcodes
84526 depending on the generated data.
84573 $ gdb -q -batch -ex "set trace-commands on" -x gdb.in
84630 Tested on s390-linux, with native and target board unix/-m31.
84644 SFrame decoder context on exit.
84753 existing gdb/features/aarch64-tls.c auto-generated file with a new file that
84863 Tested on x86_64-linux and powerpc64le-linux.
84901 When running test-case gdb.tui/tui-layout-asm-short-prog.exp on SLE-12-SP3
84914 I managed to reproduce the same behaviour on openSUSE Leap 15.4 x86_64, by
84919 Tested on x86_64-linux.
84978 Tested on x86_64-linux.
84992 While playing with JIT reader I experienced GDB to crash on null-pointer
85063 Tested on x86_64-linux.
85201 Tested on x86_64-linux.
85206 When running test-case gdb.base/longjmp.exp on x86_64-linux, the master
85230 For contrast, if we do the same on powerpc64le, the failure mode is:
85242 So, how does this happen on x86_64? Let's look at the code:
85261 Try to avoid this accident and make the failure mode on x86_64 the same as on
85264 Tested on x86_64-linux.
85401 gdb/linux-nat: don't memset siginfo on failure in linux_nat_get_siginfo
85402 No caller cares about the value of *SIGINFO on failure. It's also
85404 understand "untouched") on failure.
85460 since runto records a FAIL on error, by default. Remove all the
85461 perrors on runto failure I could find.
85576 While working on disassembler styling for MIPS, I noticed that
85746 timeouts on slower test setups.
85748 Note that this doesn't fix a timeout in the test-case on aarch64 due to:
85754 Tested on x86_64-linux.
85764 breakpoint on the first instruction of the function. PowerPC uses
85769 see the breakpoint on the GEP. However, if the function is called via a
85776 pointer method to call the functions so the tests will work correctly on
85777 both PowerPC with a GEP and LEP as well as on other systems. The GEP is
85778 the same as the LEP on non PowerPC systems.
85781 initial break point for the rest of the test on the function pointer call
85788 Patch tested on PowerPC and Intel X86-64 with no regressions.
85833 C. The idea here is that, by making C and C++ agree on the canonical
85845 The stabs reader is modified on a "best effort" basis.
85913 thread_db_target::update_thread_list implementation based on
85930 * po/POTFILES.in: Likewise.
85937 interfering with my hacking on gdb by making test runs extremely long,
85959 skip_compile_feature_tests checks for "Command not supported on this
86041 When I run the gdb testsuite on a powerpc64le-linux system with (slow) nfs
86050 Tested on powerpc64le-linux.
86089 Tested on powerpc64le-linux.
86117 Tested on s390x-linux.
86128 First, reproduce this on x86_64-linux with --enable-targets=all, by replacing
86136 Tested on x86_64-linux.
86172 section behind our back and some of them (e.g. on powerpc the
86174 being created late (a symptom would be "TOC opt*" failing on powerpc).
86212 checking is done on accesses to the Ada task state names arrays. This
86241 Currently, on x86_64, a little endian target, I get:
86268 Tested on x86_64-linux.
86297 To be on the safe side assume 2: Update the comment and fold the
86307 other means, as D is set only on a very limited number of FPU templates.
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
86803 Because libopcodes is C code, and on some (many?) targets, C code is
86818 Before C++17, the noexcept keyword on a function typedef would be
86842 Will compile just fine for C++11 and C++14 with GCC. Clang on the
86843 other hand complains that 'noexcept' should not appear on function
86874 While working on another patch, Simon pointed out that GDB could be
86880 The reason this is important is the on some hosts, libopcodes, being C
86992 However, this relies on the exception passing through frames #1 to #7,
86996 This commit proposes an alternative solution that does not rely on
87013 After the first call that results in an exception being stored on the
87023 though - to trigger this issue would rely on a libopcodes disassembler
87030 pass on AArch64.
87051 Regression tested on x86-64 Fedora 34.
87070 This means that on glibc 2.35 (or later) systems, GDB is going to
87093 stop-on-solib-events on'. If a probe is removed from glibc, but the
87162 Tested on powerpc64-linux.
87189 Tested on powerpc64le-linux.
87230 tests that use "start" were relying on the fact that start would fail
87258 Regression tested on x86-64 Fedora 34. We've also been using this
87267 - Uncomment line in test to avoid hanging when exiting, when testing on
87301 scoped_disable_commit_resumed iterates on non-exited inferiors in order
87328 clears the target's commit_resumed_state on entry, and leaves it false
87329 if the target does not have any resumed thread on exit. That means,
87335 is true on the process target).
87350 -ex "maint set target-non-stop on" \
87365 Added inferior 2 on connection 1 (extended-remote :1234)
87372 Note the "attach" command just above. When doing it on the command-line
87376 the error recovery of GDB is not on point. This patch aims to fix just
87407 iterate on all threads of all process to fulfull the qxfer:threads:read
87487 Tested on powerpc64le-linux.
87613 Tested on power64le-linux.
87618 With test-case gdb.base/msym-bp-shl.exp on powerpc64le-linux, I run into:
87649 Tested on powerpc64le.
87713 1. It heavily depended on the bignum internals (radix of 2^16),
87724 This commit will be tested on the separate commit.
87746 Note that, it only happens on ".byte" output (instruction part) and not on
87762 instructions longer than 64-bits (to print correct instruction bits on
87763 ".byte"). This commit will be tested on the separate commit.
87907 Listening on port 2345
87925 Tested on x86_64-linux.
87934 [gdb/testsuite] Don't generate core in gdb.base/bt-on-fatal-signal.exp
87935 When running test-case gdb.base/bt-on-fatal-signal.exp on powerpc64le-linux I
87938 FAIL: gdb.base/bt-on-fatal-signal.exp: SEGV: scan for backtrace (timeout)
87951 Tested on x86_64-linux.
87984 Fix jump on uninit producer_is_clang bit of cu.h dwarf2_cu struct.
87985 Valgrind reports a "jump on unitialised bit error" when running
87990 Tested on amd64/debian11 and re-running gdb.base/macro-source-path.exp
87993 ==2140965== Conditional jump or move depends on uninitialised value(s)
88101 - Rebase on upstream/master
88136 and tries stopping on them.
88179 This one is a bit tricky. The clear tests seem to depend on the various
88299 gas: Disable --gcodeview on PE targets with no O_secrel
88307 gdb/arm: Include FType bit in EXC_RETURN pattern on v8m
88320 PR22509 - Null pointer dereference on coff_slurp_reloc_table
88350 tdata->symcount on error.
88360 Fix gdb.cp/gdb2495.exp on powerpc64le
88370 To change this behavior use "set unwindonsignal on".^M
88380 - an internal breakpoint is set on the global entry point of std::terminate
88404 Tested on x86_64-linux, powerpc64le-linux.
88518 files on LLP64 hosts (Windows) where long is only 32 bits. The patch
88600 depending on which of those is available. If neither is available,
88636 Note: GDB crashes on this problem with an internal error,
88681 Regtested on debian/amd64 and re-run a few tests under valgrind.
88739 [PR build/29791] gnulib: Disable _GL_ATTRIBUTE_DEALLOC on Solaris
88740 gdbsupport compilation badly fails with GCC 12 on Solaris, with errors
88750 on Solaris, at least as a workaround for GDB 13.
88755 Tested on sparcv9-sun-solaris2.11, amd64-pc-solaris2.11, and
88762 Fix sol-thread.c compilation on 32-bit Solaris
88763 sol-thread.c fails to compile on 32-bit Solaris: there are several
88787 Tested on i386-pc-solaris2.11, amd64-pc-solaris2.11,
88885 This is based on the latest version of RISC-V Profiles
88950 with a current process but no current thread. This tripped on ps_getpid
88963 ps_get_thread_area receives as a parameter the lwpid it must work on.
88965 thread to work on. However, it is not said that both are the same.
88972 Fix that by making is_64bit_tdesc accept the thread to work on as a
88974 we know the lwpid to work on). Otherwise, pass "current_thread", to
88995 Currently, FinishBreakpoints are set at the return address of a frame based on
89009 gdb: fix symtab.c build on 32 bit targets
89010 When building on Ubuntu 22.04, gcc 12, x86-64 with -m32 and -O2, I get:
89032 PR build/29798 shows a similar error message but on Solaris.
89046 The existing gdb.cp/call-method-register.exp test relies on a GCC
89055 clang, and should work on most, if not all, architectures.
89058 register, and then tries to call a method on the structure from within
89065 DW_OP_reg0, whatever that might be. I've tested the new test on
89066 x86-64, ppc, aarch64, and risc-v, and the test runs, and passes on all
89069 Additionally, on x86-64, I've tested with Clang and gcc, and the test
89094 However, with Clang 9.0.2, I see GDB stop on the 'asm' line.
89096 In this commit I'll fix this issue by placing a breakpoint on the
89137 This test relies on the compiled binaries having a build-id within
89143 I did consider *always* turning on the build-id feature when the
89166 described in the comment on the function_range proc in lib/dwarf.exp,
89218 doesn't mean the test wont start failing on some other architecture.
89273 portable (see the comments in lib/dwarf.exp on function_range for
89322 problem is that the windows_nat_target constructor relies on
89384 Patch tested on Power 10 with no regressions.
89402 The patch has been tested on PowerPC and Intel X86_64 with no new unexpected
89454 While working on another patch I noticed that, when run on an AArch64
89478 seemed to work fine for my testing on x86-64.
89480 However, on AArch64 what I see is that the results from 'maint packet
89493 After this the gdb.python/py-send-packet.exp test passes on AArch64
89607 able to build and test gdb on both amd64-pc-solaris2.11 and
89646 Tested on powerpc64le-linux.
89727 Tested on x86_64-linux.
89740 Is generating a segmentation fault on x86_64-linux.
89749 Reproduced on command line:
89785 gdb: add "set style tui-current-position on|off", default to off
89821 Tested on x86_64-linux.
89847 Tested on x86_64-linux, without and with bzip2 installed.
89902 * binutils/Makefile.am: Add dependency on libsframe for
89922 The linker uses libsframe library to perform key actions on the
89934 The linker sorts the SFrame FDEs on start address by default and sets
89938 information for the .plt* sections on x86_64. SFrame unwind info is
89949 * Makefile.def: Add install dependency on libsframe for libbfd.
90208 The optimization is on by default for both x86_64 and aarch64.
90432 Currently for the target board remote-gdbserver-on-localhost we use the
90433 gdbserver file on build, using a file name which includes "/../".
90444 Tested on x86_64-linux.
90450 remote-gdbserver-on-localhost (using REMOTE_TARGET_USERNAME) we run into some
90457 Tested on x86_64-linux.
90465 remote-gdbserver-on-localhost (using REMOTE_TARGET_USERNAME) we run into some
90470 Tested on x86_64-linux.
90478 remote-gdbserver-on-localhost (using REMOTE_TARGET_USERNAME) we run into some
90483 Tested on x86_64-linux.
90491 remote-gdbserver-on-localhost (using REMOTE_TARGET_USERNAME) we run into some
90496 Tested on x86_64-linux.
90504 remote-gdbserver-on-localhost (using REMOTE_TARGET_USERNAME) we run into:
90527 Tested on x86_64-linux.
90535 remote-gdbserver-on-localhost (using REMOTE_TARGET_USERNAME) we run into some
90551 Tested on x86_64-linux.
90557 [gdb/testsuite] Add REMOTE_TARGET_USERNAME in remote-gdbserver-on-localhost.exp
90564 gdb/testsuite/boards, say remote-gdbserver-on-localhost.exp?
90568 pathnames to refer to files on build, we can access those files on target,
90579 Make these problems visible with remote-gdbserver-on-localhost.exp by
90580 adding an option to specify a test account (still on the same machine)
90584 the build files on the $USER account, and that the $USER account cannot see
90585 the target files on the test account.
90591 $ tb="--target_board remote-gdbserver-on-localhost"
90599 Tested on x86_64-linux.
90607 remote-gdbserver-on-localhost (using REMOTE_TARGET_USERNAME) we run into some
90612 Tested on x86_64-linux.
90618 remote-gdbserver-on-localhost.exp, I run into:
90635 Tested on x86_64-linux.
90673 Tested on aarch64-linux.
90684 follow fork mode in child or parent and set detach on fork on
90695 reliably determined on PowerPC. This is due to the fact that the PowerPC
90700 return addreses on exit from the function.
90703 of r3 on entry to a function. On PowerPC, the new gdbarch method attempts
90705 function, to determine the value of r3 on entry to the function. This
90711 data type, on exit from the function. The GDB function should_stop checks
90714 The get_return_value function will be used to obtain the return value on
90723 Note this patch is dependent on patch: "PowerPC, function
90726 This patch has been tested on Power 10 and x86-64 with no regressions.
90732 The following commit resulted in the five testcases failures on PowerPC.
90739 gdb: on x86-64 non-trivial C++ objects are returned in memory
90743 this behaviour was observed on an x86-64 target.
90762 r3 on entry to the function. However, the PowerPC ABI does not guarentee
90772 it into a method on struct expression.
90820 possible to execute instructions from the stack memory on PRU.
90887 This commit tries to address this issue on the GDB side. We have
90892 generated warnings on all standard C++ header files.
90929 and can also be run on x86_64-linux, if "set arch powerpc:common64" is
90939 Tested on x86_64-linux.
90947 The target architecture is set to "auto" (currently "i386").^M
90961 (gdb) set arch set to "auto" (currently "i386")^M
90967 Tested on x86_64-linux.
90990 Tested on x86_64-linux, by running test-cases that excercise
91009 on reloc count.
91039 includes winsock2.h. We don't want to do that on Cygwin, since
91130 "modula-2". But if I manually do "set language modula-2" on a dummy
91135 So, a short term fix would be to use = or == in the expression, based on
91149 using 0x%lx. It's cleaner, more correct, and doesn't break on LLP64.
91153 [gdb/testsuite] Don't timeout on prompt in gdb_start_cmd
91167 Tested on x86_64-linux.
91172 With gdb 12.1, on powerpc64le I ran into ERRORs related to has_hw_wp_support
91173 usage, which was already fixed on trunk by commits:
91174 - 13f72372413 ("gdb/testsuite: fix gdb.base/break-idempotent.exp on ppc"), and
91175 - 01a32ee0b8c ("PowerPC, fix gdb.base/watchpoint.exp on Power 9")
91192 Tested on x86_64-linux, using has_hw_wp_support for x86_64 in
91205 on usual GDB workloads.
91217 allows to have the search operation complexity be O(1) on average
91225 Regression tested on Ubuntu-22.04 x86_64.
91234 Investigating PR29272, it was mentioned a particular test used to work on
91236 some displaced stepping improvements on commit
91285 placed on a register. However, this keyword has been deprecated since
91294 gdb/testsuite: remove XFAIL on gdb.cp/temargs.exp
91322 Since this isn't a bug on Clang or GDB according to the DWARF
91333 gdb/testsuite: allow for Clang style destructors on gdb.cp/m-static.exp
91347 This is because the test is expecting an extra integer parameter on the
91368 gdb/testsuite: account for clang's nested destructor calls on gdb.cp/mb-ctor.exp
91374 parameter or the one with 2 parameters is called, depending on whether
91379 Clang, on the other hand, makes the single-parameter version call the 2
91436 …Executing on host: clang++ -fdiagnostics-color=never -Wno-unknown-warning-option -c -g -o /hom…
91476 The need for IsString on the PadLock insns went away with the
91598 I saw this failure on a CI:
91649 inferiors can share program spaces (usually on particular embedded
91721 When rebasing on top of the frame_info_ptr work, GDB started tripping on
91723 the frame when stopping on a breakpoint. One thing to know about frame
91748 change across a frame cache reset, we must not rely on the frame id from
91784 value, print_frame_info does have a cached frame id on entry. So
91786 a function to rely on its callers to have called prepare_reinflate, if
91929 don't rely on the moved-from object after.
91937 When resolving overloaded functions, GDB relies on knowing relationships
91978 * mach-o.c (bfd_mach_o_canonicalize_reloc): Set bfd_error on
91986 section reloc count was fuzzed. This usually doesn't hurt much (on
92004 debug symbol) fails on some systems as reported by PR/29768. This can
92025 Tested on Ubuntu-22.04 x86_64, with and without libc6-dbg.
92139 …/home/smarchi/src/binutils-gdb/gdb/infrun.c:6960:64: runtime error: member call on null pointer of…
92165 Tested on ubuntu-22.04 x86_64.
92202 This patch replaces this list with a method on 'language_defn'
92219 some compilers would complain about depending on how the macro is used.
92286 I get this test failure on my CI;
92291 who are allocated 4 CPUs on a machine that has 40. The code in
92360 Listening on port 2345
92437 disconnect_tracing too, and don't lose history if the target errors on
92454 Tested on x86_64-linux.
92477 Tested on x86_64-linux.
92514 Tested on x86_64-linux.
92624 based on the $target. We can easily merge this with the top-level
92703 "Flags are inherited by new tracees created and "auto-attached" via
92835 Automake will run each subdir individually before moving on to the next
92867 on some mips targets."), so punt it.
92959 Patch has been tested on Power 10 with no regressions.
92993 The above commit results in about 224 failures on Power 10 since the
93006 Powerpc fix for gdb.base/unwind-on-each-insn.exp
93010 "End of assembler dump". This assumption fails on PowerPC.
93032 The patch has been tested on PowerPC and Intel X86-64.
93082 an uninitialized variable usage, based on the current usage of the
93155 This patch is based on MULTIPLE_FRAME_SECTIONS and EH_FRAME_LINKONCE,
93216 test uses basename on it. Each method works in only one of the
93320 …AVR Linker: Allow the start of the data region to be specified on the linker command line. [Fix P…
93323 has not been provided on the command line then use DATA_ORIGIN.
93326 AVR Linker: Allow the start of the data region to specified on the command line.
93329 has not been provided on the command line then use DATA_ORIGIN.
93381 Rather than rely on pulling out the first cpu from the sim state
93411 the Tbyte modifier on the FLDT and FSTPT templates was pointless, as
93546 on operand 0 while have memory operand.
93639 are encoded with EVEX prefix. {vex} pseudo prefix will turn on VEX
93716 is no default case. The variable switched on is passed in as an
93853 There are no regressions on the ARM gas/binutils/ld tests that I can
93933 watchpoint resource checking in update_watchpoint needs to be redone on
93943 test is run on Power 10, an internal gdb error occurs when the PowerPC
93949 The following descibes the situation in detail that occurs on Power 10 with
93950 gdb running on the binary for gdb.base/watchpoint.c.
94016 because there are only two hardware watchpoint registers available on
94020 update_watchpoint to force the resources to be rechecked on every call to
94024 The patch has been tested on Power 8, Power 10 and X86-64. Note the patch
94025 has no effect on Power 9 since hardware watchpoint support is disabled on
94031 Test gdb.reverse/pipe-reverse.exp fails on Power 10 running the fedora 36
94036 System call 317 on PowerPC maps to the pipe2 system call.
94042 The patch has been tested on Power 10 with no regression failures.
94073 x86: Silence GCC 12 warning on tc-i386.c
94074 Silence GCC 12 warning on tc-i386.c:
94093 to avoid a use of "gdbarch" during initialization, but on the whole I
94099 PR c++/29243 points out that "info func" on a certain C++ executable
94293 When running test-case gdb.server/multi-ui-errors.exp on target board
94294 remote-gdbserver-on-localhost.exp, I run into:
94313 Tested on x86_64-linux.
94322 Executing on target: kill -9 29666 (timeout = 300)
94333 Executing on target: kill -9 31245 (timeout = 300)
94349 Tested on x86_64-linux.
94374 Tested on x86_64-linux.
94398 Tested on x86_64-linux.
94403 Because of a Libiberty hack, getopt on GNU libc (2.25 or earlier) is
94404 currently unusable on sim, causing a regression on CentOS 7.
94477 This changes compunit_language to be a method on compunit_symtab.
94504 description comment based on current spec. Limit instruction
94520 caused a build failure on GCC 12 as follows:
94556 include: Define macro to ignore -Wdeprecated-declarations on GCC
94562 defined on Clang. Since "-Wdeprecated-declarations" is also available on
94571 Define also on GCC.
94691 operand overlap only on Power10.
94720 fields later on.
94733 Stabilize the test name by using "set breakpoint on address" instead.
94737 Tested on x86_64-linux.
94745 Tested on x86_64-linux.
94816 Tested on x86_64-linux.
94857 without waiting on the resulting spawn id, so we're not sure when the
94868 Tested on x86_64-linux.
94891 temporary file on disk that is read back and written to the output
94952 while the test expects an additional "ERROR:" on the second line,
94959 Guile 2.0 outputs the `ERROR:` on the second line, while later versions
94985 Later on line 3553, the condition evaluates if an additional state
94994 RPLHM "In a PE with the Security Extension, on taking an exception,
95010 intrusive, rely on the user to configure the requested
95116 [PATCH v4] gdb/arm: Stop unwinding on error, but do not assert
95117 The warning is printed just once and not repeated on each backtrace command.
95161 bfd_canonicalize_reloc returns -1L on errors.
95220 On x86-64 the default ELF_MAXPAGESIZE depends on a configure
95233 binaries aligned to 2MB pages on disk, and hence generate 2MB
95238 variables be depending on configure options if those only influence
95248 * elf64-x86-64.c (ELF_MAXPAGESIZE): Don't depend on
95253 gdb/testsuite: make sure to consume the prompt in gdb.base/unwind-on-each-insn.exp
95256 …$ taskset -c 1 make check TESTS="gdb.base/unwind-on-each-insn.exp" RUNTESTFLAGS="--target_board=na…
95260 $ make check-read1 TESTS="gdb.base/unwind-on-each-insn.exp"
95267 FAIL: gdb.base/unwind-on-each-insn.exp: gdb_breakpoint: set breakpoint at *foo
95268 FAIL: gdb.base/unwind-on-each-insn.exp: disassemble foo
95269 …FAIL: gdb.base/unwind-on-each-insn.exp: get $sp and frame base in foo: get hexadecimal valueof "$s…
95315 hand-edit gdb/testsuite/gdb.arch/arm-disp-step.S to use %progbits instead.
95319 Tested on x86_64-linux.
95338 Tested on x86_64-linux.
95351 Tested on x86_64-linux.
95511 shouldn't be relying on the buffer contents.
95536 point fabs on some floating point values, fixed in this commit.
95546 Tested on x86_64-linux.
95560 Tested on x86_64-linux.
95628 Tested on x86_64-linux.
95658 behavior based on the input ELF, restore AC_CANONICAL_SYSTEM to
95674 gdb/testsuite: add max number of instructions check in gdb.base/unwind-on-each-insn.exp
95676 have a handful of iterations (5 on my development machine, where the
95679 FAIL: gdb.base/unwind-on-each-insn.exp - instruction 104340: maint print frame-id
95680 DUPLICATE: gdb.base/unwind-on-each-insn.exp - instruction 104340: maint print frame-id
95681 FAIL: gdb.base/unwind-on-each-insn.exp - instruction 104340: [string equal $fid $main_fid]
95682 FAIL: gdb.base/unwind-on-each-insn.exp - instruction 104340: get hexadecimal valueof "$pc"
95729 I found this to happen with ld-linux on at least Arch Linux and Ubuntu
95732 …$ ./gdb --data-directory=data-directory -nx -q -readnow -iex "set debuginfod enabled on" /lib64/ld…
95781 Regression tested on x86-64 using the cc-with-gdb-index board.
95817 gdb: declare variables on first use in inherit_abstract_dies
95887 * po/hu.po: Updated Hungarian translation.
95948 Tested on x86_64-linux, with:
96044 Previously we depended on the ordering of calls to
96080 Rather than depend on the calls to these two functions being in a
96182 on the second part containing the interactive prompt.
96186 Tested on x86_64-linux.
96203 Tested on x86-64-linux.
96225 This test case has been tested using gcc on the following x86-64 Linux
96240 RUNTESTFLAGS="CC_FOR_TARGET=clang" on all of the above expect for
96241 Fedora 28. The (old) version of clang available on F28 did not
96244 I also tried to make this test work on FreeBSD 13.1. While I think I
96256 it work on FreeBSD.
96279 commit has been tested on x86-64 linux with no regressions.
96287 generate on man pages") in 2001 and @PROGRAM@ is ineffective since then.
96306 Regen ld/po/BLD-POTFILES.in
96331 Tested on x86_64-linux.
96432 This commit is a follow on to:
96461 initialize the nr_cpus entries which we will later go on to use.
96478 extension on cygwin/mingw compilers.
96483 * MAINTAINERS: Add section on patches, copyright and DCO.
96567 Based on initial work by Jedidiah Thompson
96591 Tested on x86_64-linux.
96595 IBM zSystems: Issue error for *DBL relocs on misaligned symbols
96645 exception of Power 9. The hardware watchpoint support is disabled on
96684 The following two tests are not supported on the Power 9 system used to
96707 Tested on x86_64-linux.
96727 Tested on x86_64-linux.
96735 Executing on host: gcc -fno-stack-protector -fdiagnostics-color=never \
96745 Tested on x86_64-linux.
96753 Executing on host: cmp -s $outputs/gdb.server/file-transfer/file-transfer \
96771 Tested on x86_64-linux.
97029 I noticed one particular Ada test was failing on Fedora 34, but works
97112 be in the index -- but, based on inspection, not C++ linkage names.
97125 When building with clang 15 on Ubuntu 20.04, I get:
97157 this problem on this particular .y file because it uses `%pure-parser`
97162 ("gold: Suppress "unused" variable warning on Clang")), but then I
97339 gdb/arm: Don't rely on loop detection to stop unwinding
97341 is an ugly way to stop the unwinding. A cleaner way is to rely on
97372 Tested on x86_64-linux.
97398 Tested on x86_64-linux.
97430 Tested on x86_64-linux.
97453 FAIL: gdb.server/stop-reply-no-thread.exp: to_disable=Tthread: t_nonstop=on: \
97477 difference between the two boards mentioned is whether editing is on or off.
97489 Tested on x86_64-linux.
97510 gdb) are the same. For this host board however, gdb executes on a remote
97513 We could try to make some generic way to set TERM on the host, but for the
97520 Tested on x86_64-linux.
97528 Regression tested on x86-64 Fedora 34.
97532 gdb/arm: Stop unwinding on error, but do not assert
97593 instruction depends on whether the processor is in VLE mode (some
97663 Executing on host: gcc -fno-stack-protector \
97673 Tested on x86_64-linux.
97697 Tested on x86_64-linux.
97722 Tested on x86_64-linux.
97756 Tested on x86_64-linux.
97764 Tested on x86_64-linux.
97786 Tested on x86_64-linux.
97813 either add new CSRs, extend existing CSRs or depends on using CSRs.
97952 PowerPC, fix gdb.base/watchpoint.exp on Power 9
97953 Test gdb.base/watchpoint.exp generates 4 test errors on Power 9. The
97960 exception of Power 9. The hardware watchpoint support is disabled on
97966 on Power 9 with hardware watchpoint force-disabled. The test runs on
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
97972 no regression failures. The test fails on Power 10 due to an internal GDB
97995 but the linker doesn't support 8-byte relocation types on a 32-bit architecture.
98003 Tested on x86_64-linux with native and target board unix/-m32.
98019 The problem is that the test-cases selects an amd64 .S file based on the check:
98023 which is also true for target board unix/-m32 on x86_64-linux.
98027 Tested on x86_64-linux, using native and target board unix/-m32.
98071 Tested on x86_64-linux, with native and target board unix/-m32.
98081 on Power 9. The test uses the test [target_info exists gdb,
98084 it supports hardware watchpoints. Note, the test works fine on Power 10.
98087 exception of Power 9. The hardware watchpoint support is disabled on
98093 disabled on Power 9 but runs on all other PowerPC processors.
98095 The patch has been tested on Power 9, Power 10 and X86-64 with no
98109 Tested on x86_64-linux.
98113 [gdb/testsuite] Fix ctf test-cases on openSUSE Tumbleweed
98114 When running test-case gdb.base/ctf-constvars.exp on openSUSE Tumbleweed (with
98134 Tested on x86_64-linux.
98142 When running test-case gdb.base/gdbindex-stabs.exp on openSUSE Tumbleweed (with
98168 Tested on x86_64-linux.
98184 Tested on x86_64-linux.
98200 Tested on x86_64-linux.
98219 Tested on x86_64-linux.
98235 NULL) on glibc.
98253 later on thinks the print format should change, please feel free to do
98265 Tested on x86_64-linux.
98347 Here, target_auxv_search is called on the inferior's target stack. The
98361 that this data was obtained by reading auxv on the inferior's target
98382 latency on remote connections, when doing many queries. With the change
98460 Tested on x86_64-linux.
98498 However, this definition is now a cause of problems on modern environments.
98508 environments), we don't need to rely on the deprecated definition.
98555 To avoid warnings on the printf-like wrapper, it requires proper
98567 To avoid warnings on the printf-like wrapper, it requires proper
98582 To avoid warnings on the printf-like wrapper, it requires proper
98594 To avoid warnings on the printf-like wrapper, it requires proper
98606 To avoid warnings on the printf-like wrapper, it requires proper
98618 To avoid warnings on the printf-like wrapper, it requires proper
98630 To avoid warnings on the printf-like wrapper, it requires proper
98654 on the configure option.
98666 on the configure option.
98693 sim/riscv: fix multiply instructions on simulator
98738 The python black formatter was complaining about formatting on the
98782 Tested on x86_64-linux.
98826 It can be reliably reproduced on a recent enough GNU/Linux with this
98929 Tested on x86-64 Fedora 34.
98937 Tested on x86_64-linux.
98957 Tested on x86_64-linux.
99013 to this function, in jit.c, relied on the default value.
99029 set debug infcall on|off
99087 test relies on stale pointers, there is always a chance that GDB got lucky
99090 Regression tested on x86_64, using both gcc and clang.
99118 the class is kept on an intrusive list. When reinit_frame_cache is
99192 With native and target boards native-gdbserver, remote-gdbserver-on-localhost and
99235 Tested on x86_64-linux, using native and aforementioned target boards.
99261 Tested on Ubuntu-22.04 x86_64 with and without libc6-dbg debug symbols
99294 Tested on x86_64-linux.
99307 Tested on x86_64-linux with native and target board native-gdbserver.
99311 [gdb/testsuite] Fix have_mpx with remote-gdbserver-on-localhost
99312 With target board remote-gdbserver-on-localhost and gdb.arch/i386-mpx-call.exp
99337 Tested on x86_64-linux, with native and target board
99338 remote-gdbserver-on-localhost.
99342 [gdb/testsuite] Fix DUPLICATEs with remote-gdbserver-on-localhost
99344 remote-gdbserver-on-localhost, by using test_with_prefix.
99346 Tested on x86_64-linux, with native and target board
99347 remote-gdbserver-on-localhost.
99353 remote-gdbserver-on-localhost, I run into:
99369 Tested on x86_64-linux, with native and target boards
99370 remote-gdbserver-on-localhost, native-gdbserver and native-extended-gdbserver.
99384 fields somewhat. I chose to warn on nonsense values rather than
99392 around bfd_coff_swap_aouthdr_in. Warn on invalid SectionAlignment,
99393 FileAlignment and NumberOfRvaAndSizes. Don't return NULL on
99411 also ARM AN298, supported by Cortex-M4F architecture for details on
99415 This patch has been verified on a STM32F4-Discovery board by:
99428 D-register (D0) should be the new value (0x009..eff) on the
99447 Tested on x86_64-linux.
99472 There should be no user visible changes unless they turn on debug
99492 * riscv-dis.c (print_insn_args): Use dis_style_immediate on
99497 RISC-V: Fix T-Head immediate types on printing
99508 * riscv-dis.c (print_insn_args): Fix T-Head immediate types on
99529 This commit makes types of printf arguments on riscv_disassemble_data
99531 the cost of printf (especially on 32-bit host).
99542 fixes this issue on the RISC-V disassembler.
99552 This commit fixes certain print calls on immediate operands to have
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.
99632 Regression tested on x86-64 Fedora 34.
99671 Tested on x86_64-linux.
99706 Tested on x86_64-linux.
99720 RISC-V: Fix buffer overflow on print_insn_riscv
99776 (bfd_init_section_compress_status): Free contents on failure.
99781 initialize compress/decompress status" on compress/decompress
99850 (cross-)building on a 32-bit host.
99941 tested on gdb.cp/virtbase2.exp; the reason that test case is working
100016 Tested on x86_64-linux.
100138 depend on the new do-check-single, or will ensure the 'No matching
100196 error style, we instead give up on the styling attempt.
100224 'asm' and 'nasm' lexers based on the setting. If the setting is not
100232 that will format '#' and all other text on the line, as a comment,
100273 While working on another issue relating to GDB's use of the Python
100315 that the new condition checking functions can rely on m_dest being
100345 not available on the current architecture then these new tests will be
100368 Building on the previous commits, this commit goes through the various
100388 Building on the previous commits, in this commit I remove two
100393 own commit, because these returns of NULL appear to be depended on
100427 Building on the previous commit, this commit extends the register_name
100457 description based on the architecture.
100501 The selftest has been tested on x86-64, but I don't have access to
100543 I noticed a test failure in gdb.base/completion.exp for RISC-V on
100562 available on the current target. Indeed, there are plenty of places
100569 clearly depends on user_reg_map_regnum_to_name only returning nullptr
100581 to not rely on nullptr to indicate the end marker. Or rather, I could
100601 registers that are not supported on the current target, and that
100616 I noticed a test failure in gdb.base/completion.exp for RISC-V on a
100655 possible in one part of the pattern before moving on to the next.
100659 In short the previous implementation would leave the '\r' on the end
100774 In a later commit I want to use operator~ on a gdb_disassembly_flag
100812 the patch are grouped based on the size of the instruction, and are
100952 This is partially based on jiawei's 'Zhinx' testcases.
101023 dependency of i386-gen.o on i386-opc.h.
101057 IgnoreSize needs to remain on legacy encoded SIMD insns with GPR
101103 [gdb/testsuite] Fix gdb.mi/mi-sym-info.exp on openSUSE Tumbleweed
101121 Tested on x86_64-linux.
101157 The only extra_lines use in arrange_linetable function is removed on the
101174 Tested on x86_64-linux.
101248 Tested on x86_64-linux.
101254 * arm-dis.c (mapping_symbol_for_insn): Return false on zero
101306 our (Red Hat's) internal test infrastructure on Rawhide aarch64, s390x, x86_64,
101345 GDB fails to build for me, on Ubuntu 20.04. I get:
101429 Multi-line patterns for grep are not supported on some old versions
101511 The segv was on "info->strs[strsize - 1] = 0;" with strsize zero. OK,
101537 gold: Suppress "unused" variable warning on Clang
101546 prologue on yyscript.y.
101548 * yyscript.y: Suppress -Wunused-but-set-variable warning on
101559 auto. If pkgconfig/libzstd.pc is found, define HAVE_ZSTD and support
101649 seconds. But it's much slower if running the test on an unoptimized
101659 directory it would be named either cxxfilt or c++filt (depending on
101692 Tested on x86_64-linux.
101713 bfd_malloc_and_get_section performs some sanity checks on the section
101721 Use bfd_malloc_and_get_section. Free malloc'd buffers on failure.
101761 value of this byte depends on heap implementation and usage, but when
101763 we go on to call std::string::pop_back on the empty string which results
101786 Tested on x86_64-linux.
101814 correct target for the archive) will still be on the xvec at the point
101870 The test gdb.tui/tui-missing-src.exp fails on my CI machine, and I
102013 the problem and we can work on getting it fixed more easily than if just
102036 htab can be tidied on closing an element. Otherwise you get stale
102040 Calling _bfd_generic_close_and_cleanup on close means tdata needs to
102051 since those sections take no space on disk. Compression can only
102069 Recent version of dejagnu (1.6.3, installed on RHEL-9) includes ba60272
102087 Running .../gdb/testsuite/gdb.base/bt-on-error-and-warning.exp ...
102109 Patch tested on x86_64 RHEL-9 and ubuntu-20.04 on top of GDB and ROCgdb.
102139 applies an implicit shift by a constant value on an immediate
102315 * Additional changes if necessary (depending on the instructions)
102321 [gdb/symtab] Add all_comp_units/all_type_units views on all_units
102322 Add all_comp_units/all_type_units views on all_units.
102330 Tested on x86_64-linux.
102340 Tested on x86_64-linux.
102353 the code is auto-generated and we have no ways to deal with it.
102357 The new DIAGNOSTIC_IGNORE_UNUSED_BUT_SET_VARIABLE macro can be helpful on
102359 end of user prologues on Bison (.y) files.
102368 User-defined warnings (on Clang, "-Wuser-defined-warnings") can be harmful
102377 The new DIAGNOSTIC_IGNORE_USER_DEFINED_WARNINGS macro can be helpful on such
102443 on our testsuite makes many tests fail. This patch adds a central,
102448 epilogue that ends on another epilogue, and epilogues leading to other
102488 this difference, there are also some differences that depend on gcc
102730 A file that consists of a list of files doesn't depend on those files
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).
102793 be, so I prefer to err on the side of caution and just keep the existing
102882 Add the `length` and `set_length` methods on `struct type`, in order to remove
102900 Add the `target_type` and `set_target_type` methods on `struct type`, in order
102913 arguments on old C standards.
102931 RISC-V: Set EF_RISCV_TSO also on .option arch
102950 Compilers may not provide the attribute on functions and variables,
103031 This patch support ZTSO extension. It will turn on the tso flag for elf_flags
103103 (alpha_vms_slurp_relocs): Set reloc_done to 1 on success, -1 on
103104 failure. Return that status on subsequent calls. Check
103148 retained the copyright date range on the new library), with some minor
103152 shut down debuginfod, previously we just relied on expect shutting
103161 I have also done a little light house keeping on the original test
103242 Tested on x86_64-linux with gcc 12 and clang 14.
103278 Tested on x86_64-linux.
103296 on both little endian and big endian machines. It also works for
103356 Tested on x86_64-linux, with gcc 7.5.0 and clang 13.0.
103377 Tested on ppc64le-linux, power 10.
103439 the FAIL reproducible on x86_64-linux.
103442 Tested on x86_64-linux and aarch64-linux.
103475 Tested on x86_64-linux.
103524 Clang generates a warning on unused (technically, written but not read
103555 gprofng: fix build issues on musl
103564 pwrite64 are macros and getcontext() is absent on musl.
103576 on musl.
103583 on musl.
103664 The "@" char starts a comment on ARM.
103897 result. Regression tested on x86-64 Fedora 34.
103979 different stopping location, depending on the used compiler. With this
104004 ld: pe: Apply review suggestions on the existing exports/imports arrays
104026 but noticed while working on the code.)
104036 based on the implementation for aligncomm).
104094 Tested on x86_64-linux.
104104 Tested on x86_64-linux.
104117 That however caused a regression on ppc64le. For PowerPC, as described in the
104120 Setting a breakpoint on *$func effectively creates a breakpoint for the global
104124 Fix this by reverting commit cd919f5533c, and setting the breakpoint on
104127 Tested on x86_64-linux and ppc64le-linux.
104153 Tested on x86_64-linux, with both gcc 7.5.0 and clang 13.0.0.
104247 Tested on x86_64-linux.
104280 Vector CSRs are also required on smaller vector subsets.
104307 This test generates 48 failures on Power 9 when testing with HW watchpoints
104308 enabled. Note HW watchpoint support is disabled on Power 9 due to a HW bug.
104315 This patch was tested on Power 9, Power 10 and X86-64 with no regressions.
104332 Commit 171fba11ab27 ("Make GDBserver abort on internal error in development mode")
104387 Tested on x86_64-linux and aarch64-linux.
104401 while on x86_64-linux, I see:
104466 skipping, by setting the breakpoint on line 19 instead.
104470 Tested on x86_64-linux and aarch64-linux.
104488 16-bit parts are stored and how they are accessed later on. Arm is
104490 --enable-targets=all and on a big endian host will run into the following:
104504 the host endianness instead. The Arm selftests can be executed on non-Arm
104548 This is fixed in gas on trunk by commit 5578fbf672e ("GAS: Add a return type
104556 Tested on x86_64-linux.
104590 This patch focuses on implementing bfd_find_nearest_line_with_alt
104609 There is a portable mechanism for disassembler options and used on some
104645 When running test-case gdb.cp/cpexprs-debug-types.exp on target board
104675 Tested on x86_64-linux.
104685 Tested on x86_64-linux.
104700 Tested on x86_64-linux.
104707 There is a portable mechanism for disassembler options and used on some
104742 non-enum disassembler options on printing disassembler help.
104753 This commit removes SBREAK-related references on the simulator as it's
104822 welcome anyone who wants to take on fixing the run_sim problem
104884 RISC-V: Print highest address (-1) on the disassembler
104889 be nice because we enabled highest address printing on regular cases.
104914 fixes this by fitting an address into a 32-bit value on RV32.
104918 fixes that based on the idea of Palmer Dabbelt.
104928 * riscv-dis.c (maybe_print_address): Fit address into 32-bit on RV32.
104989 When running the gdb/configure script on ubuntu 22.04 with
105019 Tested on ubuntu-22.04 and ubuntu 20.04.
105098 A ui initializes its line_buffer, but never calls buffer_free on it.
105114 First, some background on the RISC-V registers fflags, frm, and fcsr.
105117 control mechanism on RISC-V. The fcsr is the floatint-point control
105122 CSRs) available on RISC-V. The fflags and frm registers are also
105131 How this impacts on GDB is like this: a target description could,
105202 numbers must follow on from the real (target supplied) registers.
105465 c_type_print_args on C++ functions and append their arguments to the
105804 Tested on x86_64-linux.
105854 PR29494 Trailing jump table on ARM
105857 size_inc_line_addr and emit_inc_line_addr. Pass line_delta on to
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.
105929 PR12265, Compiling ld/ fails on Solaris 8
106013 x86: Ignore protected visibility in shared libraries on Solaris
106027 isn't needed. Ignore protected visibility in shared libraries on Solaris
106029 will silently generate executable with incorrect run-time behavior on
106034 visibility in shared libraries on Solaris.
106125 tools on other OSes too.
106132 gas: arm: handle multiple .directives on a single line (PR29519)
106241 that started (or attached) to the inferior. Also, there is no way on
106324 passed on to bfd_get_relocated_section_contents. No surprises there.
106374 Regression tested on x86-64 Fedora 34.
106380 work on systems that use PIE by default. For example, on this Debian
106387 This is because entry-value-typedef-aarch64.S was generated on an old
106389 the system the test runs on tries to link the test executable as
106390 position-independent. Fix this by regenerating the same binary on the
106395 With this patch applied, the test passes on the Debian 11 AArch64
106438 a variadic argument has been passed on the stack, all future arguments
106439 will also be passed on the stack, i.e., the last argument register may
106500 computed yet (check_typedef has never been called on it). As we get in
106503 then call allocate_value on subobj_type, which does call check_typedef,
106508 Fix this by calling check_typedef on both type and subobj_type at the
106521 from the reproducer given in the bug (thanks to Pedro for suggestions on
106522 how to minimize it further than I had). Since I tested on both amd64
106552 Regression tested on x86-64 Fedora 34.
106659 just once on the first insn after .arch may have changed the things, and
106689 Fix mmo_get_byte to return a fail-safe value, not just on the first
106690 call with a read error but on subsequent calls too.
106692 * mmo.c (mmo_get_byte): Return the fail-safe value on every
106764 gdb/riscv: fix gdb.arch/riscv-unwind-long-insn.exp on RV64
106766 failing when run on a 64-bit RISC-V target.
106773 didn't match the expected frame-id that was stored on the breakpoint.
106794 With this change in place I now see this test fully passing on 32 and
106822 When working on windows-nat.c, it's useful to see an error message in
106833 argument to gdbarch_register. Regression tested on x86-64 Fedora 34.
106917 insns with multiple forms (i.e. the same Cpu64 attributes on {,V}MOVQ,
107026 going on.
107058 methods, so make it a protected method on code_breakpoint.
107082 This changes readelf output a little, removing the 0x prefix on hex
107122 When running test-case gdb.dwarf2/dw2-dir-file-name.exp on x86_64-linux, we
107138 When trying to set a breakpoint on
107200 Tested on x86_64-linux.
107219 Tested on x86_64-linux.
107258 Tested on x86_64-linux.
107281 Tested on x86_64-linux.
107371 expansion code relied on do_scrub_chars returning early. So fix that
107430 the fixed output (depending on the two criteria above)
107459 The x0 (zero) register is read-only on RISC-V. Implement the
107462 Without this method GDB will try to write to x0, and relies on the
107472 Disable year 2038 support on 32-bit hosts by default
107474 64-bit time_t by default on 32-bit hosts that support it.
107538 such that efi images can be made natively on Linux.
107543 "RVA truncated" error when using objcopy on loongarch64.
107547 Any magic number is based on the Microsoft PE specification [1].
107623 When running on a native RISC-V Linux target I currently see failures
107743 When running test-case gdb.dwarf2/debug-names.exp on openSUSE Tumbleweed, I
107754 Tested on x86_64-linux.
107947 Mach-O: i18n enablement on some error messages.
108001 Tested on x86_64-linux.
108050 (typically the case on openSUSE), and
108083 Tested on x86_64-linux.
108122 changes it to return false on silly alignment values, avoiding yet
108126 gives up on other setup operations that are necessary even after an
108137 * objcopy.c (setup_section): Keep on going after hitting
108143 Do the shift using unsigned variables to avoid UB on << 8.
108175 When building gdb on openSUSE Leap 15.3, using gcc 7.5.0, I run into:
108206 Tested on x86_64-linux.
108220 Tested on x86_64-linux.
108276 Parallel for: elements on worker thread 0 : 705
108277 Parallel for: elements on worker thread 1 : 705
108278 Parallel for: elements on worker thread 2 : 704
108279 Parallel for: elements on worker thread 3 : 0
108280 Parallel for: elements on main thread : 704
108287 Parallel for: elements on worker thread 0 : 752 (size: 371811790)
108288 Parallel for: elements on worker thread 1 : 360 (size: 371509370)
108289 Parallel for: elements on worker thread 2 : 1130 (size: 372681710)
108290 Parallel for: elements on worker thread 3 : 0 (size: 0)
108291 Parallel for: elements on main thread : 576 (size: 367671995)
108294 Tested on x86_64-linux.
108302 Tested on x86_64-linux.
108311 auto lambda = [&] (int) { ... };
108312 auto fv = gdb::make_function_view (lambda);
108316 auto lambda = [&] (int) { ... };
108320 optional function_view parameter, whose type depends on the function's
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
108372 * dwarf.c (fetch_indexed_value): Return -1 on error.
108410 When debugging cc1 I heavily rely on simple one-parameter debug functions
108421 Tested on x86_64-linux, by breaking on varobj_create, and doing:
108526 Tested on x86_64-linux.
108562 Tested on x86_64-linux, also by adding:
108605 Tested on aarch64-linux.
108695 use-after-free bugs, because it ensures that anything allocated on the
108722 * cache.c (bfd_cache_delete): Set BFD_CLOSED_BY_DELETE on the
108724 (bfd_cache_lookup_worker): Clear BFD_CLOSED_BY_DELETE on the newly
108759 Tested by rebuilding on x86_64-linux with clang 15 and gcc 12.
108806 - Instead check opcode space, even if just to be on the safe side going
108820 operation. With that, D can simply be set on the first of the two
108866 access model based on whether the symbol itself is marked as local (i.e.
108871 shared library, and if that happens on a local symbol then we currently
108875 happen when we have seen both an IE and GD access on the same symbol.
108878 The second problem is that deciding based on whether the symbol is local
108880 and known to be located in the executable. This happens on all global
108884 Here we adjust the condition we base our relaxation on so that we relax
108896 main TLS block. This means that we can perform a stronger relaxation on
108899 Hence we have to update all tests that relied on the older suboptimal
108910 tests are now only available on targets with that.
108958 comply with register ordering on push statements, being that registers
108959 are stored on the stack in numerical order, with the lowest numbered
108997 objdump -x on PE executables produces lots of "xdata section corrupt"
109023 object files instead of passed manually on the command line.
109048 Tested on x86_64-linux.
109081 hex number. Unfortunately they depend on both target and host, which
109214 while on x86_64-linux instead, I get:
109221 We can easily reproduce this on x86_64-linux using:
109269 Tested on x86_64-linux.
109289 assembled-based one tests some hard-coded debug info based on what I
109302 the new procs is based on what was done for rnglists and loclists.
109420 the compiler on the command-line.
109456 we should design things such as to rely on it. It's a heuristic, it can
109458 some good debug info, we don't end up relying on that for things to
109476 today, it is a bit dependent on the debug info). Second, it would
109501 subfile successfully, and avoid relying on
109530 Of all the cases I tried, the only one I found that ends up relying on
109791 Tested on x86_64-linux and aarch64-linux.
109797 Re: PR16005, avr linker crash on a particular instruction sequence with --relax
109897 PR16005, avr linker crash on a particular instruction sequence with --relax
109908 It's entirely unclear why some of the KeyLocker insns had NoRex64 on
109955 needs to be disabled on all SPARC targets, not just Solaris/SPARC: the
109960 Tested on sparc64-unknown-linux-gnu and sparc-sun-solaris2.11.
109971 [gdb/testsuite] Fix gdb.threads/killed-outside.exp on aarch64
109972 On aarch64 (and likewise on arm), I run into:
109975 Executing on target: kill -9 11516 (timeout = 300)
109994 Tested on aarch64-linux, and x86_64-linux.
110057 The guile code has a couple of unused functions that touch on the
110064 allocated on that objfile are copied. A temporary hash map is created
110065 during this process, and it is allocated on the destroyed objfile's
110276 breakpoints on these hosts:
110312 running kernel, enabling GDB to insert breakpoints on these older
110316 Tested on {unix,native-gdbserver,native-extended-gdbserver}/-m{32,64}
110317 on x86_64, s390x, aarch64, and ppc64le.
110377 Tested on x86_64-linux.
110399 I tried building GDB on GNU/Hurd, and ran into this error:
110443 As Luis pointed out, similar bugs may also appear on FreeBSD and NetBSD,
110444 and I have reproduced them on both systems. This patch fixes them
110447 Tested by rebuilding on GNU/Hurd, FreeBSD/amd64 and NetBSD/amd64.
110452 I ran into this error when building GDB on NetBSD:
110474 Tested by rebuilding on NetBSD/amd64.
110504 I've also updated the comment on 'struct gdbarch_tdep_base' to fix a
110505 typo, and the comment on the 'gdbarch_tdep' function, to mention that
110544 Tested on x86_64-linux
110550 variable) and expression. All of those can reference data on an
110589 Tested on x86_64-Linux.
110679 is "auto". Simon noticed that GDB's implementation doesn't
110691 .pyc files on the import of source modules.
110779 add a fallback standard-conforming implementation based on arrays.
110781 I ran the testsuite on x86_64 GNU/Linux with this implementation
110805 struct packed: Use gcc_struct on Windows
110806 Building GDB on mingw/gcc hosts is currently broken, due to a static
110853 file, after this commit, any git diff on a C, C++, Expect, or TCL
110863 Errors are only highlighted in the diff on new or modified lines, so
110864 you don't get spammed for errors on context lines that you haven't
110870 issues any time you edit a line. For GDB we're usually pretty good,
110884 pointers on Arm targets that contain more than one stack pointer.
111112 On seeing PR29369 my suspicion was naturally on a recent powerpc64
111152 Tested on x86_64 openSUSE Tumbleweed.
111177 cc-with-debug-names on a system with gcc 12.1.1 (defaulting to dwarf 5), I
111204 Tested on x86_64-linux.
111224 Regression tested on x86-64 Fedora 34.
111235 Tested on x86_64-linux.
111374 I built GDB for all targets on a x86-64/GNU-Linux system, and
111376 the binary on the native target. I got this error:
111379 The target architecture is set to "auto" (currently "i386").
111383 The target architecture is set to "auto" (currently "riscv:rv32").
111388 What's going on here is this; initially the architecture is i386, this
111389 is based on the default architecture, which is set based on the native
111391 current inferior is updated based on the architecture of the
111412 i386_gdbarch_tdep. After this cast we are relying on undefined
111417 start an executable of the wrong architecture on a native target. I
111452 In the next commit I will build on this change to add an assertion in
111475 placing a breakpoint on a particular symbol.
111509 I discovered this issue while working on a later patch in this
111513 With this later patch in place I ran gdb.multi/multi-arch.exp on an
111521 fail (they rely on reading symbols from the current program space),
111548 actually relying on undefined behaviour.
111550 Consider building GDB for all targets on x86-64/GNU-Linux, then doing
111554 Zeroing of upper 32 bits of 64-bit addresses is auto.
111565 example above, on an x86-64 native target, the current target
111587 After this commit the output of the above example command, still on my
111591 Zeroing of upper 32 bits of 64-bit addresses is "auto" (current architecture is not MIPS).
111595 get the more commonly seen 'currently "on"' or 'currently "off"', like
111601 Zeroing of upper 32 bits of 64-bit addresses is "auto" (currently "off").
111621 so, if I build GDB for all targets on an x86-64/GNU-Linux system, I
111662 Tested by running the selftest on x86_64-linux with python 3.11.
111687 Tested on x86_64-linux.
111697 Tested by rebuilding on x86_64-linux.
111705 /* Don't crash on bad data. */
111763 Tested on x86_64-linux, with native and target board cc-with-debug-names.
111769 x86: replace wrong attributes on VCVTDQ2PH{X,Y}
111837 Put abbrevs on abbrev_lists here.
111855 (process_abbrev_set): Print actual section name on error.
111858 (process_debug_info): ..or here. Warn on another case of not
111863 PowerPC64: fix build error on 32-bit hosts
111877 This commit fixes a build error on machines lacking python headers
111894 Python 3.9. I've tested these changes on Fedora 34, Fedora 36, and
111895 rawhide, though complete testing was not possible on rawhide due to
111998 step over the 3 lines below and land on the return statement. If
112013 FAIL: gdb.threads/step-N-all-progress.exp: non-stop=off: target-non-stop=on: next 3 (timeout)
112029 Focusing now on when the first step finishes -- we're in "all-stop"
112051 New test included. Tested on x86-64 GNU/Linux native and gdbserver.
112137 reported on the executable link, not on the innocent shared object link.
112176 Build-tested with --enable-targets=all and regression tested on aarch64-linux
112200 Tested on aarch64-linux Ubuntu 20.04.
112280 Put gdb.base/bt-on-fatal-signal.exp GDB cores in output dir
112281 I noticed that gdb.base/bt-on-fatal-signal.exp was contributing four
112284 $ make check TESTS="gdb.base/bt-on-fatal-signal.exp"
112304 ./testsuite/outputs/gdb.base/bt-on-fatal-signal/core.gdb.1676506.nelson.1657727692
112305 ./testsuite/outputs/gdb.base/bt-on-fatal-signal/core.gdb.1672585.nelson.1657727671
112306 ./testsuite/outputs/gdb.base/bt-on-fatal-signal/core.gdb.1674833.nelson.1657727683
112307 ./testsuite/outputs/gdb.base/bt-on-fatal-signal/core.gdb.1673709.nelson.1657727676
112309 (Note the test is skipped at the top if on a remote host.)
112344 ui_unregister_input_event_handler, replacing them with methods on
112387 Tested on x86_64-linux.
112393 python executable. For example, on my Fedora system the python2
112398 It is quite possible to only have python3 available on a system.
112405 'python', and then 'python3'. Now, on a system that only has a
112410 I've tested this on my local machine by removing the
112440 Parallel for: elements on worker thread 0 : 1817
112441 Parallel for: elements on worker thread 1 : 1817
112442 Parallel for: elements on worker thread 2 : 1817
112443 Parallel for: elements on worker thread 3 : 0
112444 Parallel for: elements on main thread : 1820
112447 Note that there are 4 active threads, and scheduling elts_per_thread on each
112459 Parallel for: elements on worker thread 0 : 1818
112460 Parallel for: elements on worker thread 1 : 1818
112461 Parallel for: elements on worker thread 2 : 1818
112462 Parallel for: elements on worker thread 3 : 0
112463 Parallel for: elements on main thread : 1817
112466 Tested on x86_64-linux.
112480 Tested on x86_64-linux, by building with -fsanitize=address and running
112500 Tested on x86_64-linux, with gcc 7.5.0, 8.2.1 and 12.1.1.
112517 Tested on x86_64-linux.
112532 Parallel for: elements on worker thread 0 : 1817
112533 Parallel for: elements on worker thread 1 : 1817
112534 Parallel for: elements on worker thread 2 : 1817
112535 Parallel for: elements on worker thread 3 : 0
112536 Parallel for: elements on main thread : 1820
112542 Tested on x86_64-linux.
112588 The test gdb.base/infcall-nested-structs-c.exp fails on a gdb assert
112605 The patch has been tested on Power 10, ELFv2. It fixes the following list
112606 of regression failures on Power 10:
112612 The patch has been tested on Power 8 BE which is ELFv1.
112647 Disable the Traceback Table generation on PowerPC for this test. The
112667 Run 'black' on gdb
112668 Running 'black' on gdb fixed a couple of small issues. This patch is
112693 Tested on x86_64-linux.
112707 Tested on x86_64-linux, by using it instead of the parallel_for_each in
112738 Tested on x86_64-linux, with gdb build with gcc 4.8.5.
112759 Tested on x86_64-linux.
112781 Tested on x86_64-linux.
112809 Tested on x86_64-linux.
112817 the code on the false branch of md_parse_name is dead.
112887 On PowePC, the test fails on a compile error:
112907 The patch has been tested and verified on a Power10 system.
112914 The patch was run on a Power 10 system. The gdb Summary for the run lists
112925 test gdb.base/step-indirect-call-thunk.exp fails on Intel X86-64 with the
112928 Executing on host: gcc -fno-stack-protector -fdiagnostics-color=never
112943 to be "-fcf-protection=none" for the test to compile on Intel.
112946 an error on other platforms. A check for X86 is added so the test will
112947 only run on X86 platforms.
112949 The patch has been tested and verified on Power 10 and Intel X86-64 systems
112977 longjmps on error. The testcase can be reduced to this:
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.
113086 - Describe "step" in terms of "on" and "off".
113111 Tested on x86_64-linux.
113125 Tested on x86_64-linux with native and target board unix/-m32.
113153 Tested on x86_64-linux.
113253 Tested on x86_64-linux.
113305 these new structs, which align on the natural alignment of the
113343 build GDB. Even a few BFD headers use on ATTRIBUTE_PACKED on external
113422 [Note: the testcased added by this commit depends on
113432 but on teardown, if the target uses exit_inferior_silent, then you'll
113523 just unpushes, and relies on core_target::close to actually do the
113581 maintenance set libopcodes-styling enabled on|off
113620 setting 'libopcodes-styling enabled' has an "auto-off" type behaviour.
113624 The target architecture is set to "auto" (currently "i386:x86-64").
113626 Use of libopcodes styling support is "on".
113628 the setting defaults to "on" for architectures that support libopcodes
113634 Use of libopcodes styling support is "off" (not supported on architecture "sparc")
113638 still "on" at this point though, if the user switches back to
113639 i386:x86-64 then the setting would go back to being "on".
113648 (gdb) maintenance set libopcodes-styling enabled on
113649 Use of libopcodes styling not supported on architecture "sparc".
113653 attempting to switch the setting "on" for an unsupported architecture
113656 (gdb) set architecture auto
113657 The target architecture is set to "auto" (currently "i386:x86-64").
113660 (gdb) maintenance set libopcodes-styling enabled on
113662 Use of libopcodes styling support is "on".
113665 they can one again turn this setting "on".
113692 depend on the state of the gdb_disassemble_info object, and this state
113693 might need to be updated, depending on what is being printed.
113759 Tested on x86_64-linux.
113774 Tested on x86_64-linux.
113866 This allocates entries added to the string hash tables on the notes
113904 core_optab memory on the notes obstack. It would be possible to free
113905 core_optab memory by using a custom hash table del_f on x86, as I do
113989 (main): Init notes obstack, and arrange to be freed on exit.
114022 * dw2gencfi.c (get_debugseg_name): Allocate on notes obstack.
114076 * read.c (read_symbol_name): Free name on error path.
114207 Tested on x86_64-linux.
114254 Tested on x86_64-linux.
114285 /* Don't crash on bad data. */
114306 Tested on x86_64-linux.
114328 Tested by rebuilding on x86_64 openSUSE Tumbleweed with gcc 12.
114373 Trying to run a simple program (empty main) on AIX, I get:
114426 This is due to some bit-rot in the AIX port, still relying on the entry
114436 pid is non-zero. Since inferior_ptid is set to null_ptid on entry, the
114468 on top of rs6000_nat_target, also relies on inferior_ptid.
114478 accept as a parameter the pid of the process we are working on.
114486 As well as break on main:
114524 I've noticed this because current llvm-dwarfdump crashed on an
114528 The older llvm-dwarfdump found on Ubuntu 20.04 (LLVM 10) reads the
114666 GPROFNG_VARIANT depends on compiler options, not on $(host).
114694 RISC-V: Fix requirement handling on Zhinx+{D,Q}
114695 This commit fixes how instructions are masked on Zhinx+Z{d,q}inx.
114702 on INSN_CLASS_{D,Q}_AND_ZFH_INX.
114704 on INSN_CLASS_{D,Q}_AND_ZFH_INX.
114726 This command works for C/C++ applications on x86_64. Using one or more gprofng
114760 Don't go as far as also making D work on the two 5-operand XOP insns:
114868 Tested on x86_64-linux.
114902 kernel since 5.19-rc1 on June 5, 2022. This commit adds orig_a0 which
114968 alloc gas seginfo on notes obstack
114969 Lots of memory used in gas should go on this obstack. The patch also
114970 frees all the gas obstacks on exit, which isn't a completely trivial
114989 memory on a bfd objalloc in objcopy and other utils.
115032 Tested on x86_64-linux.
115080 There are two related problems here: The use of "addr32" on a direct
115108 [gdb/symtab] Fix data race on per_cu->dwarf_version
115163 Tested on x86_64-linux.
115195 Tested on x86_64-linux.
115224 earlier on in the word processed.
115236 as it now goes on to propose the entire symbol table, while:
115294 only tested objects allocated on the stack. This commit adds a couple of
115345 Tested on x86_64-linux, with and without -fsanitize=thread.
115354 the PDF is generated on my machine.
115372 …==127719==ERROR: AddressSanitizer: heap-use-after-free on address 0x60f0000000e9 at pc 0x55bcbfa30…
115454 (S16 to S31) are stacked on exception entry or otherwise skipped.
115499 gdb/testsuite: fix gdb.base/break-idempotent.exp on ppc
115500 When running the gdb.base/break-idempotent.exp test on ppc, I was
115549 we call skip_hw_watchpoint_tests for the first time on powerpc, GDB
115557 After this change break-idempotent.exp runs fine on powerpc.
115648 Tested on x86_64-linux.
115652 bfd: handle codepage when opening files on MinGW
115653 Even if MS docs say that CP_UTF8 should always be used on newer
115662 ___lc_codepage_func() on MinGW.
115749 1. s0 and s1 correspond to fr0, s4 and s5 correspond to fr1, and so on.
115752 and so on. Every four pseudo registers corresponds to a vector register.
115886 handling for H. Change handling on RV32.
115906 mentions that it used to be 555 on the Gnats system and seems to relate
115910 mentions being number 1270 on Gnats, and mentions annota1 specifically,
115935 Build on x86_64-linux, with and without --enable-shared.
115947 Make GDBserver abort on internal error in development mode
115960 modes, I propose to make GDBserver abort on internal error if in
115981 A "--target_board=native-extended-gdbserver" run on Ubuntu 20.04 ends
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.
116085 Tested on x86_64-linux with target boards unix/-m32 and unix/-m32/-fPIE/-pie.
116099 Tested on x86_64-linux with target boards unix/-m32.
116127 Tested on x86_64-linux.
116139 Tested on x86_64-linux, with gfortran 4.8.5, 7.5.0, and 12.1.1.
116176 The offset 8 is based on reader->cu->header.addr_size:
116199 Tested on x86_64-linux.
116232 Tested on x86_64-linux.
116265 Note that I didn't touch */po/*.po{,t} on the assumption that these
116398 is currently based on 'info_ptr', which does not always point to the
116399 start of the CU. This patch fixes the expression. Tested on x86-64
116522 For example, here's what I get on x86-64 Ubuntu 20.04, with this
116602 changed, at least on development builds, but that would be for another
116642 end, I settled on the script approach for serial mode too, which
116738 of these functions depend on the value of the async field, so I
116741 Tested on x86-64/Linux passes with no regressions.
116808 break, but the error should be reported on the executable link, not on
116816 ("aarch64: Disallow copy relocations on protected data").
116837 moves the MI interpreter to mi-interp.h, which cuts down on
116848 aarch64: Disallow copy relocations on protected data
116858 glibc 2.36 will warn on copy relocations on protected data. Let's
116859 produce a warning at link time, matching ld.lld which has been used on
116950 This commit adds 'H' to canonical extension ordering based on current
116957 canonical extension ordering based on current consensus.
117031 false-positive test failures on some platforms (observed on
117044 A missing paren led to an intended cast to avoid dependence on the size
117077 elements in the input on the end. At output time, the CU name will
117096 (no effect on ld, which doesn't use CU mappings at all), and causing
117098 doing the last one (no effect on ld, which only ever does one
117121 and blank out ctf_link_in_out on the corresponding inputs.
117180 Tested on x86-64 Fedora 34.
117186 * prdbg.c (pr_function_type): Free "s" on failure path.
117190 * stabs.c (parse_stab_struct_fields): Free "fields" on failure path.
117252 Tested on x86_64 openSUSE Tumbleweed.
117263 print nibbles [on|off]'. The default value if OFF, which can be changed
117283 (gdb) set print nibbles on
117287 Tested on x86_64 openSUSE Tumbleweed.
117308 demand_copy_C_string, which puts the name on the gas notes obstack.
117314 names on the obstack, which is more efficient anyway. (You still
117315 can't obstack_free on error paths due to the xtensa
117320 * config/obj-elf.c (obj_elf_section_name): Create name on notes
117330 * bucomm.c (make_tempdir, make_tempname): Free template on all
117335 * stabs.c (stab_demangle_v3_arg): Free dt on failure path.
117349 cannot use aggregate initialization on them. That rule changed after
117516 When testing on openSUSE Leap 15.4 I ran into this FAIL:
117536 Tested on x86_64-linux.
117594 * dwarf.c (display_debug_frames): Set col_type[reg] on sizing
117596 Handle DW_CFA_restore and DW_CFA_restore_extended on second
117598 call frame_need_space on second pass over FDE.
117610 sim: fix BFD_VMA format arguments on 32-bit hosts [PR gdb/29184]
117611 Noticed format mismatch when attempted to build gdb on i686-linux-gnu
117712 This commit started from an observation I made while working on some
117765 Python script, i.e. all additional output has to fit on a single line,
117854 After this, the next commit can focus entirely on providing a Python
117924 I think this cleanup is worth doing on its own, however, in a later
117926 to using gdbpy_ref means that I can rely on the default copy
117939 When building trunk on openSUSE Leap 15.3 with system gcc 7.5.0, I run into:
117965 Tested on x86_64-linux, by completing a build.
117986 Just like on s390x with g++ 11.2.1 and ppc64le with g++ 11.3.1 g++ 11
117987 on hppa produces a spurious warning for stringop-overread in
117988 debuginfod_is_enabled for url_view. Just always suppress it on all
118006 the section on <rate> == <interval>, had a dangling
118033 When running test-case gdb.python/py-mi-cmd.exp on openSUSE Leap 42.3 with
118057 Tested on x86_64-linux.
118064 Furthermore, the FP registers aren't automatically saved on a task
118115 handling based on features determined, GPR regset support, and software
118122 With this patch on LoongArch:
118218 > > Tested on x86_64-linux.
118257 BFD_RELOC_16, emitted by generic code to handle fixups on 16-bit data
118258 directives, expects fixups to operate on the whole of a 16-bit word.
118289 unchanged section contents on attempting to apply R_MIPS_16.
118353 Tested on x86_64-linux.
118379 Tested on x86_64-linux.
118396 checking whether to use babeltrace... auto
118461 Tested on x86_64-linux.
118467 instance(s)") was based on an improperly refreshed patch. Correct the
118530 (zero)initializing on every invocation: Convert the op_out structure
118547 updating this test not to allocate the mutable addrmap on an obstack.
118550 While working on addrmaps, I noticed that psymtab_addrmap is no longer
118573 method calls on the objects themselves.
118618 With the registry rewrite series, on Fedora 34, I started seeing this
118666 This patch has been tested on Power 10 and Intel with no test failures.
118671 Some of the ioctl numbers are based on the size of kernel termios structure.
118692 This patch also changes the hard coding to generate the number based on a
118719 different true/false values based on compiler version then we'd just
118761 Tested on x86_64-linux.
118790 Tested on x86_64-linux.
118808 GDB's ability to run 32-bit ARM processes on an AArch64 native target
118819 modified, forgetting that any particular thread (running on the native
118847 thread! Things go downhill from there on.
118880 sense when debugging on an AArch64 native target. These function
118908 specifying ARM_CC_FOR_TARGET on the command line actually does
118917 that LR is set to 0xffffffff on reset.
118920 to 0xffffffff on warm reset if Main Extension is implemented,
118942 compiler_info based on the language passed as an argument to
118948 set based on the C++ compiler in use, while if the first call to
118950 set based on the C compiler.
118976 for each test script, hence, if a test script just checks on the C
118977 compiler, or just checks on the C++ compiler, then compiler_info will
119007 From that point on compiler_info will never be recomputed!
119043 suitable result depending on how the user called test_compiler_info.
119143 While testing on AArch64 I spotted a duplicate test name in the
119172 I ran into this error while working on AArch64 GDB:
119252 This of course relies on there not being more than 16 styles, but that
119282 on its behalf. This content is printed directly to the output stream,
119287 In some (not very scientific) benchmarking on my machine,
119302 The following commit changes the output format for the isel instruction on
119336 on Power 7, Power 8, Power 9 and Power 10.
119341 The patch has been tested on Power 7 and Power 10 to verify the patch fixes
119357 compilers, making sure that the produced executable runs on the target
119563 This patch turns some windows-nat.c static functions into methods on
119568 Allow ASLR to be disabled on Windows
119572 cautions that this isn't available on all versions of Windows, the
119600 Tested on x86_64-linux.
119611 Tested on x86_64-linux.
119694 Tested on x86_64-linux.
119714 Tested on x86_64-linux.
119766 Tested on x86_64-linux.
119815 Make sure we error out on overflow instead of truncating in all cases.
119817 Tested on x86_64-linux, with a build with --enable-targets=all.
119825 Furthermore, make sure we error out on overflow instead of truncating in all
119828 Tested on x86_64-linux, with a build with --enable-targets=all.
119835 Make sure we error out on overflow instead of truncating in all cases.
119838 on what I found at
119842 Tested on x86_64-linux, with a build with --enable-targets=all.
119847 Make sure we error out on overflow instead of truncating in all cases.
119854 Tested on x86_64-linux, with a build with --enable-targets=all.
119859 Make sure we error out on overflow instead of truncating in all cases.
119866 Tested on x86_64-linux, with a build with --enable-targets=all.
119892 Furthermore, make sure we error out on overflow instead of truncating in all
119895 Tested on x86_64-linux.
119933 Furthermore, make sure we error out on overflow instead of truncating in all
119936 Tested on x86_64-linux with --enable-targets=all.
119967 Tested on x86_64-linux with --enable-targets=all.
119989 claim proper testing on x86_64-linux.
120008 trying to pass on some order and fail on another order.
120013 Tested on x86_64-linux.
120030 Tested on x86_64-linux.
120120 Tested on x86_64-linux.
120138 Tested on x86_64-linux.
120150 Don't use gregset.h in *-tdep.c since it's not usable on
120159 * elf32-mips.c (mips_elf_final_gp): Don't segfault on symbols
120171 * coff-mips.c (mips_gprel_reloc): Don't segfault on any of
120214 Tested on x86_64-linux.
120340 (depending on the particular .c file) -- and this declares it in a
120350 When execute the following command on LoongArch:
120361 branch instruction and determine the address of the next instruction on
120384 Fix a new warning on Cygwin
120489 (parse_comp_unit): Set unit->error on err_exit path.
120519 Tested on x86_64-linux.
120525 the current language without (1) ever having the value "auto" or (2)
120541 calculate the correct offset on the stack, the values were not saved.
120550 on a STM32F407-DISC0 board, but the upper 8 registers on Cortex-M33
120561 the same registers using "info float" on frame 2 (the frame just
120680 Regression tested on x86-64 Fedora 34.
120728 stack will keep the variable locally on the stack and not define a
120755 object "derived_type obj" goes on the stack which is then passed-by-value
120759 object. Right after each of the functions the object gets freed - on the
120761 free on the heap allocated string which leads to a double free. Instead
120864 while anythings else can be displayed as well (depending on the
120982 read them on-demand through read_type_die. */
120993 that the type is actually defined on line 41 (which is what is emitted by
121014 flang and ifx on the other hand this is not the case. The two compilers
121071 valid Fortran. It is missing the external keyword on the
121144 Classic and LLVM flang were each tested with their latest releases on
121185 doing an lserach on the options passed to the procedure.
121189 or false depending on whether or not the argument is found in the
121191 lsearch on the procedure options in the rest of the procedure.
121222 claimed on gcc.gnu.org/fortran.
121228 inconsequent to only implement this for f90 but, on the other hand, f77
121263 access u.def.section on non-default visibility undefined symbol.
121325 gdb/testsuite: fix gdb.trace/signal.exp on x86
121355 @item edit @var{location}
121389 based on the user-specified location spec. Then use "location
121469 The following test fails on the armeb-gnu-eabi target:
121691 While working on another patch[1] I had need to touch this code in
121704 The problem I ran into when working on this code can be seen by
121818 modifier is on the last register operand (with a possible immediate
121923 This fixes the build on older FreeBSD systems without support for
121938 Regression tested on x86_64-linux.
121963 - set detach-on-fork off
121970 Make breakpoint pending on future shared library load? (y or [n]) y
122057 Note that not having the debug info on the main binary is not strictly
122064 detach-on-fork off, follow-fork-mode child, infrun.c sets
122087 for (auto *iter : qf)
122101 Regression tested on x86_64-gnu-linux.
122133 each index is finalized on its own, in a worker thread. The cost
122142 When run on gdb itself, the memory cost seems rather low -- on my
122165 Regression tested on x86-64 Fedora 34.
122173 ba951afb999 2022-05-03 changed behaviour on arm and score regarding
122202 gdb/linux-nat: xfer_memory_partial return E_IO on error
122214 Regression tested on x86_64-linux-gnu.
122230 Tested on x86_64-gnu-linux.
122284 The "-" sign is inspired on how the TUI represents breakpoints on the
122304 be silent on PASS, now started emitting PASS messages based on
122332 Tested on x86_64 GNU/Linux, native and native-extended-gdbserver. I
122350 be silent on PASS, now started emitting PASS messages based on
122379 detection that prohibits RV32Q on 'Q' version 2.2 or later.
122386 showing RV32IQ fails on 'Q' extension version 2.0.
122390 showing RV32IQ fails on ISA specification version 2.2.
122392 showing RV32IQ succesds on 'Q' extension version 2.2.
122394 showing RV32IQ succesds on ISA specification 20190608.
122478 Tested on x86_64-linux.
122512 Tested on x86_64-linux.
122543 Tested on aarch64-linux-gnu, with a GCC with DFP support in the PATH,
122548 Merge config/ changes from GCC, to enable DFP on AArch64
122603 This also fixes the build on hosts such as FreeBSD that do not define
122609 When execute the following command on LoongArch:
122616 FAIL: gdb.base/auxv.exp: load core file for info auxv on native core dump
122617 FAIL: gdb.base/auxv.exp: info auxv on native core dump
122619 UNSUPPORTED: gdb.base/auxv.exp: info auxv on gcore-created dump
122629 gdbarch method to iterate over core file register note sections on LoongArch.
122654 Tested on x86_64-linux.
122661 (gdb) PASS: gdb.ada/access_to_packed_array.exp: set logging enabled on
122683 Tested on x86_64-linux.
122698 Tested on x86_64-linux.
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.
122886 bikeshed on the naming.
122895 Test "set multiple-symbols on" creating multiple breakpoints
123091 type without relying on set_raw_breakpoint, and similarly,
123092 momentary_breakpoint_from_master not rely on
123242 to store a 64-bit prefix instructions on Big Endian (BE) systems, the .quad
123246 on BE gets messed up since GDB fetches the suffix first and interprets it
123252 For example on BE we have two prefixed instructions stored using the
123269 The patch has been tested on Power 10 and Power 7 BE and LE to verify
123364 (but not full) debug information turned is on, we go from 6 ms to
123381 Yes, this patch introduces fails on arm/aarch64. Not a problem with
123440 filter based on object-regexp, and in the other, to remove the
123449 gdb: testsuite: Support displaced stepping on LoongArch
123450 When execute the following command on LoongArch:
123459 on LoongArch.
123469 with this patch on LoongArch, there is no failed testcases.
123477 …gdb/testsuite/gdb.base/step-over-syscall.exp: if {$displaced == "on" && ![support_displaced…
123487 …gdb/testsuite/gdb.threads/step-over-lands-on-breakpoint.exp: if { $displaced != "off" && ![supp…
123489 …gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.exp: if { $displaced != "off" && ![supp…
123500 IS_ABSOLUTE_PATH. IS_ABSOLUTE_PATH accesses [0] on that string_view,
123522 Like the placeholder types added in 04dfe7aa5217 ("Arm64: follow-on to
123556 --strip-debug. Set BSF_FILE on these symbols to change that.
123588 _bfd_real_fopen should not use ccs parameter on Windows
123625 Arm64: follow-on to PR gas/27217 fix
123673 Fix missing -wrap on gdb_test_multiple in gdb.base/kill-after-signal.exp
123674 that is causing regression test on x86_64-linux with taskset -c 0.
123678 [AArch64] Return the regnum for PC (32) on aarch64
123750 Tested on x86_64-linux.
123758 Tested on x86_64-linux.
123789 between GCC and binutils where GCC has FP16 on by default and gas doesn't.
123858 syscall with "int 0x80". This causes a segfault on kernels with
123900 errors out e.g. on a recording with only gaps.
123947 issue the question, so this test would start failing on older GCCs.
124079 true on a system where HAVE_POLL is not defined, by calling
124130 Fix Ada exception regression on Windows
124132 it caused "catch exception" and related commands to fail on Windows.
124149 errors, as most of these tests are not inside loops. All cases on which
124204 Tested using the AdaCore internal test suite on Windows. I also did
124211 write on" (equivalent), and then poke memory expecting it to patch the
124277 "set write on" testcases at all, this is the first one.
124279 Tested on x86-64 GNU/Linux, gdb, ld, binutils, and gas.
124301 PTR will disappear from ansidecl.h and libiberty on the next import
124307 When running test-case gdb.cp/break-f-std-string.exp on openSUSE Leap 15.3
124341 Tested on x86_64-linux, with:
124360 gdb: Workaround stringop-overread warning in debuginfod-support.c on powerpc64
124361 Just like on s390x with g++ 11.2.1, ppc64le with g++ 11.3.1 produces a
124363 for url_view. Also suppress it on powerpc64.
124368 DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD on powerpc64.
124377 Also, depending on the target (64-bit/32-bit), long doubles may not
124385 These divergences cause the following FAIL's on aarch64/arm:
124390 With the above in mind, extend the test a little so it behaves well on
124401 Tested on x86_64 (16 PASS), i686 (16 PASS), aarch64 (12 PASS) and arm (9 PASS).
124410 Tested on x86_64-linux.
124414 [gdb/testsuite] Fix gdb.dwarf2/dw2-out-of-range-end-of-seq.exp on aarch64
124430 - the FAIL triggers on aarch64-linux, but not on x86_64-linux, because the
124433 - on aarch64-linux, there's no prologue, so main_label and main coincide,
124435 - on x86_64-linux, there's a prologue, so main_label is different from main.
124443 Tested on both x86_64-linux and aarch64-linux.
124462 The new test failed on s390-linux due to bfd_sprintf_vma trimming
124502 Tested on x86_64-linux.
124520 Make breakpoint pending on future shared library load? (y or [n]) n^M
124531 Tested on x86_64-linux.
124535 [gdb/testsuite] Fix gdb.base/maint.exp on powerpc64le
124551 Tested on x86_64-linux and powerpcle-linux.
124556 Regenerate syscalls/{ppc64,ppc}-linux.xml on a system with 5.14 kernel.
124576 Tested on x86_64-linux, with:
124585 unix/-m32 on openSUSE Tumbleweed, I run into:
124615 Tested on x86_64-linux.
124692 PR build/29110 points out that GDB fails to build on mingw when the
124718 Make breakpoint pending on future shared library load? (y or [n]) n
124765 print a type in a given language, avoiding a dependency on the current
124790 Currently, on any remotely modern GNU/Linux system,
124852 names as they appear in the symbol tables almost (more on this is in a
124855 breakpoint on the resulting prototype, in this case "f(unsigned int)".
124939 This obviously no longer makes sense to have, since we now depend on
124953 Reason for the failures was, that on a 32 bit machine the maximum
124971 running on targets with 64 bit. For this, the compiled tests evaluate the
125003 the assignment is done dynamically, depending on the kind of machine one
125004 is on. Sadly, just changing this line to
125017 on the other hand fail to compile with gfortran (9.4.0) as the compiler
125025 This works on all 3 compilers as expected.
125068 observable, but it doesn't have to be, as it does not depend on the
125188 - Add a script syscalls/gen-header.py, based on syscalls/arm-linux.py.
125206 Tested on x86_64-linux.
125216 Tested on x86_64-linux.
125221 When execute the following command on LoongArch:
125241 gdbarch method on LoongArch.
125248 displayed. This issue was also discussed on the mailing list here:
125307 Tested on x86_64-linux with native and unix/-m32.
125314 When running test-case gdb.reverse/pipe-reverse.exp on openSUSE Tumbleweed,
125325 The current glibc on Tumbleweed is 2.35, which contains commit
125332 Tested on x86_64-linux, specifically on:
125348 When running test-case gdb.reverse/pipe-reverse.exp on openSUSE Tumbleweed,
125361 The current glibc on Tumbleweed is 2.35, which contains commit
125370 Tested on x86_64-linux, specifically on:
125416 19", and the second matching triggers on that. Consequently, wait_for no
125423 Tested on x86_64-linux with make targets check and check-read1.
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:
125475 warning: Error detected on fd 11^M
125495 Tested on x86_64-linux, by manually triggering the error in
125500 [gdb/testsuite] Fix gdb.ada/catch_ex_std.exp with remote-gdbserver-on-localhost
125501 When running test-case gdb.ada/catch_ex_std.exp on target board
125502 remote-gdbserver-on-localhost, I run into:
125516 Tested on x86_64-linux with native and target board
125517 remote-gdbserver-on-localhost.
125527 FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: \
125539 Tested on x86_64-linux with native, check-read1 and check-readmore.
125586 multi-character input sequences. I have raised this issue on the
125649 The test has been run on a Power 10 system and and Intel x86_64 system.
125676 constructor on 'breakpoint' itself. The subclasses and callers are
125729 This changes print_recreate_thread to be a method on breakpoint. This
125736 The break point after the stepi on Intel is the entry point of the user
125754 The bp-permanent.exp and kill-after-signal tests run fine on PowerPC with an
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
125792 user signal handler. With the patch below, the tests run without errors on both
125892 to a GDBserver on startup, and therefore pushes a remote target on the
125896 Rewrite it to use scoped_mock_context, so it doesn't depend on the
125976 on a 32-bit host, so we may as well make targmatch.h include cris.
126010 gdb: Workaround stringop-overread warning in debuginfod-support.c on s390x
126011 For some reason g++ 11.2.1 on s390x produces a spurious warning for
126023 DIAGNOSTIC_IGNORE_STRINGOP_OVERREAD on s390x.
126074 on purpose, via set_desired_process, exactly to expose code relying on
126108 gdb/remote: send qSymbol to all inferiors on startup
126113 process on initial connection, and this would send a qSymbol for only
126116 Change it to iterate on all the target's inferiors and send a qSymbol
126119 I tested this by changing gdbserver to spawn two processes on startup:
126135 starting manually two inferiors on an "extended-remote" connection,
126166 gdb/remote: iterate on pspace inferiors in remote_new_objfile
126172 …(gdb) PASS: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=child: break cond on t…
126188 -ex "set detach-on-fork off" \
126271 - After doing the "continue" on inferior 1, the remote target gives us
126297 process on the remote side (it has exited, that's why it's being
126299 process that doesn't exist on the remote side. remote_check_symbols
126327 To fix this, make remote_new_objfile iterate on all inferiors bound to
126337 As before, on sufficiently old glibc this conflicts with a global
126383 NEWS: Add a note for TLS support on FreeBSD/arm and FreeBSD/Aarch64.
126385 Read the tpidr register from NT_ARM_TLS on Linux.
126387 gdbserver: Read the tpidr register from NT_ARM_TLS on Linux.
126389 Read the tpidr register from NT_ARM_TLS core dump notes on Linux Aarch64.
126394 Support TLS variables on FreeBSD/Aarch64.
126397 Read the tpidr register from NT_ARM_TLS core dump notes on FreeBSD/Aarch64.
126404 Support TLS variables on FreeBSD/arm.
126407 Read the tpidruro register from NT_ARM_TLS core dump notes on FreeBSD/arm.
126485 auto-connect-native-target off", to prevent testcases from mistakenly
126490 connection everywhere except on targets that do reload on run (e.g.,
126498 While working on this patch:
126510 Unless 'set debug infrun on' is in effect, then there should be no
126588 …exp: inferior-tty=separate: mi=separate: force-fail=0: breakpoint hit reported on console (timeout)
126596 look for some expected output on each, however, as there is no CLI
126662 …exp: inferior-tty=separate: mi=separate: force-fail=0: breakpoint hit reported on console (timeout)
126691 Now, once we have seen the expected pattern on the gdbserver spawn-id,
126715 Tested on x86_64-linux, with gcc 7.5.0, gcc 12.1 and clang 12.0.1.
126774 - GDB build on RHEL 7:
126832 Tested on x86_64-linux with native, check-read1 and check-readmore.
126967 sublcass based on bptype. This is important due to the somewhat
127002 which can't be virtual methods on breakpoint -- they are only used
127057 old one. I tested both the new and old versions of gdb on both new
127063 Regression tested on x86-64 Fedora 34.
127101 …(gdb) PASS: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
127106 …(gdb) PASS: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
127111 …(gdb) PASS: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
127114 …(gdb) FAIL: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
127128 …a-directory testsuite/outputs/gdb.base/foll-fork/foll-fork -ex "set detach-on-fork off" -ex start …
127149 [infrun] proceed: start: resuming threads, all-stop-on-top-of-non-stop
127155 [infrun] proceed: end: resuming threads, all-stop-on-top-of-non-stop
127217 after the loop (I presume the current thread on entry is always supposed
127278 Fix libinproctrace.so build on PPC
127280 on PPC:
127323 Regression tested on x86-64 Fedora 34.
127365 /* Return a view on this block's ranges. */
127415 libctf: impose an ordering on conflicting types
127430 Adjust things to use the same strategy used to sort types on the output:
127432 appeared earlier on the link line (and if there is somehow still a tie,
127498 call on the returned array_view.
127533 Replace with an equivalent method on struct block.
127540 Replace with equivalent methods on blockrange.
127601 For example, on aarch64 a long type is 8 bytes, whereas a long type is
127605 FAIL: gdb.base/parse_number.exp: lang=auto: ptype 0xffffffffffffffff
127664 * Adjusts the expected values and types based on the sizes of long
127677 I broke the gdbserver build on x86-64 Windows a little while back.
127690 Create pseudo sections for NT_ARM_TLS notes on FreeBSD.
127720 gdb/arm: Add support for multiple stack pointers on Cortex-M
127737 arm_m_exception_cache() and relies on the definition with the XML
127743 While working on adding support for Non-secure/Secure modes unwinding,
127768 Tested on x86_64 ubuntu 20.04.4 and openSUSE Tumbleweed(VERSION_ID="20220425").
127816 The patch has been run on both Power 10 and Power 9 to verify the ISA
127817 2.06 test case runs on both platforms without errors. The ISA 3.1 test
127818 runs without errors on Power 10 and is skipped as expected on Power 9.
127906 The patch has been tested on Power 10, Power 8 LE and Power 8 BE.
127911 This fixes build breakage using clang with libc++ on FreeBSD where
128010 Tested on x86_64-linux-gnu.
128035 The problem seems to be that calling setbuf on terminal file handles
128080 - Connect to a remote target with inferior 2, continue and stop on the
128083 continue and (expect to) stop on the all_started function
128097 for (auto *target : all_non_exited_process_targets ())
128115 want to ignore the "no resumed" and carry on.
128117 But I don't really see why we need to update the thread list on the
128170 linux_process_target::mourn on failure (before calling error). But this
128222 rely on rl_deprep_terminal to print the trailing '\n'. However,
128224 on. If the user has turned this feature off, no '\n' is printed.
128226 "quit" when bracketed paste mode is on, and "quit\n" when bracketed
128245 readline, and they have bracketed paste mode on, then they will see
128246 the 'quit' sting printed on the line below the prompt, like this:
128347 '--with-system-readline' flag, and build GDB on a system that uses
128361 (gdb) FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: no threads left
128367 …(gdb) FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left (the progr…
128432 definitely built and tested the series on Windows, and I didn't change
128433 it before pushing. Something must have gone wrong on the Windows
128491 at different addresses the test runs correctly on Powerpc.
128499 the same effect on PowerPC but you must use a value much larger than
128503 defined to get the lib2_spacer function on Intel and Powerpc.
128521 The backtrace on Intel with the good libraries is:
128534 is wrong on Intel. This is due to the fact that the ARRAY_SIZE caused
128539 So without the patch the backtrace on PowerPC looks like:
128557 Now with the patch the backtrace for the bad library on PowerPC looks
128565 And the backtrace for the good libraries on PowerPC looks like:
128577 The issue then is on Power where the ARRAY_SIZE of 1 versus 8192 is not
128583 default size of the data section allocated by the dynamic linker on
128585 section on Intel to have to move when the large array is defined.
128587 Note on PowerPC, if you make ARRAY_SIZE big enough, then you will cause
128600 up in the binary for the correct or incorrect library on Intel or PowerPC.
128601 With the patch, RIGHT gets defined as originally intended for the test on
128603 binaries on both architectures changing the other function addresses as
128604 intended thus causing the test work as intended on PowerPC.
128619 follow the code with the standard on the side when we use the same
128656 Internally we noticed that some tests would fail like so on Windows:
128683 Support for the `p' packet is auto-detected, currently unknown.
128696 Support for the `X' packet is auto-detected, currently unknown.
128742 Regression-tested on Ubuntu 18.04. Built-tested on Windows, and I also
128769 Tested on x86_64 openSUSE Tumbleweed(VERSION_ID="20220413").
128786 This GDB supports auto-downloading debuginfo from the following URLs:
128795 This GDB supports auto-downloading debuginfo from the following URLs:
128868 Tested on x86_64-gnu-linux
128875 This turns symbol_symtab into a method on symbol. It also replaces
128879 This turns symbol_arch into a method on symbol.
128882 This turns symbol_objfile into a method on symbol.
129088 Regression tested on x86-64 Fedora 34.
129125 As a consequence, the list of selftest effectively executed depends on
129142 architectures are registered and we do not have a dependency on the
129145 Tested on x86_64-linux
129223 the following patches, I would need to have finer grained control on
129229 used to refer to that directory entry (based on the DWARF version), and
129281 Tested on x86-64 Fedora 34. I also did a mingw cross build.
129296 Regression tested on x86-64 Fedora 34.
129314 does not place a breakpoint on the "Ada main", but on some symbol in a
129380 Regression tested on x86_64 openSUSE Tumbleweed(VERSION_ID="20220413").
129506 Tested on x86_64-linux with native and unix/-m32.
129526 Make breakpoint pending on future shared library load? (y or [n]) n^M
129533 Make breakpoint pending on future shared library load? (y or [n]) n^M
129546 Tested on x86_64-linux.
129605 stored on a side map, we can store it directly in the process
129664 same on the read side, in read_inferior_memory.
129687 indexer, I found one regression on RISC-V. The test in question uses
129702 Use GetThreadDescription on Windows
129713 Set the worker thread name on Windows
129715 is a change to gdb's behavior on the host. It changes gdb's thread
129716 pool to try to set the thread name on Windows, if SetThreadDescription
129770 gdb.dwarf2/calling-convention.exp making the test sometimes fail on his
129798 Tested on x86_64-gnu-linux, using
129822 Fix regression on Windows with WOW64
129919 Currently, the configure check for std::thread relies on pthreads
129970 Tested on x86_64-linux with target boards unix and unix/-m32.
130043 binutils: enable PE on 32bit haiku build
130138 main one, so now I just call arrange_linetable on the main subfile's
130215 instead, depending on the C++ version.
130306 In our ongoing example, this reduces the scanning time on gdb itself
130373 copied my built gdb to /tmp, so that each test would be done on the
130380 This patch is the baseline and on one machine came in at 1.598869 wall
130450 While working on this, I noticed that whether a DIE is interesting is
130457 the results on the abbrev. These combine to speed up the new indexer.
130484 Based on this, the new implementation doesn't try to store any DIEs,
130485 but instead just re-scans them on demand. In order to do this,
130587 This patch implements this idea. I built it on a thread-less host
130610 Tested on x86_64-linux.
130703 re-instating coordinates first thing on every iteration; note that the
130704 file can't change from what was previously pushed on the scrubber's
130792 Replace them with equivalent methods on the appropriate objects.
130809 When working on the files I noted that there was no actual test for a
130901 directly tell me what is going on. Note, that when debugging a binary
130921 depending on the compiler flag.
131083 Tested on x86_64-linux.
131109 Work around this in the test-case by breaking on bar_label instead.
131111 Tested on x86_64-linux with target boards unix, unix/-m32, unix/-fPIE/-pie and
131130 For better packing on 64-bit hosts.
131227 Compilers don't error out on such shifts, at best they warn, so I
131340 Debug info for function in Windows PE binary on wrong instruction
131465 This patch fixes PR22497 and PR26373 on GDB side.
131550 The history of this patch can be seen on the mailing list here:
131633 - rewrite the regexp such that each annotation is on a single line,
131638 Tested on x86_64-linux.
131797 This commit is focused on the minimal changes needed to manage the
131810 of default_groups in gdb/reggroups.c for details on this.
131846 on csky, we previously never added the 'vector' group. Now, as a
131980 While working on a different patch, I triggered an assertion from the
132042 So what's going on now? The next problem is that the call_readline
132223 working on, and I thought it would make sense to send it separately.
132225 Regression tested on x86-64 Fedora 34.
132247 This was based on the comment on value::contents, which suggest that
132255 entirely optimized out, for example on exit of
132261 value_contents_all_raw on the input value, which caused contents to be
132263 value_copy did not have its contents allocated on entry, but had it
132264 allocated on exit. The result value had it allocated on exit. And that
132276 allocated, it depends on how they were created) and adjust
132288 input value would still be without allocated contents on exit). But
132320 Testcase for the simulator is included. It has a trivial dependency on the
132334 That seemed better than using 1UL for the constant (on a 32bit host unsigned
132343 * v850/simops.c (v850_bins): Avoid undefined behavior on left shift.
132349 frame unwinder for signal on LoongArch.
132430 feature is not included as an XML file on GDB's side because it is only
132441 While working on the disassembler I was getting frustrated. Every
132454 files that depend on disasm.h is much reduced.
132476 Regression tested on x86-64 Fedora 34.
132483 internal AdaCore test suite on Windows, which FWIW does include some
132510 schedule-multiple is on. The child exits, which un-freezes the parent
132525 that the parent loops on that we set only after we confirmed the exit of
132537 I got failures like this once on a CI:
132557 not the hexadecimal address is printed (roughly) depends on whether the
132558 current PC is at the beginning of a line. So depending on where thread
132565 Note that for test "frame 5", we are showing a pthread frame (on my
132567 can rely on. In that case, it's almost certain that we are not at the
132618 …fork-other-thread.exp: fork_func=fork: target-non-stop=auto: non-stop=off: displaced-stepping=auto…
132677 …FAIL: gdb.threads/forking-threads-plus-breakpoint.exp: cond_bp_target=0: detach_on_fork=on: displa…
132723 …fork-other-thread.exp: fork_func=vfork: target-non-stop=on: non-stop=off: displaced-stepping=auto:…
132817 gdb: fix handling of vfork by multi-threaded program (follow-fork-mode=parent, detach-on-fork=on)
132824 detach-on-fork=on case, because it would be too much to chew at once to
132882 target-non-stop on/off, follow-fork-mode parent/child, detach-on-fork
132883 on/off, schedule-multiple on/off), but for this patch I restrict the
132884 scope to follow-fork-mode=parent, detach-on-fork=on. That's the
132894 For non-stop targets (the default on Linux native), this is what
132949 to make sure this doesn't cause regressions on its own, and to keep the
132968 currently not reset on inferior exec or exit. I could imagine that if a
132976 destroyed on exec or exit, it could be worse now since we could try to
133039 Tested on x86_64-gnu-linux.
133111 the compiler gave information on where the prologue ends, we should use
133112 this information and not try to rely on architecture dependent logic to
133115 The testsuite have been executed using this patch on GNU/Linux x86_64.
133143 Tested on x86_64-linux, no regression observed.
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
133169 I caught this assert by trying the CTF symbol reader on a library I
133250 converted to be methods on this object.
133442 (generally directives on the new symbol should win) and is relied upon by glibc
133498 later on. The problem is that by the time we print the arguments out
133504 on this, to add additional styling, in later commits.
133574 In this commit I have focused on objdump. The changes to GDB at this
133585 colors applied (if the option is on).
133666 (reproduced on Fedora 34).
133668 Tested on x86_64-linux, specifically openSUSE Leap 15.3 and Fedora 34.
133695 on to the dwarf expression evaluator. This rank will only be used in
133886 not depend on any file listed in ALLDEPFILES.
133904 depend on all the files in ALLDEPFILES. With this change the TAGS
133959 whole delta on the next window.
134002 gdb/tui: relax restrictions on window max height and width
134074 Something weird has gone on, gdb has overlapped the cmd window with
134079 So, what's going on?
134191 This commit allows this (details on how are below). After this
134203 can fit on the screen.
134328 the window size based on the fixed size.
134363 Well, it turns on, that due to the implementations of these things,
134380 This commit adds 'set debug tui on|off' and 'show debug tui'. This
134390 If tui debug is not turned on, then there should be no user visible
134398 (gdb) set logging debugredirect on
134399 (gdb) set logging enable on
134447 really needed for winheight, as there are always multiple windows on
134462 be changed to handle either height, or width, based on whether we are
134564 Regen bfd po/SRC-POTFILES.in
134904 …/home/simark/src/binutils-gdb/gdb/ctfread.c:1545:31: runtime error: member call on misaligned addr…
134926 With this patch, this passes cleanly on my system:
134939 This patch removes gdb's dbx mode. Regression tested on x86-64 Fedora
134955 on Tiger Lake.
134959 gdb/linux-nat: remove check based on current_inferior in linux_handle_extended_wait
135230 conditional on having both armv8.5-a and +rng, but only +rng should be
135267 gdb: test vfork + follow-fork-mode=parent + detach-on-fork=off
135281 procfs.c doesn't compile on Solaris:
135294 Tested on amd64-pc-solaris2.11, sparcv9-sun-solaris2.11.
135324 characters on the right instead of shifting them. It also doesn't
135332 I found that this web page [2] gave some good clues on the expected
135344 Only allow QUIT on the main thread
135349 new code. This patch arranges for the QUIT macro to only work on the
135380 Fix for MUL instruction on the v850
135575 cases are all handled by infrun's blanket ban on paging, and so can be
135603 on targets. The second inferior below sits on top of a remote target.
135609 (gdb) maint set target-non-stop on
135642 Running the same scenario with "debug infrun on" reveals more details.
135712 If target-non-stop is not turned on at the beginning, the same bug
135715 # Same setup as above, without 'maint set target-non-stop on'.
135734 Regression-tested on X86-64 Linux.
135843 any comparisons based on that pointer are undefined.
135867 twice on addr2line's command line would resolve the function for the 2nd
136145 on-the-fly at the time of transfer. In this case gdb wrongly prints
136235 The problem is that the test relies on sending two commands to GDB in
136239 act on the incoming commands.
136241 Usually, both commands are echoed in full before GDB acts on the first
136265 foreign-endian CTF dicts on the input and endian-flipping them: dicts
136271 endian code paths when you run make check on a big-endian machine.
136275 To improve on this, add a new environment variable,
136378 This is a little fiddly. We relied on compiler assistance for data
136412 fail whenever the compiler emits anything on stderr, even if it
136419 names, but right now the linker doesn't link CTF on any such platforms
136423 leak sanitizers etc even if those spray warnings on simple CTF
136436 - Rebase on master, fix a few more issues that appeared.
136456 thinking to get something that behaves correctly on both. And that's if
136539 are better done the other way around: The 2nd doesn't depend on what the
136601 (introduced by c06ae4f232e6) looks more usual on the surface in that it
136649 should return early as well on failure.
136699 Add support for hardware breakpoints/watchpoints on FreeBSD/Aarch64.
136715 Note that this method is only invoked on systems supporting LWP
136717 supported on older kernels that do not support LWP events.
136763 is only defined on Linux. In addition, pass the ptid on to
136769 x86-fbsd-nat: Copy debug register state on fork.
136771 per-process debug state from the parent to the child on fork.
136784 code. The ptrace request has been present on FreeBSD x86
136849 Notes on the implementation:
136852 the type of the PyObject being worked on. Prior to this commit all
137029 I notice this happening on a current Fedora Rawhide install with the
137154 and, based on the type being pulled from the register, would extract
137169 And so, based on all the above draw backs, I rejected this first
137175 is extracted from the value contents (based on type). This is similar
137196 register. Obviously, that will only work on a x86 target, so I've
137204 depend on systemtap/gcc versions), then again, the tests are skipped.
137210 I found that on a Fedora 35 install, with these packages installed, I
137223 I have kicked the can down the road a bit on this. In the function
137232 generate the agent expression to place the xmm register on the stack,
137244 on the agent expression evaluation stack. Solving this is clearly
137246 problem. I'd like to get feedback on whether my approach to solving
137275 Run black on the file.
137293 reasons, depending on the function. The issue happens because
137322 - if the user specifies GDB on the command line, then by default,
137628 out-of-scope watchpoint is deleted. This fails on some aarch64
137771 Releases some obstack memory on an error path.
137796 Error: dl failure on line 894
137903 segfault on not finding section. Wrap overlong lines.
137920 * po/SRC-POTFILES.in: Regenerate.
137948 x86: unify CPU flag on/off processing
138051 escape sequence to leave bracketed paste mode is emitted on the same
138106 In this commit I change GDB to print the 'quit' string on the line
138107 after the prompt, but only when bracketed paste mode is on. This
138133 However, while working on this, I looked at how this code could
138156 converted to a wide or wide-wide string depending on context.
138177 The last two tests in gdb.base/ending-run.exp case fail on Powerpc when the
138197 I checked the behavior on Powerpc to see if this is typical.
138198 I ran gdb on the following simple program as shown below.
138236 output on Powerpc without the needed debug-info files installed.
138238 The patch has been tested on a Power 10 system and an Intel
138239 64-bit system. No additional regression failures were seen on
138254 inconsistently as mentioned on gdb-patches mailing list here:
138262 2 is selected using '-thread-select 2' command on GDB/MI terminal:
138268 and on CLI terminal we get the notification (as expected):
138275 using 'thread-select --thread 1 1' command on GDB/MI terminal
138282 but no notification is printed on CLI terminal, despite the fact
138295 notification to be sent on MI channel. This is because by the time
138304 With this change, all gdb.mi tests pass, tested on x86_64-linux.
138548 The flags for the "HSA" OS ABI are properly versioned and documented on
138624 The specific AMDGCN models added here are a bit arbitrary, based on
138635 The flags for the "HSA" OS ABI are properly versioned and documented on
138683 rely on inferior I/O. However, when testing against gdbserver using
138878 paste errors) has 'on MI' on their name, when they were actually
138879 checking CLI output. For these test I changed the name to use 'on
138900 When execute the following command on LoongArch:
138931 This commit is based on work linked too from this mailing list thread:
139034 big issue. However, the original patch relied on being able to
139134 definition on gdbarch-components.py, setting the 'invalid' field to
139224 With the patch, gdb.cp/non-trivial-retval.exp has full passes on
139225 aarch64-linux and armhf-linux on Ubuntu 20.04/18.04.
139249 depending on cpu, such as mftb which has pre- and post-power4
139297 gdb finds the local (x86-64) libraries. This is not ideal, but on the
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]"
139396 I noticed that 'progress' is a method on ui-out, but it seems to me
139399 on the meter itself.
139417 Tested on Linux-x86_64, native and gdbserver.
139424 Re-add zombie leader on exit, gdbserver/linux
139448 Re-add zombie leader on exit, gdb/linux
139653 Turning on debug output in gdbserver leads to an assertion failure if
139735 toplevel: Makefile.def: Make configure-sim depend on all-readline
139737 libreadline-dev installed on the build system, won't
139755 The sim dependency on readline is apparently (nominally)
139760 * Makefile.def (dependencies): Make configure-sim depend on
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
139806 if no auto-load script is otherwise found the search will be
139809 This helps gdb locate auto-load scripts when debuginfo files do not have
139936 This property should only be read on types for which Type.is_scalar is
139955 Following on from the previous commit, where the -add-inferior command
140062 While working on another patch, I noticed that Ada integer literals
140116 handling this case from gdb, on the theory that it is hard to figure
140126 encoding failure on PPC when running a test that tries to read
140132 relies on whatever version of Unicode is used by the host Python,
140185 levels of up to the MIPSr5 ISA and a machine instruction on its own
140263 view on the contents. They both take a non-const value, that's a
140311 Regression tested on x86-64 Fedora 34.
140524 This request is present on all modern *BSD/i386 systems (those
140548 This silences warnings on recent FreeBSD/amd64 kernels due to not
140682 … TESTS="gdb.base/attach-pie-noexec.exp" RUNTESTFLAGS="--target_board=remote-gdbserver-on-localhost"
140700 Running mi-exec-run.exp on native-extended-gdbserver/-m{32,64}
140731 # and so on
140797 Also, while working on this, I noticed that gdb will print the decimal
140805 that's assigned based on the enumeration type.
140854 gdb_is_target_remote both rely on gdb_is_target_1, which actually
140866 the test suite throws several ERRORs on native-gdbserver/-m{32,64},
140869 [on native-extended-gdbserver/-m64]
140879 This patch skips these tests when running on non-native targets.
140883 Further correct the handling of long pathnames on Windows hosts.
140886 characters on Windows hosts.
140906 on a machine with a pre-release version of glib-2.34 installed:
140987 Print MI prompt on interrupted command
141028 prompt. Regression tested on x86-64 Fedora 34.
141053 riscv_parse_prefixed_ext call, a "while" loop on riscv_parse_subset
141184 on first, it happens to be the remote inferior.
141214 for me on Ubuntu 20.04 amd64.
141239 - Read and ignore such messages (counting on the next exception message
141251 mappings' output") has broken test gdb.base/info-proc.exp on Linux,
141264 The test passes on FreeBSD, because the test looks for four hex numbers
141269 I suggest fixing it on Linux by moving the flags column to the same
141294 for (a non-NULL terminated view on a string). No changes in behavior
141493 * Testcases for most CSRs added on the Privileged
141573 ptrace on FreeBSD cannot be used against running processes and instead
141575 the threads were running (for example when using schedule-multiple=on
141672 Enable async mode on supported targets in target_resume.
141937 Tested on Linux-x86_64, no regression observed.
141949 code will typically wait4() a second time on the same process that was
141955 WNOHANG instead of outright deleting the call. However, tests on the
142034 Simple int to bool conversion on callback_handler_installed in
142077 * peicode.h (pe_ILF_make_a_symbol_reloc): Don't segfault on
142087 being 32 on a 32-bit object or 64 on a 64-bit object. That then
142155 There was an omission on 3e6dc39ed7a8 "sim/testsuite: Set
142199 returned, and so on. For this reason, it is unsafe for GDB to try to do
142200 the following operations on a function with marked with DW_CC_nocall:
142206 This patch ensures that if a command which relies on GDB's knowledge of
142207 the target's calling convention is used on a function marked nocall, GDB
142217 Tested on x86_64-Linux, with no regression observed.
142234 Tested on x86_64-linux.
142313 passing on to the simulated program) to remove a leading
142417 depending on different-valued configure options, like
142418 --enable-sim-hardware[=off|=on]. To avoid failures in
142459 cris*-*-elf, where testing had until then relied on
142505 tests, or that its use must be gated on $global_cc_works !=
142511 .exp files without gating on $global_cc_works != 0.
142547 on a consistency error when trying to allocate a memory
142560 microblaze: fix fsqrt collicion to build on glibc-2.35
142600 that relies on them.
142608 set style disassembler enabled on|off
142615 register names such as r9d and r8d (on x86-64) was incorrect.
142629 to close the door on a user overriding this function to provide
142641 precise colors will depend on which instructions are in the
142714 make relro work on powerpc can disappear.
142736 size from 322208 to 2099872 bytes. Fixing this on x86 will require
142743 * ldexp.c (fold_segment_align): Set relropagesize depending on
142754 There are constraints on layout of binaries to meet demand paging and
142762 data (RW), the data segment must start on a different page to the
142766 pages. Demand paging would require the image on disk to be 64k+1k
142796 MAXPAGESIZE on x86 is for reasons other than the demand paging and
142801 Always end the relro segment on a MAXPAGESIZE boundary, except for
142905 process these dies and does not support 'print' or 'ptype' commands on
142938 with line numbers marked on the left:
143019 One test that relies on the output of 'maint info jit' was updated to
143059 It also allows saving one extra fork every time we start debugging on
143088 going on during GDB's stepping. I added some extra infrun debug print
143128 Test --only-keep-debug on ELF relocatables
143150 riscv_update_subset_version, and stop reporting warnings on
143176 I have no info on the format of a "SUNPRO C++ Namespace" stab, so am
143177 relying on the previous code being correct in parsing these stabs.
143202 Unless 'set debug index-cache on' is used, there should be no visible
143211 Tested on glibc 2.35 build with GCC 11.2 and -Os.
143255 While working on function calls, I realized that the thread_fsm member
143274 Tested on x86_64-linux with no regression observed.
143281 This commit should fix PR gdb/28711. What's actually going on is
143297 allow glibc to perform buffering on the FILE object being used.
143317 going on I think I would likely need to dive into kernel code, which
143347 on the input stream, drop out of the select, and call back into
143383 internal read buffer, which, on my machine, is 1024 characters.
143411 that is the first command is 8 characters plus a newline, then, on the
143445 Fix for using named pipes on Windows
143463 supported on a tty, this lseek call fails, this results in the ESPIPE,
143474 issue, the buffered input would now only be on the input stream, the
143526 I'm not completely sure what's going on here, but it appears that the
143527 kernel on the virtual machine is delivering the input to glibc slower
143528 than I see on my real hardware; glibc asks for 1024 bytes, but only
143533 If I run this exact example on my real hardware then the first command
143588 as thread and inferior context switches, on the CLI. This is used
143611 Added inferior 2 on connection 1 (native)
143640 (gdb) set suppress-cli-notifications on
143644 Added inferior 2 on connection 1 (native)
143653 events on the CLI should be suppressed.
143656 command to turn the flag off/on.
143942 last_filetab field to m_last_filetab as well (it's only used on
144015 matter, since we should work toward removing dependencies on these
144340 tlbr, tlbwi, tlbwr): Enable on *r6 models.
144453 arm-riscix. Those targets weren't on the obsolete list but they are
144505 Regression tested on x86-64 Fedora 34.
144565 Executing on target: kill -9 16622 (timeout = 300)
144634 Supporting -static-pie on PowerPC64 requires the linker to properly
144636 absolute symbol. I've been slow to fix the linker on powerpc because
144728 While working on the fix for PR cli/28665 (see previous couple of
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
144752 While working on the previous commit to fix PR cli/28665, I noticed
144753 that the 'edit' command would suffer from the same problem. That is,
144756 (gdb) edit task 123
144758 would cause GDB to break. For a full explanation of what's going on
144846 While the first version of this patch was on the mailing list, a
144903 'startswith' on the nullptr, which is undefined behaviour.
144908 This patch came about while I was working on fixes for PR cli/28665
144924 gdb: update the comment on string_to_event_location
144925 The comment on string_to_event_location is (I believe) out of date.
144985 When trying to use 'record btrace' on a system that does not support it,
144997 on objfile created by JIT reader crashes GDB.
145059 thought I'd run clang-tidy with this diagnostic on all the files (that I
145089 of XXXX over XXXX.NUMBER for info symbol on gfortran symbols.
145138 Re: PR28827, assertion building LLVM 9 on powerpc64le-linux-gnu
145157 i386-fbsd-tdep.c and amd64-fbsd-tdep.c failed to build on my x86-64
145174 Re: PR28827, assertion building LLVM 9 on powerpc64le-linux-gnu
145176 on offset used in the current iteration, and if we're fudging the
145199 * objcopy.c (setup_section): Act on make_nobits after calling
145208 gdb: fix ppc-sysv-tdep.c build on 32-bit platforms
145209 The previous code triggered the following error on an i386 host:
145241 While here, rework the probing of PT_GETXMMREGS on FreeBSD/i386.
145257 the signal frame as is done on several other FreeBSD arches. This
145260 registers stored as 16-bit values on amd64.
145262 While signal frames on FreeBSD do contain floating point/XSAVE state,
145272 Use register maps for gp regsets on FreeBSD/x86 core dumps.
145291 handling x86 segment register values stored in 16-bit slots on
145338 Build on x86_64-linux with clang 13.0.0.
145353 I added rules for the kinds of files I edit most often, but more can be
145381 on R_PPC64_TOC isn't local.
145388 binary, and symbols on these expressions cannot be overridden. Make
145398 PR28827, assertion building LLVM 9 on powerpc64le-linux-gnu
145428 (ppc64_elf_size_stubs): Iterate on stub_changed too.
145479 …==888645==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020000c52af at pc 0x7f711b23…
145656 So, based on this, the current use of data_section_offset /
145683 The enable_btrace target method takes a ptid_t to identify the thread on
145697 the xfer request later on, remote_target::xfer_partial() again sets the
145702 enable tracing on a newly created thread inside a newly created process
145814 cannot be introduced. Instead, all callers must use the method on the
145824 This changes all existing calls to wrap_here to call the method on the
145852 gdb/python: improve the auto help text for gdb.Parameter
145869 val = "on"
145892 val = "on"
146163 of the values coming from the enum array. This invariant is relied on
146202 However, this won't actually work, because the language is captured on
146213 bfd: Make bfd.stamp depend on source bfd.texi
146214 Make bfd.stamp depend on source bfd.texi to avoid regenerating
146219 * doc/local.mk (%D%/bfd.stamp): Depend on $(srcdir)/%D%/bfd.texi.
146258 Tested on x86_64-Linux.
146271 gdb_stdlog based on a debug flag. It seems better to me to simply
146302 Fix a probem building the binutils on SPARC/amd64
146354 gdb/doc: improve description for Window.click on Python TUI windows
146375 Tested on x86-64 Fedora 34. I'm checking this in.
146617 (gdb) set print array-indexes on
146684 Amend existing test cases accordingly that rely on the current incorrect
146743 here depending on SYMBOL_REFERENCES_LOCAL.
146916 it easier for a user to understand what is going on.
147030 (ppc_build_one_stub): Don't emit relative relocs on .branch_lt.
147086 Now that this lives on the stack, let's have it be a little less
147093 There's a single use on a generally infrequently taken code path. Put
147148 Buclaw, the D language maintainer, I trust him on that.
147176 PR28751 mbind2a / mbind2b regressions on powerpc*-linux
147270 (configure_deps): Depend on ../config/gcc-plugin.m4.
147361 + (configure_deps): Depend on ../config/gcc-plugin.m4.
147371 + (configure_deps): Depend on ../config/gcc-plugin.m4.
147434 + * configure.ac: Do not search for sbrk on Darwin.
147495 The ccache problem is that -W... options are reordered on the command
147506 In this attempt, instead of just relying on a compile to check if a
147546 While working on another patch I wanted to add some extra debug
147556 Re: gas: add visibility support using GNU syntax on XCOFF
147564 * xcofflink.c (xcoff_link_input_bfd): Don't segfault on NULL
147581 * scripttempl/elf.sc (.relr.dyn): Don't depend on $COMBRELOC.
147586 Tidy, and fix "FAIL: Build dt-relr-glibc-1b.so" on all non-x86
147633 Let's not rely on .init/.fini having relocs for the size sanity check.
147648 The test cases only failed on LoongArch. The default type of char
147649 is signed char on LoongArch, like x86-64. But when use gdb print
147650 command on LoongArch, the default type of char is unsigned char,
147699 The patch has been tested on Power 9, processor revesions 2.2 and 2.3. The
147700 patch has also been tested on Power 10. No regression test failures were
147757 Regression tested on x86-64 Fedora 34.
147766 which is provided by glibc with DT_RELR support, dependency on the shared
148054 maintenance set gnu-source-highlight enabled on|off
148202 gas: add visibility support using GNU syntax on XCOFF
148220 on several pseudo-ops: .globl, .weak, .extern and .comm.
148270 noticed none. I chose to remove "CU:" on the objdump tests instead of
148387 XCOFF: add support for TLS relocations on hidden symbols
148464 While testing on GNU/Hurd (i386) I noticed that GDB crashes when an
148487 Unfortunately, the GNU/Hurd target is still relying on the value of
148497 I've not run the full testsuite on GNU/Hurd as there appear to be lots
148521 to off or on.
148527 PASS: gdb.base/arrayidx.exp: set print array-indexes to on
148528 PASS: gdb.base/arrayidx.exp: print array with array-indexes on
148535 PASS: gdb.base/arrayidx.exp: set print array-indexes to on
148536 PASS: gdb.base/arrayidx.exp: show print array-indexes is on
148537 PASS: gdb.base/arrayidx.exp: print array with array-indexes on
148552 To prepare for DT_RELR implementation on these targets, extract
148562 .sizeof. symbols have been finalized on x86, __[start|stop]_SECNAME for
148623 Tested on x86_64-linux.
148638 Testeed on x86_64-linux both in a setup where the test fails to prepare
148656 Tested on x86_64-linux.
148671 Tested on x86_64-linux.
148684 Tested on x86_64-linux.
148696 Tested on x86_64-linux.
148708 Tested on x86_64-linux.
148723 Tested on x86_64-linux.
148742 Tested on x86_64-linux.
148755 Tested on x86_64-linux.
148768 Tested on x86_64-linux.
148780 Tested on x86_64-linux.
148790 Fix by using proc_with_prefix instead on plain proc to create logical
148793 Tested on x86_64-linux.
148815 Tested on x86_64-linux.
148830 Tested on x86_64-linux.
148842 Tested on x86_64-linux.
148855 Tested on x86_64-linux.
148868 Tested on x86_64-linux.
148880 clean the on flag set in this previous block, so moving it there makes
148883 Tested on x86_64-linux.
148889 developers test the auto-completion capabilities of GDB.
148955 Tested on x86_64-linux.
148967 Tested on x86_64-linux.
148986 Tested on x86_86-linux.
149002 Tested on x86_64-linux.
149017 Tested on x86_64-linux.
149026 DUPLICATE: gdb.base/del.exp: info break after removing break on main
149032 Tested on x86_64-linux.
149055 Tested on x86_64-linux.
149067 Tested on x86_64-linux.
149079 Tested on x86_64-linux.
149095 Tested on x86_64-linux.
149108 Tested on x86_64-linux.
149116 DUPLICATE: gdb.base/realname-expand.exp: set basenames-may-differ on
149126 Tested on x86_64-linux.
149163 Tested on x86_64-linux.
149182 Tested on x86_64-linux.
149195 Tested on x86_64-linux.
149210 * po/fr.po: Same.
149211 * po/ru.po: Same.
149212 * po/uk.po: Same.
149229 * po/fr.po: Same.
149230 * po/ru.po: Same.
149231 * po/uk.po: Same.
149248 Building on the previous commit, this makes use of a trailing @ to
149459 For testing I've build GDB on GNU/Hurd, and manually tested these
149497 'verbose' is on and when switching the "expected" language in auto
149516 check to PCLMULQDQ, AES, and GFNI insns"), base the check on opcode
149654 Tested on x86_64-pc-linux-gnu.
149770 better to me, both on the principle that this is an ordinary command,
149786 Regression tested on x86-64 Fedora 34.
149804 fail on x86-64 Linux, though. It's possible that maybe I'd have to
149807 Regression tested on x86-64 Fedora 32.
149826 Regression tested on x86-64 Fedora 34.
149872 on. However, in the meantime, adding the old gdb_stdout check back to
149875 Regression tested on x86-64 Fedora 34.
149880 Currently, on 32-bit and 64-bit ARM, it seems that ld generates p_align
149886 does not have to be reflected in the p_align value. If running on a 64K
149902 This means that on 4K kernels, we will start to do extra work for 64K
149911 It has been fixed in glibc 2.35. But linker output must work on existing
149916 align segments to the minimum page size or above, depending on system page
150097 Added inferior 2 on connection 1 (extended-remote localhost:2346)
150101 of the message. The 'on connection 1 [...]' part is unexpected.
150106 Tested on x86_64-linux with native-extende-gdbserver and unix boards.
150117 I tried building GDB on GNU/Hurd, and ran into this warning:
150126 gdb: fall back on sigpending + sigwait if sigtimedwait is not available
150131 The original patch was written for macOS, I assume on that target
150138 rebuild on GNU/Linux, I see the same warning that I see on GNU/Hurd.
150146 sigwait instead on sigtimedwait on GNU/Linux, I saw no regressions.
150167 202 | fprintf_unfiltered (_("on: Logging is enabled.\n"));
150171 Build and tested on x86_64-linux.
150224 $ gdb -q -batch -ex "set trace-commands on" \
150227 -ex "set logging on" \
150235 +set logging on
150251 +set logging on
150260 OTOH, it's explicit about whether boolean values are on or off.
150288 Tested on x86_64-linux.
150299 Simon and Tom pointed out that page-logging.exp failed on their
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.
150355 out */po/*.pot which we don't update frequently.
150582 Regression tested on x86-64 Fedora 34.
150689 Regression tested on x86-64 Fedora 34.
150738 The other properties this commit copies on clone (i.e. CWD and the
150745 inferior based on an existing one, they probably already propagate those
150748 Tested on x86_64-linux.
150857 Regression tested on x86-64 Fedora 64.
150959 is based on priv spec 1.9.1, but it seems unlikely that they implemented
151059 Notice that when debug printing is on we dereference
151076 gdb: on x86-64 non-trivial C++ objects are returned in memory
151079 this behaviour was observed on an x86-64 target.
151137 be found (on x86-64 targets anyway).
151152 A, actually contains the address of an instance of A (in this case on
151269 While working on another patch relating to how GDB manages threads
151341 about turning debug on and off, so I don't think there's any updates
151349 changed from 'Enables printf debugging output.' to 'When on, print
151358 set debug threads on|off
151373 debug sub-systems are turned on (especially things like `infrun` and
151438 on the upper half of %esp being zero), simply issue an error. While at
151465 Regression tested on x86-64 Fedora 34.
151482 Based on this, I'm removing puts_debug. I don't think it's useful.
151529 Tested on x86_64-linux.
151536 While working on another patch I ended up in a situation where I had
151555 While working on another patch relating to remote targets, I wanted to
151585 in infcmd.c. From here we call the ::attach method on the attach
151691 back on (see remote_target::async) we will mark the event token if
151720 After discussion on the mailing list:
151743 For testing I've been running test on x86-64/GNU Linux, and run with
151762 Tested on x86_64-pc-linux-gnu.
151823 The new gdbarch.sh approach will be to edit a Python file, rather than
151827 Documentation on the format will come in a subsequent patch.
151933 Tested on x86_64-linux.
151950 Leaving entries on mips_hi16_list from a previous pass over relocs
151954 Free mips_hi16_list entries on error exit.
151983 * mmo.c (mmo_get_symbols): Error on symbol name exceeding max length.
152102 Armv8.6-A, and so on.
152210 using binutils 2.37, we observed a failure that didn't show up on
152222 Using an unsigned int cast (to 32 bits) on a pointer difference (of
152223 possibly 64 bits) is wrong. Even though it will work on all real
152233 Run black 21.12b0 on gdb/, there is a single whitespace change. I will
152243 Run black 21.9b0 on gdb/ (this is the version currently mentioned on the
152316 loongarch32 build failure on 32-bit host
152330 loongarch64 build failure on 32-bit host
152337 Cast it to the correct size int, relying on normal integer promotions
152345 XCOFF C_STSYM test failure on 32-bit host
152346 This test was failing here and on another similar symbol:
152379 execute. So crashing on this failed assertions seems against the intent.
152401 When building gdb with on AArch64 with g++ 11.1.0 (and some preceding
152614 While working on a Python script, which was interacting with a remote
152646 What's going on is that in valarith.c, in value_subscript, for C like
152719 Regression-tested on X86-64 Linux using the native-gdbserver and
152731 gdb: make post_startup_inferior a virtual method on inf_ptrace_target
152732 While working on a later patch that required me to understand how GDB
152772 a protected, pure virtual function on inf_ptrace_target.
152787 turns on 'set debug target 1'. With this debug flag on, prior to this
152800 While working on another patch I had reason to look at
152821 Later on all the remaining targets (except mips) were converted to
152910 disassemblers do, not surprisingly, depend on features supplied from
152923 This was discussed on the mailing list in a couple of threads:
152946 Regression tested on x86-64 Fedora 34.
153008 Don't edit bogus sh_link on reading relocatable objects (Oracle fix)
153022 The comment on top of gdb/testsuite/boards/remote-stdio-gdbserver.exp says
153023 that user can specify path to gdbserver on remote system by setting
153058 * dwarf2.c (read_attribute_value): Return NULL on trying to read
153123 This unfortunately means that tests relying on runto_main won't emit a
153187 Tested on x86_64-linux with native and target board readnow, as well as
153207 Tested on x86_64-linux, with native and target board readnow.
153268 for the child, we can simply call detach_inferior on it.
153276 while stopping all threads, to present an all-stop stop on top of a
153348 "detach-on-fork on". follow_fork_inferior calls target_detach to detach
153375 allows iterating on only this inferior's threads and avoid further
153376 filtering on the thread's pid.
153383 filtering on the pid to the callers, when it is necessary.
153415 (gdb) show detach-on-fork
153416 Whether gdb will detach the child of a fork is on.
153485 without the fix applied on the native-gdbserver and
153509 Regression tested on x86-64 Fedora 34.
153523 This patch fixes the bug. Regression tested on x86-64 Fedora 34. I
153620 GDB compiled on a 32-bit arm target, with --enable-targets=all. Then
153691 Notice however, that the error message is always printed on a new line
153706 For me, I'm happy to accept this change, having the error on a line by
153726 Tested on Linux on PowerPC e500 and on QEMU PPC64le.
153818 Support AT_FXRNG and AT_KPRELOAD on FreeBSD.
153841 Regression tested on x86-64 Fedora 34.
153869 Tested on x86_64-linux.
153876 FAIL: gdb.tui/basic.exp: check main is where we expect on the screen
153878 while this is passing on x86_64.
153893 but on aarch64:
153908 on x86_64:
153914 and on aarch64 instead:
153922 entire main function on a single line, in order to force the compiler to use
153927 Tested on x86_64-linux and aarch64-linux.
154025 Tested on x86_64-linux, with target board unix/-m32 and unix/-m32/-fPIE/-pie.
154043 Tested on x86_64-linux.
154075 Tested on x86_64-linux.
154097 Error on ld output file name matching input file name
154102 * ldlang.c (open_output): Exit with error on output file matching
154117 The patch has been successfully tested on both PowerPC BE, Powerpc LE and
154134 - run later into a failure on a different test setup (which may be a setup
154150 - prevent the same type of problems in any new test-cases based on these
154152 Tested on x86_64-linux, with both gcc and clang.
154183 Tested on x86_64-linux, with both gcc and clang.
154298 These rules don't depend on the target compiler settings, so hoist
154312 We already turn these on in the configure script.
154325 be used on demand; this is an important property for the new DWARF
154337 execution time on my system goes from ~100sec to ~60sec.
154349 set index-cache enabled, set index-cache off, set index-cache on
154351 alias set index-cache on = set index-cache enabled on
154353 When on, enable the use of the index cache.
154355 (gdb) help set index-cache on
154356 … Warning: 'set index-cache on', an alias for the command 'set index-cache enabled', is deprecated.
154357 Use 'set index-cache enabled on'.
154359 set index-cache enabled, set index-cache off, set index-cache on
154361 alias set index-cache on = set index-cache enabled on
154363 When on, enable the use of the index cache.
154369 When on, enable the use of the index cache.
154370 (gdb) help set index-cache on
154371 … Warning: 'set index-cache on', an alias for the command 'set index-cache enabled', is deprecated.
154372 Use 'set index-cache enabled on'.
154375 When on, enable the use of the index cache.
154416 (most likely) because they rely on the chew & related tools. But
154519 least on libstdc++, appears to pick memmove when copying trivial data.
154525 std::copy_backward, depending on whether the destination is before the
154531 The order of parameters of the new copy function is based on std::copy
154661 then decrements the reference count on the remote_target object. This
154672 pages based on the GNU standard behavior of shipping info pages with the
154723 Listening on port 2346
154762 Tested on x86_64-linux with native and unix/-m32.
154828 Note that the "finish" function, on the other hand, does not
155082 This becomes useful with a follow-on patch to check that code follows
155290 in insn_type on branching instructions.
155327 passed -Wswitch on the command-line). There doesn't seem to be a way to
155357 Don't convert memory load to immediate load on __start_SECNAME and
155484 As defined on: https://systemd.io/COREDUMP_PACKAGE_METADATA/
155513 Tested on x86_64-linux.
155517 [gdb/testsuite] Fix gdb.arch/i386-pkru.exp on linux
155518 When running test-case gdb.arch/i386-pkru.exp on a machine with "Memory
155536 Tested on x86_64-linux.
155606 results in compilation errors on 64-bit PowerPC.
155611 The patch was tested on a Power 10 system. No compile errors were generated.
155622 * doc/local.mk: Give each man page target its missing dependency on
155654 aarch64: Make LOR registers conditional on +lor
155785 When running the gdb.python/py-arch.exp tests on a GDB built
155827 Tested on x86_64-linux.
155876 when running on a 32-bit ARM target, though I suspect running on any
155926 for the default architecture (the one selected by "auto") we _only_
156032 Or you can read the new 'connection' property on the gdb.Inferior
156039 though this is not always the case, depending on the connection type).
156284 Tested on x86_64-linux.
156305 Tested on x86_64-linux.
156317 Tested on x86_64-linux.
156333 Tested on x86_64-linux.
156338 We'll rely on the toolchain probing to determine whether each arch's
156401 Some of the core sim headers rely on the SIM_AC_OPTION_BITSIZE macro
156409 on any port-specific settings, so move it up to building as part of the
156492 Avoid use of TARGET_<syscall> defines and rely on the callback layers
156497 Avoid use of TARGET_<syscall> defines and rely on the callback layers
156565 Tested on x86_64-linux.
156570 Add missing $(EXEEXT) to dependencies on bits-gen. These are actually
156602 dir, the init function was no longer called on every test. However, it
156609 variables on a per-test basis which allows us to recollapse the sim_path
156652 Fix ifunc test fails on hppa*-*-*
156661 Skip static ifunc-using executable test on hppa*-*-*.
156750 Tested on x86_64-linux.
156771 commit is based on this patch which was never committed:
156787 The implementation provided here is based on this mailing list patch
156963 * po/BLD-POTFILES.in: Regenerate.
156964 * po/SRC-POTFILES.in: Regenerate.
156969 * po/fr.po; Updated French translation.
157000 While working on another patch I ended up in a situation where I had
157104 [gdb/cli] Add "set logging enabled", deprecate "set logging on/off"
157108 $ gdb -q -batch -ex "set trace-commands on" \
157111 -ex "set logging on" \
157116 +set logging on
157126 +set logging on
157137 - adding a corresponding new command "set logging enabled on/off"
157138 - making the commands "set logging on/off" deprecated aliases of the
157139 "set logging enabled on/off" command.
157144 Tested on x86_64-linux.
157176 syscall based on the behavior seen on a Linux PowerPC machine. That is,
157178 on Linux with other architectures, though, and it seems like a
157214 This is a problem because, later on in this same function, we
157227 This issue was reported on the mailing list here:
157254 such that efi images can be made natively on Linux.
157287 Any magic number is based on the Microsoft PE specification [1].
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.
157427 and caused errors on compilation.
157438 While working on target_waitstatus changes, I noticed a few places where
157514 A build error on x86_64 with x32 abi was reported here (
157528 si_addr_bnd in compat_siginfo_from_siginfo" doesn't compile on an x86_64 x32
157533 Tested on x86_64-linux.
157602 AFAIU, gdb is wrong. It assumes DW_FORM_line_strp is 8 bytes on the basis
157622 Tested on x86_64-linux, using native and target board dwarf64.exp.
157629 Tested on x86_64-linux.
157650 Tested on x86_64-linux.
157659 Tested on x86-64-linux.
157670 Tested on x86_64-linux.
157678 Tested on x86_64-linux.
157713 Tested on x86_64-linux.
157736 Tested on x86_64-linux.
157777 Fix intermittent failures on the H8, particularly H8/SX tests.
157778 The upstream GCC tester has showed spurious execution failures on the
157784 Because it only happened on the H8/SX variant I was able to zero in on
157839 we're excercising the enable_source_highlight=auto scenario. ]
157855 In the enable_source_highlight=auto scenario, this allows the build to skip
157861 Tested on x86_64-linux.
157920 Tested on x86_64-linux.
157952 Tested on x86_64-linux with target board unix/-m32.
157981 Tested on x86_64-linux.
158201 Instead of always using target_alias as a prefix on the name, use
158226 …data-directory data-directory -iex set height 0 -iex set width 0 -iex set auto-connect-native-targ…
158241 Listening on port 2346
158248 using the native target via "-iex set auto-connect-native-target off".
158423 Patch tested on Power 10 ppc64le GNU/Linux platform.
158428 This patch fixes eight test failures on PowerPC for the test
158436 Tested on Power 10 ppc64le-linux with no regressions.
158451 Patch tested on Power 10 ppc64le GNU/Linux, no duplicate tests reported,
158456 elf/x86: Issue an error on discarded output .plt section
158457 Issue an error, instead of crash, on discarded output .plt section.
158463 on discarded output .plt section.
158488 Fix this by waiting on the result of the spawned command.
158490 Tested on x86_64-linux.
159046 gdb/nat/linux-osdata.c: fix build on gcc-12 (string overfow)
159087 -static linking). This is because cris-sim.exp in dejagnu turns on
159111 sim: cr16: fix build on gcc-12 (NULL comparison)
159274 Tested on x86_64-linux.
159408 and Zkne extensions on rv64. Add new operand letter 'y' to present 'bs'
159446 First, use "set debuginfod enabled on/off/ask" instead of "set
159447 debuginfod on/off/ask". This is more MI-friendly, and it gives an
159587 I looked at the documentation of "set logging debugredirect [on|off]":
159605 Tested on x86_64-linux.
159658 on XCOFF") introduces C_FILE entries which can store additional
159719 argv[0] for the tests to read out later on. Now that the sim has an
159748 say the test fails on all targets. WIth multitarget testing, the
159769 R_PPC64_REL24_P9NOTOC is a variant of R_PPC64_REL24_NOTOC for use on
159774 The new relocation tells the linker to not use power10 instructions on
159814 A couple of files changed on my latest --enable-maintainer-mode
159862 Tested on x86_64 GNU/Linux.
159888 sim: sh: rework carry checks to not rely on integer overflows
159890 triggers warnings in this code that relies on integer overflows to test
159920 Patch has been tested on x86_64-linux and ppc64le-linux with no test failures.
159941 Tested on x86_64-linux.
159952 * configure.ac (BFD_MACHINES): Defined depending on BFD_ARCH_SIZE.
159976 * po/POTFILESin: Regenerate.
159991 - "set scheduler-locking on"
160061 Build on x86_64-linux, using gcc 7.5.0 and clang 13.0.0.
160088 Tested on x86_64-linux, with gcc 7.5.0, both without (implying -std=gnu++14) and
160093 [gdb/testsuite] Add gdb.arch/ppc64-break-on-_exit.exp
160096 - set a breakpoint on a local copy of glibc's _exit, and
160102 Tested on ppc64le-linux. Verified that the test-case fails without
160280 gdb: adjust x_file fields on COFF readers
160282 on XCOFF") changes the structure associated to the internal
160298 [gdb/testsuite] Add gdb.opt/break-on-_exit.exp
160302 - set a breakpoint on _exit, and
160317 Tested on x86_64-linux and ppc64le-linux.
160324 unique configure flag"), I changed the default from off to on.
160354 PR 28447: implement multiple parameters for .file on XCOFF
160409 The name of this new test was based on that of an existing test,
160519 target. Waiting for the command's completion is later done on
160655 the commands to be run on the bpstat chain constructed in
160656 bp_stop_status(). These commands are run later on. For dprintf
160660 prevents the dprintf commands from being run again later on when other
160661 commands on the bpstat chain are processed.)
160683 infinite recursion check for potential 'source' commands on the
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
160771 This only showed up on the RISC-V target internally, due to the
160777 Fix build on rhES5
160861 mloop files so we can turn -Werror on here fully.
160871 constructor that builds an array_view on top of a contiguous container
160928 This patch proposes to change the constraints on the gdb::array_view
160971 where we iterate on threads and proceed them individually.
160995 ... and so on for each thread ...
161091 Casting 0 to a pointer via (long *) doesn't work on LLP64 targets:
161104 This isn't needed on any reasonable target nowadays, and no other
161130 This block of code relies on i to control which bits to test and how
161353 So all in all, this commit gives up on the idea of only ever keeping
161406 PR28530, Hang in objdump on machine with 196GB RAM
161431 gdb: introduce "set index-cache enabled", deprecate "set index-cache on/off"
161434 boolean setting for turning the index-cache on and off. Even though I
161449 Fix this by introducing "set/show index-cache enabled on/off", regular
161450 boolean setting commands. Keep commands "set index-cache on" and "set
161452 with respectively the default arguments "on" and "off".
161454 Update tests using "set index-cache on/off" to use the new command.
161516 from commit 5dfe4bfcb969 ("Fix format_pieces selftest on Windows").
161602 PR28540, segmentation fault on NULL byte_get
161648 Adjust the comment on top of `struct inf` to clarify the purpose of that
161703 on a pre-populated array of register sets.
161710 Making the register set selection dynamic, based on feature checks, solves
161712 sets only once, and pick and choose based on HWCAP/HWCAP2 or other properties.
161726 …==1909567==ERROR: AddressSanitizer: alloc-dealloc-mismatch (malloc vs operator delete []) on 0x602…
161745 It depends on libraries and compiler which of the operators will get used.
161753 Tested on x86_64-linux.
161784 The cris execute function is conditionally used depending on the
161803 These rules don't depend on the target compiler settings, so hoist
161810 aren't normally run, and they rely on cgen logic that has not yet
161816 These rules don't depend on the target compiler settings, so hoist
161819 We leave the mips rules in place as they depend on complicated
161825 These rules don't depend on the target compiler settings, so hoist
161832 include. This avoids an implicit dependency on the generated
161840 PR28523, ld.bfd created undefined symbols on ppc64
161861 I ran into a case where a breakpoint on _exit never triggered, because it was
161887 Tested on ppc64le-linux, on a power 8 machine.
161904 because it's a power9 insn, and I'm running on a power8 machine.
161908 Tested on powerpc64le-linux.
161962 Tested on x86_64-linux.
162019 Regression tested on `arm-none-eabi` cross Binutils and no issues.
162077 and can set variables on a per-object basis.
162082 we require GNU make and can set variables on a per-object basis.
162086 disable to that now that we require GNU make and can set variables on
162091 disable to that now that we require GNU make and can set variables on
162098 on a per-object basis.
162103 on a per-object basis.
162107 disable to that now that we require GNU make and can set variables on
162113 on a per-object basis.
162117 but we don't abort the build for them, so turn on -Werror everywhere.
162234 then remove the defines out of the header so no new code can rely on
162327 sim: fix compilation on mingw64 [PR sim/28476]
162390 PR28518: signed integer overflow & free on unmalloced address
162429 Add 'set debuginfod' command. Accepts 'on', 'off' or 'ask' as an
162430 argument. 'on' enables debuginfod for the current session. 'off'
162435 This GDB supports auto-downloading debuginfo from the following URLs:
162439 To make this setting permanent, add 'set debuginfod on' to .gdbinit.
162445 is set to 'on', 'off' or 'ask'.
162564 signed-ness. This is useful to avoid dependency on debuginfo when a
162567 v2 moves this to be a method on gdb.Architecture and addresses other
162578 Regression tested on x86-64 Fedora 34.
162598 on the gdb.fortran/dynamic-ptype-whatis.exp test case. In particular
162606 ... relies on is_dynamic_type returning true for such an array.
162614 Avoid self-test failures on x86-linux
162615 The disassembly tests in "maint selftest" will fail on x86-linux.
162646 Rebuild on x86_64-linux and ran gdb.gdb/unittest.exp.
162678 bfd_get_file_size. Set read_only on file size errors.
162710 This patch adds support for running gdb natively on OpenRISC linux.
162729 debugging the glibc port that in being worked on here:
162738 To fix this error (seen on cygwin):
162858 Executing on target: kill -9 28535 (timeout = 300)
162866 Tested on aarch64-linux (with python support disabled) and x86_64-linux (with
162888 Tested on aarch64-linux and x86_64-linux.
162932 Tested on x86_64-linux.
162934 The test-case is based on gdb.opt/fortran-string.exp from
162980 (mmo_scan): Return error on mmo_get_loc returning NULL.
163029 Fix watchpoints with multiple threads on Windows
163031 on Windows when the inferior was multi-threaded. This happened
163048 [Thu Oct 21 11:48:49 2021] (559/559): started http server on IPv6 port=8000^M
163053 The test-case is trying to start debuginfod on a port to see if it's
163055 "started http server on IPv4 IPv6 port=$port"
163062 - accepting "started http server on IPv4 port=$port"
163063 - rejecting "started http server on IPv6 port=$port"
163065 Tested on x86_64-linux.
163069 gdb: fix value.c build on 32-bits
163070 When building on ARM (32-bits), we errors like this:
163119 If built as a shared library, libopcodes has a load-time dependency on
163222 callers to call .data() on the result, meaning it's not changing
163293 Tested on x86_64-linux.
163325 libctf: dump: do not stop dumping types on error
163329 type-dumping, but rather ignore them and carry on, so we dump as many
163335 * ctf-dump.c (ctf_dump_type): Do not abort on error.
163397 new ELF sections on the fly named things like .ctf.foo.c for ambiguous
163424 on the assumption that this name will almost always be at the start
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.
163677 Unaligned load/store instructions on aligned memory or register are as
163678 fast as aligned load/store instructions on modern Intel processors. Add
163716 I found these while working on the subsequent patches, and figured it
163754 Tested on x86_64-linux.
163805 Tested on x86_64-linux.
163826 copyright date on py-membuf.c as 2009-2021 to match py-inferior.c.
163933 be run once so we may potentially miss out on relaxation opportunities
163993 I stumbled on a bug caused by the fact that a code path read
164010 - Make the kind initialized to TARGET_WAITKIND_IGNORE on
164028 This was tested on x86-64 Linux (unix, native-gdbserver and
164029 native-extended-gdbserver boards). It was built-tested on x86-64
164103 Build on x86_64-linux, tested with all .exp test-cases that contain
164112 Depending on the optimization level, gdb may stop in the prolog or after
164114 of main, have it explicitly stop at a break point on the first line of the
164201 "__tls_get_addr call lacks marker reloc" on processing some calls
164204 triggers on a file contained in libphobos.a when running the gcc
164219 with zero sym on the call might be a solution, but current linkers
164289 Tested on x86_64-linux.
164299 Regression tested on x86-64 Fedora 34.
164304 The Rust lex selftest fails on our Windows build. I tracked this down
164313 Fix format_pieces selftest on Windows
164314 The format_pieces selftest currently fails on Windows hosts.
164389 on the remote target (where it is) and expected them to be installed
164420 Also add error checking on ctf_func_type_info call.
164498 gdb.dwarf2/loc-sec-offset.exp (which is based on
164501 Tested on x86_64-linux.
164572 object param on add_long_branch_entry and find_long_branch_entry.
164618 Tested on x86_64-linux.
164697 Tested on x86_64-linux.
164710 Tested on x86_64-linux.
164737 Tested on x86_64-linux.
164748 -ex "set auto-connect-native-target off" \
164759 "set auto-connect-native-target off", which makes that the last command to
164764 Tested on x86_64-linux.
164796 Tested on x86_64-linux.
164950 When running test-case gdb.mi/mi-var-child-f.exp on openSUSE Tumbleweed
164975 Tested on x86_64-linux.
165027 Tested on x86_64-linux.
165047 Tested on x86_64-linux, both with native and target board readnow.
165072 Tested on x86_64-linux.
165089 Tested on x86_64-linux.
165107 Tested on x86_64-linux, both with and without a trigger patch that forces
165128 [gdb] Make execute_command_to_string return string on throw
165162 Tested on x86_64-linux.
165190 return or to wait a bit and do another read, and so on.
165213 Tested on x86_64-linux.
165241 - "set auto-solib-add off" to avoid symbols of shared libs
165246 Tested on x86_64-linux.
165274 Fix this by setting auto-solib-add to off.
165276 Tested on x86_64-linux.
165292 Tested on x86_64-linux.
165305 Tested on x86_64-linux.
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,
165316 gdb.base/bt-on-error-and-warning.exp: problem=internal-error, mode=on: \
165340 Tested on x86_64-linux.
165345 When running test-case gdb.dwarf2/dw2-restrict.exp on openSUSE Leap 15.2 with
165360 Tested on x86_64-linux.
165369 When running test-case gdb.threads/check-libthread-db.exp on openSUSE
165395 Tested on x86_64-linux.
165406 on flexible array member: $cmd
165414 on flexible array member: $cmd
165450 Tested on x86_64-linux.
165463 There are places where the FIELD_* macros are used on call_site_target
165472 setting a field's location. However, I found that some places relied on
165612 You can hit this error on small fuzzed object files, or on files that
165639 Tested on x86_64-linux.
165646 Tested on x86_64-linux.
165664 Limit on string chars or array elements to print is unlimited.
165674 When running test-case gdb.tui/corefile-run.exp on openSUSE Tumbleweed,
165681 What's going on is easier to see when also doing dump_screen if
165704 Tested on x86_64-linux.
165753 failures on sections having huge bogus sizes are to be expected. We
165792 - dropping the -log on the call to verbose in _log. We still can get the
165802 Tested on x86_64-linux.
165810 Tested on x86_64-linux.
165906 Tested on x86_64-linux.
165918 inferior object ensures that the reference count on the Python
165941 pointer to nullptr and finally reduces the reference count on the
166006 Tested on x86_64-linux with gcc and clang.
166078 Regression tested on x86-64 Fedora 34.
166143 Tested on x86_64-linux.
166212 Tested on x86_64-linux.
166227 Tested on x86_64-linux.
166261 Tested on x86_64-linux, both with and without a trigger patch that moves pc to
166283 Since python 2 is no longer supported on most distributions, update the
166291 TARGET_WORD_SIZE. This is done by running grep on the file
166304 grep on bfd-in3.h fails.
166331 value against the old one before updating it, and based on that notifies
166358 /* And so on for all possible var_types. */
166379 Tested on x86_64 GNU/Linux.
166415 Tested on GNU/Linux x86_64 with no regression observed.
166428 An obvious reason is that string operations on std::string are often
166480 rather not try to change it to work on an std::string right now.
166565 on the fly instead of pointing to a static chunk of memory. This will
166585 Tested on GNU/Linux x86_64, with no regression noticed.
166632 While working on other problems, I encountered situations where GDB
166646 Tested on riscv64-linux-gnu.
166662 Tested on x86_64-linux.
166727 Tested on x86_64-linux.
166776 that case, the temporary proc is deleted on exit.
166779 _loclists_list. This is on purpose: as we implement more loclists (and
166782 here to put them on the same level.
166797 Add the `name` and `set_name` methods on `struct field`, in order to
166817 [PR gdb/28369] Use get_shell on gdb/ser-pipe.c
166831 Tested on x86_64-linux.
166930 Without this, we rely on tests logging a failure if runto_main fails,
166998 regression on Windows when using shared libraries. I tracked this
167020 Tested on x86_64-linux.
167035 Tested on x86_64-linux.
167049 Tested on x86_64-linux.
167061 UNRESOLVED: gdb.dwarf2/dw2-opt-structptr.exp: console: set print object on
167068 Tested on x86_64-linux.
167086 Tested on x86_64-linux.
167112 Tested on x86_64-linux.
167123 Tested on x86_64-linux.
167145 Tested on x86_64-linux.
167169 Tested on x86_64-linux.
167197 Tested on x86_64-linux.
167208 note parser. Better GDB's coredump analysis on Solaris...
167215 * elf/common.h: Add note segment constants for core files on
167231 When running test-case gdb.base/break-interp.exp on openSUSE Leap 42.3, I get:
167241 Tested on x86_64-linux.
167275 set schedule-multiple on
167276 …PASS: gdb.multi/multi-term-settings.exp: inf1_how=attach: inf2_how=attach: set schedule-multiple on
167397 Tested on x86_64-linux.
167428 Tested on x86_64-linux.
167438 --with-auto-load-dir=$debugdir:$datadir/auto-load
167439 --with-auto-load-safe-path=$debugdir:$datadir/auto-load
167485 Tested on x86_64-linux.
167540 PR27202, readelf -wL doesn't work on ".loc 0"
167557 - maint set target-non-stop on
167569 Listening on port 1234
167573 …ory=data-directory /usr/bin/gnome-calculator -ex "maint set target-non-stop on" -ex "tar rem :1234"
167675 …(gdb) FAIL: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
167679 stable: it will depend on the insertion order. Here, the insertion
167747 This commit builds on previous work to allow GDB to print a backtrace
167756 In contrast, printing of a backtrace is on by default for
167763 maintenance set internal-error backtrace on|off
167766 maintenance set internal-warning backtrace on|off
167926 * Makefile.def: Add all-gdb dependency on all-libbacktrace.
167931 top-level configure: setup target_configdirs based on repository
167973 I've tested a build of gcc on x86-64, and the same set of target
167999 sim: drop weak func attrs on module inits
168021 x86: Print {bad} on invalid broadcast in OP_E_memory
168073 gdb: don't share aspace/pspace on fork with "detach-on-fork on" and "follow-fork-mode child"
168079 3. "set detach-on-fork on" (the default)
168127 new symtabs for the child as well. When the child stop, but still on
168133 Note that the problem described above happens today with "detach-on-fork
168177 gdb.base/foll-fork.exp: remove gating based on target triplet
168180 to me that the check based on target triplet at the beginning of the
168213 bug on any machine with 4KiB pages.)
168351 * libctf.ver: Give every symbol not in libctf-nobfd a comment on
168359 -export-symbols-regex support. Some nms need specific flags to turn on
168364 reasonably refuse to do an nm on a device file, but before now this
168372 - the test is entirely skipped if NM is set in the environment, on the
168379 -export-symbols-regex on such platforms. Libtool also needs to
168380 augment $LD on some platforms, but this is done unconditionally,
168391 symlink to /usr/bin/nm on the PATH, and /not-on-the-path/my-nm where
168399 NM, if there is one. Run nm on itself, not on /dev/null, to avoid
168400 errors from nms that refuse to work on non-regular files. Remove
168483 Tested on x86_64-linux.
168490 be stored on a slow to access network file system.
168564 The ID of an inline frame is based on the id of the previous frame, so
168616 But, we have not yet computed the frame id for the outer most (on the
168684 /* No sniffer should extend the frame chain; sniff based on what is
168689 frame, as getting the previous frame is likely to depend on the next
168723 When running test-case gdb.base/dcache-flush.exp on ubuntu 18.04.5, I run into:
168741 Tested on x86_64-linux.
168762 observe the sw watchpoint behaviour also on can-use-hw-watchpoints
168770 Tested on x86_64-linux.
168787 PowerPC: Enable mfppr mfppr32, mtppr and mtppr32 extended mnemonics on POWER5
168789 in ISA 2.03, so enable them on POWER5 and later.
168793 on POWER5 and later.
168815 Tested on x86_64-linux.
168865 comment from the implementation, on the basis that it seems obsolete
168889 Tested on x86-64-linux-gnu, native and gdbserver.
169016 attr_to_dynamic_prop depends on the presence of
169077 Tested on x86_64-linux.
169096 There is no indication that using -fpie rather than -fPIE is on purpose, so
169099 Tested on x86_64-linux.
169109 Tested on x86_64-linux.
169160 This patch fixes it, by running subst on the location list body, in
169180 Tested on x86_64-linux.
169191 Tested on x86_64-linux.
169222 Tested on x86_64-linux.
169233 Tested on x86_64-linux.
169242 There is no indication that this is on purpose, so replace these with pie and
169245 Tested on x86_64-linux.
169251 machine the testsuite ran on. On a local machine one can just do
169269 Tested on x86_64-linux.
169282 This patch changes it to be a method on struct type. And, I went
169308 Tested on x86_64-linux, with:
169312 specifically, on openSUSE Leap 15.2 both with package gcc-PIE:
169325 Tested on x86_64-linux.
169330 When running test-case gdb.base/break-interp.exp on ubuntu 18.04.5, we have:
169357 Tested on x86_64-linux.
169362 When running test-case gdb.base/break-probes.exp on ubuntu 18.04.5, we have:
169375 (gdb) UNSUPPORTED: gdb.base/break-probes.exp: probes not present on this system
169400 Tested on x86_64-linux.
169405 When running test-case gdb.base/break-probes.exp on ubuntu 18.04.5, we have:
169429 + unsupported "probes not present on this system"
169434 Tested on x86_64-linux.
169454 Tested on x86_64-linux.
169464 E.g., on x86-64, right after running to main, we see:
169496 using "maint set dwarf unwinder on/off".
169498 Tested on {x86-64 -m64, x86-64 -m32, Aarch64, Power8} GNU/Linux.
169506 type. However, on some platforms this is actually a pointer, and
169512 uses. This approach preserves sign extension on the targets where it
169513 is apparently intended, while avoiding it on others.
169543 This patch changes gdb to use the 'highlight' style on the "XXX" text
169553 With test-case gdb.python/py-events.exp on ubuntu 18.04.5 we run into:
169575 Tested on x86_64-linux.
169593 Tested on x86_64-linux.
169599 running the testcase on ia64 targets I found timeouts along with lots
169605 Note that the testcase fails on ft32-elf, mn10200-elf, score-elf,
169684 Tested on x86_64-linux.
169717 Tested on x86_64-linux.
169742 Tested on x86_64-linux.
169780 Tested on x86_64-linux with an --enable-targets=all build.
169790 Tested on x86_64-linux.
169813 Tested on x86_64-linux.
169911 --enable-targets=all on a 32-bit host results in a link failure with
169929 elf: Don't set version info on unversioned symbols
169930 Don't set version info on unversioned symbols when seeing a hidden
169938 on unversioned symbols.
169988 (gdb) Executing on target: kill -9 13082 (timeout = 300)
170005 Tested on x86_64-linux.
170038 on being able to get the value from such variables, using a named reference.
170049 Tested on x86_64-linux.
170067 info on seeing compiler generated line info, so any reference back
170097 A followup patch will remove all the gas generated line info on
170107 (dwarf2_gen_line_info_1): Don't call set_or_check_view on
170397 Tested on x86_64-linux.
170460 Tested on x86_64-linux with gcc and clang-7 and clang-12.
170527 Tested on x86_64-linux.
170591 Tested on x86_64-linux.
170690 Tested on x86_64-linux with native and target board cc-with-debug-names.
170716 Tested on x86_64-linux.
170781 Tested on x86_64-linux.
170834 Tested on x86_64-linux.
170865 Tested on x86_64-linux.
170902 With a gdb build with CFLAGS "-O2 -g -flto=auto", I run into:
170925 Tested on x86_64-linux.
170949 Tested on x86_64-linux.
170998 Tested on x86_64-linux.
171026 Tested on x86_64-linux.
171068 Tested on x86_64-linux.
171126 Tested on x86_64-linux.
171135 accessing section contents. Don't segfault on NULL howto.
171193 Tested on x86_64-linux.
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:
171258 Tested on x86_64-linux.
171330 has moved on long ago, so drop support for these non-standard names.
171336 We have enough functionality from gnulib now to build sockser on
171452 based on signed integers to read out unsigned values, but in practice, this
171536 build errors for mingw targets. Turning format warnings on triggers
171561 Fix unit test build on Windows
171564 parallel-for-selftests.c. This fixes a build failure on Windows.
171577 PowerPC64: Avoid useless work on R_PPC64_TPREL34
171640 When building gdb on openSUSE Leap 42.3, we trigger the case that
171659 Tested on x86_64-linux.
171728 I've also updated the comments on struct internal_problem as the
171795 Tested on x86_64-linux.
171843 Tested on x86_64-linux.
171855 Tested on riscv64 GNU/Linux.
171891 Tested on x86_64-linux.
171906 Fix potential use on an uninitialised vairable in the MCore assembler.
171934 On a machine on Open Build Service I'm running into a SIGILL for test-case
171961 Tested on my x86_64-linux laptop with avx support, where both test-cases pass.
172095 breakpoint was set on a source line in the library after which a "run"
172111 When building gdb with "-Wall -O2 -g -flto=auto", I run into:
172129 Tested on x86_64-linux.
172140 gdb: Enable finish command and inferior calls for _Float16 on amd64 and i386.
172141 Values of type _Float16 and _Float16 _Complex can now be used on CPUs with
172186 Values of type bfloat16 can also be used on 32-bit targets, which was missed
172204 When building gdb with "-Wall -O2 -g -flto=auto", I run into:
172217 Make breakpoint pending on future shared library load? (y or [n]) n^M
172223 and consequently the selftests dependent on that cannot run.
172257 * testsuite/ld-auto-import/auto-import.exp: Don't pass
172315 * testsuite/ld-auto-import/auto-import.exp: Likewise.
172374 * po/BLD-POTFILES.in: Regenerate.
172397 …t patches we have been grooming and maintaining for quite a few years over on git.haiku-os.org. A…
172449 Current ubsan complains on every use of __PTR_ALIGN (when ptrdiff_t is
172517 Tested on x86_64-linux, using make check//unix.
172542 while on openSUSE Leap 15.2 I have instead:
172595 Tested on x86_64-linux.
172694 The handler for 'info proc status' for native processes on FreeBSD
172716 We get this error when building GDB on some platforms. I get it using
172717 g++-10 on Ubuntu 20.04 (installed using the distro package). It was
172787 Regression tested on x86-64 Fedora 34.
172791 [gdb/cli] Don't assert on empty string for core-file
172810 Tested on x86_64-linux.
172996 Tested on x86_64-linux.
173030 PR28264, ld.bfd crash on linking efivar with LTO
173068 Tested on x86_64-linux.
173138 Tested on x86_64-linux.
173148 Tested on x86_64-linux.
173160 Tested on x86_64-linux.
173177 Tested on x86_64-linux.
173193 on the condition that we switch to the .debug_info section before, which makes
173218 Tested on x86_64-linux.
173248 dwarf2_per_cu_data objects depends on precisely which CUs have been
173255 resize the vector on demand. It fixes the iteration problem by
173270 objdump -S test fail on mingw
173273 is seen on mingw for the simple reason that gcc adds a .exe suffix on
173280 Only run on ELF targets.
173304 between these two ranges. Then it sets a breakpoint on this function
173305 and runs to it, expecting that the language should remain "auto; c"
173340 Tested on x86_64-linux.
173364 same test-case, there are a few known issues, filed on the gdb side as:
173368 and on the gas side as:
173383 Tested on x86_64-linux.
173412 using openSUSE, that didn't show up on other platforms.
173414 Force the same situation on other platforms by adding a dummy start
173417 Tested on x86_64-linux.
173445 Tested on x86_64-linux.
173462 directly matches -- it's being run on 32-bit little endian Linux.
173510 x86: Avoid abort on invalid broadcast
173511 Print "{bad}" on invalid broadcast instead of abort.
173523 * i386-dis.c (OP_E_memory): Print "{bad}" on invalid broadcast
173590 gdb: fix spacing on CCLD silent rules
173596 so no new code can rely on them.
173608 currently working on.
173654 gdb: Don't assume r_ldsomap when r_version > 1 on Linux
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
173938 * write.c (write_relocs): Call obj_fixup_removed_symbol on
173942 if it is used on relocation. Instead, mark it as to be removed
173970 * testsuite/ld-elf/overlay.t: Add fill pattern on overlays.
173987 state rule. Comment on lookahead state madness and need for
174008 (ifile_p1): Change state here on EXTERN instead.
174017 * ldgram.y (statement): Don't switch lexer state on INCLUDE.
174093 While working on the testsuite, I ended up noticing that GDB fails to
174104 on prologue analysis in order to unwind stack.
174129 the RA (return address) register on the stack, which is the information
174139 the stack canary[1], which will then be placed on the stack at <+36> at
174162 The testsuite have been run on riscv64 ubuntu 21.01 with no regression
174227 * testsuite/gas/all/float.s: Make NaN tests conditional on hasnan.
174294 One possible concern was the status of NetBSD on NS32K, where only a.out
174340 This was certainly not my intention when adding the backtrace on fatal
174350 I've also added a test that checks we don't see a backtrace on the
174360 terminates (see maint set backtrace-on-fatal-signal).
174371 gdb: print backtrace on fatal SIGSEGV
174387 The production of the backtrace is on by default, but can switched off
174390 maintenance set backtrace-on-fatal-signal on|off
174391 maintenance show backtrace-on-fatal-signal
174463 restore_original_signals_state prior to forking, so the comment on
174467 comment on SIGQUIT talks about problems with BSD4.3 and vfork,
174473 Finally, the header comment on the function now called
174549 undefined behaviour, after ignoring the signal on many targets we
174552 infinite loop. The behaviour is certainly true on x86-64.
174555 performed an integer divide by zero, compiled this on x86-64
174705 bytes long (with 2 bytes of trailing padding), while on 64-bit it is 16
174710 also for non-ELF targets; so far they were different depending on input
174719 is 12 bytes long (with 2 bytes of trailing padding), while on 64-bit it
174737 (where output sizes currently differ depending on input format).
174745 bytes long (with 2 bytes of trailing padding), while on 64-bit it is 16
174814 gdb: iterate only on vfork parent threads in handle_vfork_child_exec_or_exit
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
174833 Fix that by iterating only on the vfork parent's threads, instead of on
174834 all threads. This is more efficient, as we iterate on just the required
174859 - Pattern matching based on the type of a value.
174861 typically use dynamic dispatch based on the types of the arguments).
174862 - Type-checking assertions when applying some defensive programming on
174924 I found a few .c files that rely on objfiles.h, but that only include
174940 * elf.c (_bfd_elf_fixup_group_sections): Don't segfault on
174977 Tested on x86_64-linux.
175138 Tested on x86_64-linux.
175258 Added inferior 2 on connection 1 (extended-remote localhost:2347)
175279 (it hangs up on the existing remote target) and start listening again
175311 This test tests using both "-p <pid>" and "-ex start" on the command line,
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"
175339 in executing on a different machin. native-extended-gdbserver is not
175431 The push_address method is used to push a CORE_ADDR as a value on
175433 later changed to push any struct value object on the stack.
175974 Depending on the information needed to evaluate a given expression,
176000 returned as one of three possible values, based on operations found in a
176011 condition depends on a value read from an actual target, and the true
176035 location of another variable. Depending on a value of some_variable, the
176038 the value will be returned as an implicit location description on the
176051 evaluating it. Also, a similar example could be made based on a
176079 implicit location description with a constant value that depends on a
176082 end condition of that loop depends on the expectation that a frame base
176094 the act of evaluation relies on accessing the data from the actual
176421 While working on a stack unwinding issue using 'set debug frame on', I
176438 Tested on riscv64-linux-gnu.
176445 after -g3 on the command line, and that would cause some gcc versions to
176471 gdb::optional::get"), some macro-related tests fail on Ubuntu 20.04 with
176488 DW_AT_str_offsets_base attribute on the CU.
176505 testsuite looks on par with how it was before 4d7188abfdf2.
176525 Building on OpenBSD, I get warnings like:
176584 Also remove unnecessary static on local var temp_obstack in test_addrmap.
176592 (test_addrmap): ... here. Remove static on temp_obstack. Use lambda
176649 Build on x86_64-linux, tested by doing:
176713 In the context of ROCm-gdb [1], the ROCm target sits on top of the
176725 called on the parent's target stack and sometimes on the child's target
176737 target_follow_fork on the parent inferior's target stack. I think it
176746 parent as the current inferior. That lets all targets present on the
176748 themselves on the fork child's target stack if needed.
176767 exec_on_vfork depends on the current inferior, after this change.
176816 on the line
176825 Add checks in the two `get` methods, also conditional on _GLIBCXX_DEBUG.
176975 Tested on x86-64 Fedora 32. I also propose putting this on the GDB 11
177005 Tested on x86_64-linux.
177030 Tested on x86_64-linux.
177053 Tested on x86_64-linux.
177076 Tested on x86_64-linux.
177106 Tested on x86_64-linux.
177156 running on an x86_64 machine. The unit-test introduced in this change
177157 has passed for all the targets (--enable-targets=all) running on the
177194 Tested on x86_64-linux.
177216 Tested on x86_64-linux.
177238 Regression tested on x86-64 Fedora 34.
177247 Regression tested on x86-64 Fedora 34.
177387 - Don't use #ifdef's on ptrace ops. obsd-nat.h didn't include
177395 single function and invoke it on new child processes reported via
177411 Replace a check for WIFSTOPPED on the returned status from waitpid
177429 This fixes an unused function warning on OpenBSD which does not
177434 Don't compile x86 debug register support on OpenBSD.
177435 Simon Marchi tried gdb on OpenBSD, and it immediately segfaults when
177464 HAVE_PT_GETDBREGS is defined. PT_GETDBREGS doesn't exist on OpenBSD, so
177468 fix by omitting debug register support entirely on OpenBSD:
177569 gas: improve C_BSTAT and C_STSYM symbols handling on XCOFF
177701 to avoid running out of file descriptors on thin archives with many
177852 That operation is not available on integers of more than 8 bytes.^M
177857 Tested on x86_64-linux, with gcc-11 and target board
177891 assembled when selecting a basic -mppc on the command line:
177947 Tested on x86_64-linux.
177978 Tested on x86_64-linux.
178000 problems exposed by using 'set debug frame on'.
178043 Now, inside this function, if 'set debug frame on' is in effect, then
178119 original test relied on the fixes in that original series. However, I
178148 on open_nested_file failure only if the error is unset.
178157 This test fails on PPC64 because PPC64 prints the value of 3.5 with
178158 more significant digits than on Intel. The patch updates the regular
178159 expression to allow for more significant digits on the constant.
178169 The gdb build was broken on Windows after the patch to change
178463 on a lookahead NAME parsed in expression mode.
178537 so that we can understand what is going on, do some cleanups and add new
178623 some arguments on the command line, but does not end up running the
178658 each. I find it easier to work on a test with multiple smaller
178660 but one when working on one. It's also easier to add things without
178661 having to think about the impact on existing tests, and vice-versa.
178701 last_spawn_tty_name depending on whether spawn_out(slave,name) exists
178713 in spawn_capture_tty_name we unset last_spawn_tty_name. However, on
178803 Tested on x86_64-linux, with:
178845 cases, but their expectations were wrong. (This may have been based on
178960 Tested on x86_64-linux, with gcc-8, gcc-9, gcc-10, gcc-11, clang-8, clang-10
179016 Tested on x86_64-linux.
179036 That operation is not available on integers of more than 8 bytes.^M
179052 Tested on x86_64-linux, with gcc-10 and gcc-11.
179078 The patch also tidies some tc_get_reloc functions that leak memory on
179109 (tc_gen_reloc): Delete dead code. Free memory on error.
179111 on error.
179157 PR28106, build of 2.37 fails on FreeBSD and Clang
179161 reinterpret_cast can't be used on nullptr.
179367 on the global context when observers are invoked. Frame 35,
179421 I'm debugging why GDB crashes on OpenBSD/amd64, turns out it's because
179423 to break on x86_dr_low_get_status, so I thought it would be a good
179547 FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left
179550 the detach-on-fork=off case:
179565 (gdb) FAIL: gdb.threads/fork-plus-threads.exp: detach-on-fork=off: only inferior 1 left
179569 actually iterating on inferiors. The current implementation:
179583 We actually need to pass down the list on which we want to iterator
179587 all_inferiors_safe needed to allow filtering on process target (like
179604 gdb: Support stepping out from signal handler on riscv*-linux
179605 Currently, gdb cannot step outside of a signal handler on RISC-V
179620 This patch adds support for stepping outside of a signal handler on
179628 Build and tested on riscv64-linux-gnu.
179633 Many tests fail in gdb/testsuite/gdb.base/sigstep.exp on
179638 kernel support), but none are available on riscv*-linux-gnu hosts, at
179642 have hardware single step capability, disabling tests relying on such
179645 Tested on riscv64-linux-gnu.
179650 While working on my series to replace the DWARF psymbol reader, I
179656 Regression tested on x86-64 Fedora 32.
179680 Regression tested on x86-64 Fedora 32.
179684 or1k: fix pc-relative relocation against dynamic on PC relative 26 bit relocation.
179773 setting up inferior 2, and all that code relies on the current
179778 - solib_create_inferior_hook is currently not called on the
179824 It then verifies that whatever the detach-on-fork and follow-fork-child
179933 DWARF sections have special names on AIX which need be handled
179954 When running test-case gdb.base/gold-gdb-index.exp on openSUSE Tumbleweed,
179986 Tested on x86_64-linux.
180009 Tested on x86_64-linux.
180046 interpreter as this is the only one available on this platform.
180048 I do not think this change will cause regressions on any other
180146 with -fasynchronous-unwind-tables (x86-64 defaults that on, but not
180169 try/catch and print warning on exception.
180243 This commit fixes the issue by not relying on target_close to
180278 When running test-case gdb.threads/check-libthread-db.exp on openSUSE
180293 which is what I get on openSUSE Leap 15.2 with glibc 2.26, and what is
180299 Using a breakpoint on check_thread_db_callback we can compare the two
180306 thread to return. We cannot rely on its thread register. They
180332 Tested on x86_64-linux, both with glibc 2.33 and 2.26.
180400 gdb: disable commit-resumed on -exec-interrupt --thread-group
180488 If a filter target and thread-specific ptid are given, it iterates on
180490 on thread. And this happens quite often, which means we unnecessarily
180491 spend time iterating on threads to find the one we are looking for. The
180496 different behaviors depending on the kind of ptid, to avoid this
180499 can work seamlessly on multiple threads or on one specific thread, just
180503 different cases and limiting what we iterate on to just what we need.
180506 based on filter_target, iterate on all of the matching inferiors'
180509 necessarily be given), look up that inferior and iterate on all its
180512 specific thread and "iterate" only on it
180514 For the last case, what was an iteration on all threads of the filter
180526 Don't filter on m_filter_ptid.
180528 Choose path based on filter_ptid (all threads, all threads of
180542 std::unordered_map::find, instead of iterating on all of the
180578 inferiors on the same target. Imagine that inferior A has 10k resumed
180643 About implementation details: using the new setters on class
180655 on the threads, it means we could mistakenly leave some threads in the
180669 introducing a dependency on the current inferior (the current inferior
180682 status is set on or removed from a thread. Add a getter and a setter on
180737 its internal use (statuses it doesn't intent on leaving pending).
180819 start_step_over). Based on the std::list and Boost APIs, add a splice
180846 adds its mock inferior to the inferior list on construction, and removes
180847 it on destruction. This means that tests run with mock inferiors in the
180863 we want to append a new element on the list, we need to walk the whole
180875 immediately. We currently keep exited threads on the thread list, but
180947 Iterating on an intrusive_list yields references to objects (e.g.
180993 SEF_ELF_OCTETS flag on debug sections.
180997 [gdb/testsuite] Fix gdb.btrace/tsx.exp on system with tsx disabled in microcode
181011 Tested on x86_64-linux, with both gcc 7.5.0 and clang 12.0.1.
181068 Tested on x86_64-linux, with native, check-read1, readnow, cc-with-gdb-index,
181105 We shouldn't be asserting on anything to do with leb128 values, or
181124 block, and uvalue decrementing past zero on one of the leb128 bytes.
181159 If GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS is set on any input
181167 4. Set GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS on output.
181187 non_got_ref_without_indirect_extern_access on legacy non-GOT or
181276 Built on x86_64-linux-gnu and riscv64-linux-gnu.
181386 program, or an s390 program on another OS GDB doesn't know about, we
181400 even for non-Linux system. Maybe that was on purpose, because it would
181410 when debugging a bare-metal s390 executable or an executable on another
181483 When running test-case gdb.guile/scm-breakpoint.exp on openSUSE Tumbleweed
181495 The same test passes on openSUSE Leap 15.2 with guile 2.0, where the second
181514 Tested on x86_64-linux, with both guile 2.0 and 3.0.
181546 Since plugin_maybe_claim calls bfd_close on the original input BFD if it
181584 gprof fails to compile on Solaris 10 and 11.3 with --disable-nls:
181625 following patch does. Tested on i386-pc-solaris2.10 and
181631 * sysdep.h [!ENABLE_NLS]: Prevent inclusion of <libintl.h> on
181637 binutils currently fails to compile on Solaris 10:
181653 Fixed with the following patch. Tested on i386-pc-solaris2.10.
181675 * po/gas.pot: Regenerate.
181682 * po/bfd.pot: Regenerate.
181798 propagated to downstream consumers, to run the testsuite on an already
181800 in a CI job. This GDB package is then tested on different machines /
181810 takes a few more seconds to run, but on the other hand it's quite useful
181844 currently working on.
181889 Running "make check-perf" on a system with Python 3.8 (e.g., Ubuntu
181909 use time.perf_counter() or time.process_time() instead depending on
181949 (time.perf_counter, time.process_time): Map to time.clock on
181964 gdb.perf/: FAIL on Python errors, avoid "ERROR: internal buffer is full"
181965 Currently, if you run make check-perf on a system with Python 3.8,
182046 Tested on x86_64-linux, whith make targets check and check-read1.
182091 Tested on x86_64-linux (openSUSE Leap 15.2), no regressions for config:
182249 [gdb/testsuite] Fix fail in gdb.fortran/ptype-on-functions.exp with gcc-7
182255 (gdb) FAIL: gdb.fortran/ptype-on-functions.exp: ptype say_string
182269 Tested on x86_64-linux, with gcc-7 and gcc-10.
182275 * gdb.fortran/ptype-on-functions.exp: Allow both $integer8 and
182280 gdb: fall back on sigpending + sigwait if sigtimedwait is not available
182368 When loading a file using the file command on macOS, we get:
182400 commit ea142fbfc9c1 ("Fix breakpoints on file reloads for PIE