Lines Matching +refs:po +refs:skip +refs:over +refs:python +refs:string
251 skip SCFI tests for x32 targets.
1224 gdb/testsuite: fix failure in gdb.python/py-inferior.exp
1230 gdb/python: add gdb.InferiorThread.__repr__() method
1232 failures were reported for gdb.python/py-inferior.exp.
1256 As the main thread doesn't exit (until the test is over), the
1378 gdb/python: Add gdb.InferiorThread.__dict__ attribute
1404 gdb/python: Add gdb.Inferior.__dict__ attribute
1429 gdb/python: remove users ability to create gdb.Progspace objects
1470 gdb/python: add gdb.Frame.__repr__() method
1498 gdb/python: add gdb.InferiorThread.__repr__() method
1526 gdb/python: hoist common invalid object repr code into py-utils.c
1536 unwind_infopy_repr, where we currently return a different string.
1654 gdb/python: New InferiorThread.ptid_string attribute
1656 read-only attribute contains the string returned by target_pid_to_str,
1657 which actually converts a ptid (not pid) to a string.
1659 This is the string that appears (at least in part) in the output of
1663 Having access to this string from Python is useful for allowing
1793 (gdb) python kill_and_detach()^M
1795 File "<string>", line 1, in <module>^M
1796 File "<string>", line 7, in kill_and_detach^M
1800 python kill_and_detach()
1853 of opcodes. When opc->format is an empty string, no extra
1954 more examples, also in other langauges, over time.
2360 Update x86 ELF linker to skip R_386_NONE/R_X86_64_NONE when scanning
2984 scheme, and also may trip over versioned symbols) -- but we know that
2999 lookup_minimal_symbol_text always loops over all objfiles, even when
3001 function to loop over the minimal number of objfiles in the latter
3169 This patch changes this code to just use a std::string. A new type is
3552 visium: drop .bss and .skip overrides
3558 The override for .skip is simply pointless, for read.c having exactly
3800 4) Check out */po/*.pot which we don't update frequently.
3854 end of the expression GDB just reports the empty string to the user.
3873 within some longer string, I don't think multi-line error messages
4048 Currently GDB when executing in reverse over multiple statements in a single
4127 So far so good, a "next" stepped over the whole of line 11 and stopped at
4226 When stepping forward from line 40, we skip both of these ranges and land on
4413 get migrated over to the common parsing logic, but for now, switch
4637 of DW_TAG_entry_point over DW_TAG_subprogram:
5613 wonder which code paths have to skip inline frames when creating
6177 > CXX python/py-unwind.o
6178 …> gdb/python/py-unwind.c:126:16: error: flexible array member 'reg' of type 'cached_reg_t[]' with …
6326 human readable string when store tracing is enabled.
6364 (gdb.rocm/continue-over-kernel-exit.exp) that exposes a couple issues
6398 was stepping when it terminated (due to the displaced step over the
6506 Currently, if you step over kernel exit, you see:
6547 Step over thread exit, always delete the thread non-silently
6548 With AMD GPU debugging, I noticed that when stepping over a breakpoint
6600 While making step over thread exit work properly on AMDGPU, I noticed
6614 The previous patch extended gdb.threads/step-over-thread-exit.exp to
6630 gdb.threads/step-over-thread-exit.exp improvements
6632 gdb.threads/step-over-thread-exit.exp:
6634 - Add a third axis to stepping over the breakpoint with displaced vs
6648 …Thread 3 "step-over-threa" hit Breakpoint 2, 0x000055555555524e in my_exit_syscall () at .../tests…
6650 …(gdb) FAIL: gdb.threads/step-over-thread-exit.exp: displaced-stepping=auto: non-stop=on: target-no…
6808 s390: Use safe string functions and length macros in s390-mkopc
6810 and use macros for string lengths, such as mnemonic, instruction
6976 This can also remove the XFAIL added to gdb.python/pq-watchpoint tests
7476 still over-broad, but it seems safe and is better than the status quo.
7744 the code for string handling writes the address fetching callback
7746 rather than option_def::var_address::string.
8363 gdb/python: avoid use of _PyOS_ReadlineTState
8364 In python/py-gdb-readline.c we make use of _PyOS_ReadlineTState,
8386 gdb: move gdbpy_gil into python-internal.h
8387 Move gdbpy_gil class into python-internal.h, the next
8389 than python.c.
8533 …Temporary breakpoint 1 at 0x13f1917b4: file C:/src/repos/binutils-gdb.git/gdb/testsuite/gdb.python…
8546 …Temporary breakpoint 1 at 0x13f5617b4: file C:/src/repos/binutils-gdb.git/gdb/testsuite/gdb.python…
8550 …_inlined (a=0x40fa5c) at C:/src/repos/binutils-gdb.git/gdb/testsuite/gdb.python/py-finish-breakpoi…
9319 - the string "[ No Source Available ]".
9372 gdb.python/py-symtab.c with clang, I noticed that it was going wrong
9514 However, that final 'step' command steps to (but not over/through) the
9518 This commit adds a test to see what happens when stepping over/through
9531 when stepping over/through a statement which triggers a watchpoint.
9540 This was split over multiple lines and ended up missing a space.
9627 variable, in ada_to_fixed_type_1, could result in gdb walking over all
9628 the entries in the cooked index over and over.
10062 expected output. I've also changed the branch over stubs emitted at
10557 regcache::transfer_regset iterates over an array of regcache_map_entry,
10675 command, we can tell when the output is over when we receive the GDB
10705 index() in string.h, which triggers a "shadows a global declaration"
10867 [gdb/build] Fix adding -DNDEBUG to python flags of release build
10872 intends to ensure that -DNDEBUG is added to the python flags of a release
10877 configure:22024: checking compiler flags for python code
10912 configure:25214: checking compiler flags for python code
11002 since we iterate over all symbols. By deferring this until once we've found the
11151 gdb/python: display errors from command completion
11176 possible completion is a string, if not the completion is ignored.
11179 a string, and display an error if the conversion fails. After all,
11180 returning anything but a string is surely a mistake by the extension
11191 string, but still can't convert it to a string, then I think it's OK
11290 [gdb/tui] Use const std::string for string literals in tui-stack.c
11292 strlen with a string literal argument:
11304 Use const std::string to encapsulate the string literals, and use
11305 std::string::size () instead.
11307 I tried making the string names (PROC_PREFIX, LINE_PREFIX, PC_PREFIX and
11525 over.
11558 duplicated between compilation units, the more GDB would over count,
11559 and so, over-grow the index.
11569 bothered to check the upper limit, and over full hash table isn't
12418 gdb/python: handle completion returning a non-sequence
12426 completions available. Only string elements of the sequence
12521 [gdb/testsuite] Two fixes in gdb.python/tui-window-disabled.exp
12522 I ran test-case gdb.python/tui-window-disabled.exp on a configuration without
12523 python support, and ran into:
12566 wasn't properly re-based over recent opcode table additions.
12578 x86: also prefer VEX encoding over EVEX one for VCVTNEPS2BF16 when possible
12579 Deal with what 58bceb182740 ("x86: prefer VEX encodings over EVEX ones
12601 preferable over converting match_never() to match_always()), while
12827 [gdb/python] Reformat missing_debug.py using black
12828 Reformat gdb/python/lib/gdb/missing_debug.py with black after commit
12829 e8c3dafa5f5 ("[gdb/python] Don't import curses.ascii module unless necessary").
13366 [gdb/python] Don't import curses.ascii module unless necessary
13367 I ran into a failure in test-case gdb.python/py-missing-debug.exp with python
13368 3.6, which was fixed by commit 7db795bc67a ("gdb/python: remove use of
13371 However, I subsequently ran into a failure with python 3.11:
13386 (gdb) FAIL: $exp: source python script
13394 Fix this by only using the curses module when necessary, for python <= 3.7.
13396 Tested on x86_64-linux, with both python 3.6 and 3.11.
13600 of the first string in TestStrings, but without making sure that this
13601 string is preceded by a string terminator. Thus GDB may spuriously print
13602 some random characters from before that string, and then the test fails.
13702 use the std::string ctor or implicit conversion from std::string_view to
13703 std::string instead.
13868 no control over. So I changed the code to heap allocation.
14412 Deprecated functionality would better not win over its modern
14489 Windows and AIX. Use std::string instead. I'm not able to test this
14514 gdb/python: remove use of str.isascii()
14702 does not cover this case so that python can be partially initialized
14709 variables but is named "two"), and to iterate over all the variables
14934 [gdb/testsuite] Fix gdb.threads/stepi-over-clone.exp regexp
14937 (gdb) PASS: gdb.threads/stepi-over-clone.exp: catch process syscalls
14945 (gdb) FAIL: gdb.threads/stepi-over-clone.exp: continue
14954 (gdb) PASS: gdb.threads/stepi-over-clone.exp: third_thread=false: \
14963 FAIL: gdb.threads/stepi-over-clone.exp: third_thread=false: non-stop=on: \
15048 - A string: The handler can return a filename, which is the file
15125 second request -- and as these requests go over the network, they
15394 target), and you step over thread exit with scheduler-locking on, this
15411 resumed thread has a thread_fsm. Note that unlike stepping over a
15440 Testcases for stepping over thread exit syscall (PR gdb/27338)
15441 Add new gdb.threads/step-over-thread-exit.exp and
15442 gdb.threads/step-over-thread-exit-while-stop-all-threads.exp
15443 testcases, exercising stepping over thread exit syscall. These make
15582 on", and you step over a function that spawns a new thread, the new
15621 Without this, we'd see failures in step-over-thread-exit testcases
15627 …- (gdb) PASS: gdb.threads/step-over-thread-exit.exp: displaced-stepping=off: non-stop=on: target-n…
15628 …+ FAIL: gdb.threads/step-over-thread-exit.exp: displaced-stepping=off: non-stop=on: target-non-sto…
15639 gdb.threads/step-over-thread-exit-while-stop-all-threads.exp testcase
15644 …FAIL: gdb.threads/step-over-thread-exit-while-stop-all-threads.exp: displaced-stepping=off: target…
15659 stops all threads to start an inline step over for thread 1.
15665 #3 - Thread 1 exits while stepping (it steps over an exit syscall),
15678 over and restarts threads.
15686 stepped over too, so gdb starts a step-over dance again.
15715 gdb: clear step over information on thread exit (PR gdb/27338)
15716 GDB doesn't handle correctly the case where a thread steps over a
15724 …tory build/binutils-gdb/gdb/testsuite/outputs/gdb.threads/step-over-thread-exit/step-over-thread-e…
15725 …from build/binutils-gdb/gdb/testsuite/outputs/gdb.threads/step-over-thread-exit/step-over-thread-e…
15727 …ram: build/binutils-gdb/gdb/testsuite/outputs/gdb.threads/step-over-thread-exit/step-over-thread-e…
15733 …Thread 2 "step-over-threa" hit Breakpoint 1, my_exit_syscall () at src/binutils-gdb/gdb/testsuite/…
15741 …Thread 3 "step-over-threa" hit Breakpoint 1, my_exit_syscall () at src/binutils-gdb/gdb/testsuite/…
15749 …Thread 4 "step-over-threa" hit Breakpoint 1, my_exit_syscall () at src/binutils-gdb/gdb/testsuite/…
15765 When trying the same but with in-line step over (displaced-stepping
15769 … build/binutils-gdb/gdb/testsuite/outputs/gdb.threads/step-over-thread-exit/step-over-thread-exit \
15771 …from build/binutils-gdb/gdb/testsuite/outputs/gdb.threads/step-over-thread-exit/step-over-thread-e…
15773 …ram: build/binutils-gdb/gdb/testsuite/outputs/gdb.threads/step-over-thread-exit/step-over-thread-e…
15779 …Thread 2 "step-over-threa" hit Breakpoint 1, my_exit_syscall () at src/binutils-gdb/gdb/testsuite/…
15787 …1 Thread 0x7ffff7c60740 (LWP 2928285) "step-over-threa" 0x00007ffff7f7c9b7 in __pthread_clockjo…
15803 infrun never clears the in-line step over info. So if we try
15809 displaced or in-line step over exits. We can do that with the new
15816 any step-over the exiting thread might have been doing at the time of
15819 - the exiting thread was doing an in-line step-over with an all-stop
15821 - the exiting thread was doing an in-line step-over with a non-stop
15823 - the exiting thread was doing a displaced step-over with a non-stop
15875 Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit
15876 When stepping over a breakpoint with displaced stepping, GDB needs to
15882 Similarly, when stepping over a breakpoint in line, GDB also needs to
15884 over state and re-resume threads.
16015 With this, gdb.threads/stepi-over-clone.exp now cleanly passes against
16090 over a breakpoint.
16143 Step over clone syscall w/ breakpoint, TARGET_WAITKIND_THREAD_CLONED
16149 stepping over a breakpoint set at a clone syscall instruction, one is
16169 (as there's no breakpoint to step over). While stepping the thread
16175 (as there's no breakpoint to step over). Other threads might be
16184 The problem then is what happens when we try to step over a clone
16237 What is needed is for GDB to have more control over whether the new
16296 This adds a new gdb.threads/stepi-over-clone.exp testcase, which
16297 exercises stepping over a clone syscall, with displaced stepping vs
16299 over clone syscalls with gdb.base/step-over-syscall.exp, but this test
16314 ("Step over clone syscall w/ breakpoint,
16315 TARGET_WAITKIND_THREAD_CLONED"), the gdb.threads/step-over-exec.exp
16325 gdb.threads/step-over-exec.exp testcase (almost silently) expose a
16338 …./gdb /home/pedro/gdb/build/gdb/testsuite/outputs/gdb.threads/step-over-exec/step-over-exec-execr-…
16346 …) at /home/pedro/gdb/build/gdb/testsuite/../../../src/gdb/testsuite/gdb.threads/step-over-exec.c:69
16352 …Exec-ing /home/pedro/gdb/build/gdb/testsuite/outputs/gdb.threads/step-over-exec/step-over-exec-exe…
16353 …gram: /home/pedro/gdb/build/gdb/testsuite/outputs/gdb.threads/step-over-exec/step-over-exec-execr-…
16355 …hread 1 "step-over-exec-" hit Breakpoint 1, main () at /home/pedro/gdb/build/gdb/testsuite/../../.…
16395 above -- linux_nat_target::kill iterates over all LWPs, and after the
16416 The crash with gdb.threads/step-over-exec.exp is not observable on
16429 gdb.threads/step-over-exec.exp to cover the fix, add a new
16700 bfd: use less memory in string merging
16706 string merging, and then got pushed over the limit by this.
16717 ld: Avoid overflows in string merging
17034 We want the "nexti" to step into, not over, signal handlers invoked by
17266 * po/bfd.pot: Regenerate.
17281 * po/bfd.pot: Regenerate.
17295 * po/bfd.pot: Regenerate.
17657 Fix resizing of TUI python windows
17659 TUI python window that would then be outside of the new size,
18127 producer string.
18397 released in 2019[3], which is over 4 years ago. Clang has had C++17
18499 gdb/python: Add new gdb.Value.bytes attribute
18592 from every other thread, then GDB has finished detaching, GDB can skip
18723 gdb/testsuite: add a clang XFAIL to gdb.python/py-watchpoint.exp
18726 a FAIL in gdb.python/py-watchpoint.exp. Since this is nothing wrong with
18733 gdb/testsuite: fix running gdb.python/py-explore-cc with clang
18734 The test gdb.python/py-explore-cc.exp was showing one unexpected
18748 new_program_name (a string) each time GDB starts an inferior, in the
18756 gdbsupport: make gdb_abspath return an std::string
18766 std::string, which copies the buffer contents, leaving ownership with
18949 [gdb/python] Only include gdbsupport/selftest.h if GDB_SELF_TEST
18950 I noticed that gdb/python/python.c unconditionally includes
19137 python pygments, and in absence of that, unhighlighted source text.
19139 In the case of python pygments, it autodetects which language to use based on
19225 * ctf-string.c (ctf_str_add_ref_internal): Report ENOMEM on the
19226 dict if addition of a string ref fails.
19482 - Introduce svr4_so, which contains just an std::string for the name
19862 [gdb/cli] Skip string copy in source_cache::ensure
19869 The last line causes an unnecessary string copy.
19871 C++20 allows us to skip it, like this:
20222 sim: mips: fix printf string
20270 -zstack-size skip.
20365 various functions over GDB's remote protocol. By using bfd_stat we
20711 gdb/python: implement support for sending custom MI async notifications
20722 gdb/python: generalize serialize_mi_result()
21059 Convert tdesc's expedite_regs to a string vector
21095 After the previous commit there is now a redundant string copy in
21217 The problem is that gdbserver processes this string in a loop. At
21220 to the end of the string.
21228 statement at the end of the loop if the (sub-)string we just processed
21282 quote is not opening an argument string.
21529 test (gdb.python/py-progspace-events.exp) was failing when run with
21565 …[Switching to inferior 1 [process 3970383] (/tmp/build/gdb/testsuite/outputs/gdb.python/py-progspa…
21567 …#0 breakpt () at /tmp/build/gdb/testsuite/../../../src/gdb/testsuite/gdb.python/py-progspace-even…
21755 Anyway, after this commit, the gdb.python/py-progspace-events.exp test
21916 reread_symbols, and reread_symbols loops over every currently loaded
21921 BFD, the filename for this BFD is literally the string
21947 always skip in-memory BFDs in reread_symbols. This preserves the
21982 Currently the function takes a string and an errno, and prints, to
21983 stderr, the string followed by the result of calling strerror on the
21986 In some places the string passed to print_sys_errmsg is just a
21993 is passed through strerror and the resulting string printed. This new
21998 a warning, however, the string being passed in is more than just a
22000 used, it would style the whole string. For these users I have
22035 strings when we could easily use std::string and string_printf to
22424 Fix this by initializing the z registers to 0 and then copying over the
22476 Convert tdesc's expedite_regs to a string vector
22480 Convert expedite_regs to a std::vector of std::string so it is easier to
22484 std::vector of std::string as well. Or maybe expose an interface that target can
22711 candidates corresponding to aliases can be conveniently skipped over.
22791 gdb/python: reformat file with black
22806 string.
22976 (gdb) PASS: gdb.python/py-progspace-events.exp: inferior 1
22990 (gdb) PASS: gdb.python/py-progspace-events.exp: step
23001 a consequence of reading files over the remote protocol. The test
23450 iterate over the objfiles list, and for each of those we check the
23467 After handling the executable, GDB can then iterate over the objfiles
23472 to the gdb.python/py-exec-file.exp test in the previous commit.
23478 gdb/python: make the executable_changed event available from Python
23646 gdb/python: new Progspace.executable_filename attribute
23670 gdb/python: new Progspace.symbol_file attribute
23687 mention what the returned string is actually the filename
23786 …string table. Initialise the dt_strsz field. (_bfd_elf_slurp_version_tables): Only free the conten…
23828 x86: prefer VEX encodings over EVEX ones when possible
24178 over 64. The intention is that these should be reused by real
24225 [gdb/dap] Fix dap for python < 3.8
24226 With any gdb.dap test and python 3.6 I run into:
24232 The attribute is not supported before python 3.8, which introduced the
24238 - openSUSE Leap 15.4 with python 3.6, and
24239 - openSUSE Tumbleweed with python 3.11.5.
24276 std::string x = f.string ();
24278 However, string_file::string returns a 'const std::string &'... so it
24279 seems to me that this must be copying the string (? I find it hard to
24283 the string.
24989 that a C type of this kind is recognized as a string.
25012 Python array- and string-handling code.
25430 when in MI mode, and uses this new mechanism to skip the related section
25487 This problem was encountered while building the python-graph-tool
26021 convert to a nop. If the opcode was split over two frags then a size
26197 will skip the output if it is present, but is equally happy if the
26453 not using the actual contents of the string.
26457 scenario where a string like this can really be returned.
26630 function, there is no such concept of token, so we can just skip that.
26705 Commit 3bab069c29b3 carelessly allowed "string" to be released from
26708 the original string. The fixup then of course was overwritten.
26713 * stabs.c (s_stab_generic): Don't free string twice. Don't
26714 blow away entire notes obstack on a missing string.
26768 When running test-case gdb.python/py-symbol.exp with target board
26771 (gdb) python print (len (gdb.lookup_static_symbols ('rr')))^M
26773 (gdb) FAIL: gdb.python/py-symbol.exp: \
26778 (gdb) python print (len (gdb.lookup_static_symbols ('rr')))^M
26780 (gdb) PASS: gdb.python/py-symbol.exp: \
26784 The problem is that the loop in gdbpy_lookup_static_symbols loops over compunits
26918 address string being shorter or longer than a regular address.
26925 Handle array- and string-like values in no-op pretty printers
26927 array- and string-like objects known by the gdb core. Two new tests
26934 example, the Rust code understands that &str is a string-like type, or
26946 language code knows that a type is string-like.
26948 Unlike Value.string, these cases are handled by the type's language,
27037 string in the executable. But, if the inferior is running, then the
27062 …ble_section_name): Use a rotating array of static buffers for the return string. (printable_sectio…
27409 Replace two uses of alloca with std::string.
27768 section name string. Really, the name belongs in bfd_alloc'd memory
27773 the "string" copy.
27780 as I see that function might skip over end-of-line, and lack of a
27807 ensuring "string" is freed. Use get_absolute_expression in
28451 checking X86_XSTATE_ZMM and skip the ZMM region handling entirely if
28699 and unnecessary casts. Don't zalloc when only the string
28933 * i386-gen.c (process_i386_opcodes): Correct format string.
28940 Delete support for old compilers that don't support string
29057 name is outside the string table. That is, the offset is greater
29058 than the actual string table size.
29066 COFF Error: string table offset (256) outside string table (length 0)
29157 were three copies of the string handling code, so rather than fix them
30089 uint64_t to match format string.
30091 use PRIx64 in format string.
30176 Some places matching the first char of a string against
30178 This could lead to accesses past the end of the string and potential
30181 the end of a string.
30186 Some places matching the first char of a string against
30188 string being "". This patch adds the check to stop accesses past the
30189 end of the string and potential buffer overruns.
30195 zero string terminator.
30201 zero string terminator.
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.
31218 gdb/testsuite: fix race condition in gdb.python/py-thread-exited.exp
31219 I ran into a test failure on gdb.python/py-thread-exited.c. The test
31728 This fixes an internal error in the gdb.threads/detach-step-over.exp
31770 For the resume method, iterate over all non-exited inferiors resuming
31895 gdb/python/py-param.c:33:6: note: an enum with different value name is \
31912 [gdb/build] Remove superfluous variable param_types in gdb/python/py-param.c
31913 In gdb/python/py-param.c we have:
32022 When running test-case gdb.python/py-symbol.exp with target board
32025 (gdb) python print (len (gdb.lookup_static_symbols ('rr')))^M
32027 (gdb) FAIL: gdb.python/py-symbol.exp: print (len (gdb.lookup_static_symbols ('rr')))
32798 The patch adds a second possible result string for the test
33133 Update the set re string to accept the hex address if it exits.
33349 std::string copy.
33445 It makes little sense to have this comment meanwhile over a hundred
33824 Handling of main is special, and a future optimization may skip the lookup and
34319 over 300 unexpected errors, due to a segmentation fault and several
34392 + std::string encoded = ada_encode (name, false);
34444 Remove f-string from DAP
34445 One more f-string snuck into the DAP code, in breakpoint.py. Most of
34680 value. Return end of string.
34695 Avoid the use of sprintf with a "%s" format string, replacing with
34698 string output buffer.
34751 * pe-dll.c (pe_process_import_defs): Use string already formed
34812 for a single char, or a two char string.
34911 [gdb/dap] Disable DAP for python <= 3.5
34912 DAP requires python module typing, which is supported starting python 3.5.
34915 - disabling the dap interpreter for python version < 3.5
34916 - returning 0 in allow_dap_tests for python version < 3.5
35070 that VSCode will not report the debug session as over unless this is
35164 …p_debug_symbols_for_elf_relocatable): Do not add sections containing the string "debug_" to the li…
36595 [gdb/testsuite] Fix gdb.python/py-thread-exited.exp
36596 Two fixes in gdb.python/py-thread-exited.exp:
36700 consequently we do not skip the breakpoint in main, and also don't run into
36750 [gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2 -flto=auto and gcc 7.5.0 some more
36752 gdb.gdb/python-helper.exp I run into:
36762 (outer-gdb) FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb
36766 in commit 0d332f11122 ("[gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2
36780 and in gdb/python/py-tui.c:
36794 - then gdb/python/py-tui.c.
36796 So when running test-case gdb.python/tui-window-factory.exp, we see the
36824 [gdb/testsuite] Fix regexps in gdb.base/step-over-syscall.exp
36825 When running test-case gdb.base/step-over-syscall.exp without glibc debuginfo
36832 (gdb) PASS: gdb.base/step-over-syscall.exp: vfork: displaced=off: \
36843 (gdb) FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=off: \
36924 std::string. Return section name for STT_SECTION symbols with
36938 bpf: format not a string literal
37525 Remove redundant @findex from python.texi
37527 @defun. This patch removes all such uses from python.texi, plus a
37535 I noticed that a doc string py-type.c says "an signed".
37553 patch updates gdb to return this, and simply uses a hex string of the
37922 (gdb) python i = gdb.selected_inferior ()
37923 (gdb) python i.read_memory (4,4)
37957 New test added to gdb.python/py-inferior.exp, exercising
37992 [gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2 -flto=auto and gcc 7.5.0
38001 (outer-gdb) FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again
38266 1. The user performs a 'next' over a vfork, GDB stop in the vfork
38284 proceed function we iterate over all threads that match the resume
38286 proceed_resume_thread_checked. One of the threads we iterate over
38301 8. Back in the proceed function GDB continues to iterate over all
38447 already resumed, and is not in the step-over chain, however, the third
39093 exceed 16 symbols (by well over 3 times with gcc-11).
39472 Note that this test also shows that string-printing is incorrect in
39527 Fix execute_frame_filters doc string
39528 When reading the doc string for execute_frame_filters, I wasn't sure
39530 string to reflect my findings, and also fixes an existing typo.
39620 eval_result_names array does not include a string for either
39625 string for every possible error.
39631 the enum eval_result_type and the eval_result_names string array.
39632 Doing this means it is impossible to have a missing error string in
39903 load a complete string from the inferior into a GDB buffer.
39916 inferior memory to figure out how long the string actually is, we just
39918 user an error we can tell the user how big the string actually is,
39941 However, in this case we are building a string, and (at least for
39942 GCC), the std::string type has a small string optimisation, where
39946 string, we're just constructing a printf format specifier for a hex
39949 small string buffer.
39952 std::string. This shouldn't result (normally) in any additional
39976 this case we are reading an arbitrary string from the inferior. This
39984 setting as we load the string to stop GDB crashing if a corrupted
39997 const wchar_t wide_str[] = L"wide string";
40020 expected 'wide string' output.
40041 to print an empty string.
40344 as well, to continue to allow sharing of the string literals.
41308 string directive.
41354 * riscv-dis.c (print_insn_args): Add 'l' as new format string
41373 We picked up support for a few new extensions over the last weeks
41424 (validate_riscv_insn): Add 'Wfv' as new format string directive.
41512 new format string directive 'Wfv'.
41521 strings: Improve code to detect excessively large minimum string lengths.
41525 …gal memory access when running the strings program with an excessively lerge minimum string length.
41527 * strings.c (main): Check for an excessively large minimum string length.
42739 gdb/testsuite: fix gdb.python/py-unwind.exp with python >= 3.11
42846 DAP specifies a breakpoint's hitCondition as a string, meaning it is
42868 First of all, name of VariableReferences must always be of string type.
42880 object, not a string) and is not serializable by json.dumps.
43179 Use std::string in do_set_command
43180 do_set_command manually updates a string, only to copy it to a
43181 std::string and free the working copy. This patch changes this code
43182 to use std::string for everything, simplifying the code and removing a
43198 Use std::string in linux-osdata.c
43199 I found some code in linux-osdata that manually managed a string.
43200 Replacing this with std::string simplifies it.
43208 all the uses. This avoids some manual memory management. std::string
43216 Use std::string for MI token
43217 This changes the MI "token" to be a std::string, removing some manual
43281 1 - The Thread Object (the python type) checks it's own validity
43290 2 - A python user can hold a global reference to an exiting thread. Thus
43457 [gdb/testsuite] Remove f-string in gdb.python/py-unwind.py
43458 on openSUSE Leap 42.3, with python 3.4, I run into a
43459 "SyntaxError: invalid syntax" due to usage of an f-string in test-case
43460 gdb.python/py-unwind.py.
43462 Fix this by using string concatenation using '+' instead.
43690 [gdb/testsuite] Fix gdb.base/step-over-exit.exp with glibc debuginfo
43691 In test-case gdb.base/step-over-exit.exp, we set a breakpoint on _exit and
43696 Thread 2.1 "step-over-exit" hit Breakpoint 2.2, 0x00007ffff7d46aee in \
43698 (gdb) PASS: gdb.base/step-over-exit.exp: continue to exit
43702 Thread 2.1 "step-over-exit" hit Breakpoint 2.2, 0xf7d84c25 in _exit () from \
43704 (gdb) PASS: gdb.base/step-over-exit.exp: continue to exit
43710 Thread 2.1 "step-over-exit" hit Breakpoint 2.2, \
43714 (gdb) PASS: gdb.base/step-over-exit.exp: continue to exit
43718 Thread 2.1 "step-over-exit" hit Breakpoint 2.2, _Exit () at \
43721 (gdb) FAIL: gdb.base/step-over-exit.exp: continue to exit
43875 [gdb/testsuite] Fix gdb.dap/type_check.exp with older python
43876 On openSUSE Leap 15.4 with system python 3.6, I run into:
43878 (gdb) python check_everything()^M
44212 Transfer ownership of exception string to ada_catchpoint
44214 ownership of the exception string can be transferred to the catchpoint
44233 [gdb/testsuite] Relax breakpoint count check in gdb.python/py-rbreak.exp
44236 (gdb) PASS: gdb.python/py-rbreak.exp: nosharedlibrary
44242 (gdb) FAIL: gdb.python/py-rbreak.exp: check number of returned breakpoints is 11
44297 [gdb/tui] Replace macro HELP_ATTRIBUTE_MODE with std::string
44298 Replace macro HELP_ATTRIBUTE_MODE with a std::string.
44362 <468f2> DW_AT_name : (indirect string, offset: 0x4781): jq_util_input_next_input
44371 <46922> DW_AT_name : (indirect string, offset: 0x8cb): value
44641 gdb: fix ASan failure after recent string changes
44650 was triggered by gdb.base/internal-string-values.exp:
44652 (gdb) PASS: gdb.base/internal-string-values.exp: test_setting: all langs: lang=ada: ptype "foo"
44653 print $_gdb_maint_setting("test-settings string")
44721 value contents directly to a C-string, i.e. one that is assumed to
44725 string value will be represented just as it would be in the current
44726 language, so for Ada and Fortran the string will be an array of
44729 My proposed solution is to copy the string contents into a std::string
44730 object, and then use the std::string::c_str() value, this will ensure
45013 This patch fixes both of AArch64's and Arm's prologue skippers to not skip past
45028 [gdb/testsuite] Add missing wait in gdb.python/tui-window-disabled.exp
45030 gdb.python/tui-window-disabled.exp.
45036 Term::check_box "check for python window" 0 0 80 16
45045 [gdb/testsuite] Fix two typos in gdb.python/tui-window-disabled.exp
45046 Fix two typos in test-case gdb.python/tui-window-disabled.exp.
45307 a string that isn't null terminated. */
45341 Within py-value.c we have a null-terminated C-style string. We then
45342 pass a pointer to this string, along with the length of this
45343 string (so not including the null-character) to value_cstring.
45354 pushed to the inferior, and then read back as a C-style string, that
45377 character at the end of the string value it creates.
45392 (gdb) p $_gdb_maint_setting("test-settings string")
45408 appropriate value that represents the string. For C, C++, etc this
45409 will be a null-terminated string (by calling value_cstring), and for
45488 last string if that matters.
45791 [gdb/python] Fix doc string of valpy_const_value
45792 In gdb/python/py-value.c, in the value_object_methods array I noticed:
45804 [gdb/guile] Fix doc string for value-optimized-out?
45812 There's a typo in the doc string.
46234 …(coff_write_object_contents): Handle base64 encoding on PE. Also check for too large string table.
46243 python, btrace: Fix some small formatting issues.
46292 string, just as GDB would for a 'print' command, e.g.:
46321 string type. When we try to print this we call value_as_address,
46322 which ends up trying to push the string into the inferior's address
46325 Clearly we could solve this problem, the string data exists in GDB, so
46370 The new %V format solves all these problems: the string is computed
46376 print the string representation of flag enums, so given:
46410 When dprintf-style is 'call' the format string and arguments are
46416 any restrictions on the format string when operating in 'call' style.
46425 process the format string and send the dprintf command to the remote,
46689 over all UIs and calls the signal_received method on the interpreter.
46696 observer. These observer go over all UIs, and, for those that have a
46699 After this patch, we have just one "loop over all UIs", inside
46732 configuration string.
47329 x86: disassembling over-long insns
47944 than a string. This is done by implementing a new ui_out subclass
47972 accessor. It also changes this member to be a std::string. This
47982 currently that is simply emitted as a string. However, it's
48251 Tested by re-running the TUI test-cases (gdb.tui/*.exp and gdb.python/tui*.exp)
48259 Tested by re-running the TUI test-cases (gdb.tui/*.exp and gdb.python/tui*.exp)
48367 original command string to lookup the command again after its execution.
48388 command because the original command string is gone.
48391 original command string for the sole purpose of using it after command
48527 the string in breakpoint.c,
48542 gdb/testsuite: handle older Python versions in gdb.python/py-disasm.exp
48549 gdb/python: extend the Python Disassembler API to allow for styling
48565 tests in gdb.python/py-disasm.exp now pass.
48758 set expected_lbound $expect_out(1,string)
48907 Tested by re-running the TUI test-cases (gdb.tui/*.exp and gdb.python/tui*.exp)
48992 "&str" is an important type in Rust -- it's the type of string
49123 gdb/testsuite: fix formatting of gdb.python/py-disasm.py
49124 Run black on gdb.python/py-disasm.py file and commit the changes.
49134 gdb.python/py-function.exp, and that still passes after this change,
49210 gdb/python: extend the Python Disassembler API to allow for styling
49218 string of their choosing, this string then became the disassembled
49224 string. This string was then returned from the builtin_disassemble
49225 call, and the user could modify or extend this string as needed.
49250 libopcodes and building a single string, we will now create either a
49280 that creates a DisassemblerResult using a single string immediately
49296 DisassemblerAddressPart into a string. To do that we need to call
49304 passed over each time. I implemented both solutions (the one
49313 gdb/python: rework how the disassembler API reads the result object
49407 prints complete string, which is not what the user asked for.
49495 the number to go over the current maximum. This bumps the number.
49506 gdb: remove unnecessary call to std::string constructor
49507 I spotted this explicit call to std::string, which creates an
49508 unnecessary temporary extra std::string, while calling emplace_back.
49553 gdb/python: implement DisassemblerResult.__str__ method
49555 as the DisassemblerResult.string attribute, but can be useful
49562 gdb/python: implement __repr__ methods for py-disasm.c types
49938 PR python/29603.
49949 inappropriate, since `breakpoint_auto_delete' goes over all breakpoints
50558 iterate over an objfile's sections, so this patch renames the existing
50609 gdb/python: add mechanism to manage Python initialization functions
50610 Currently, when we add a new python sub-system to GDB,
50613 function do_start_initialization in python.c.
50617 from finalize_python which is also in python.c.
50621 no longer require changes to python.c or python-internal.h, instead,
50626 new class gdbpy_initialize_file in python-internal.h. This class
50634 Now from python.c we can call static functions on the
50655 protection I guess we'd need to run all gdb.python/*.exp tests with
50693 doesn't care. Also, as expect is happy to skip non-matched output
50695 skip over it before matching the rest. As such, this leading
50714 gdb.python/python.exp
50727 [gdb/testsuite] Generate long string in gdb.base/page.exp
50730 set fours [string repeat 4 40]
50737 Summarize the long string in the same way using string repeat:
50739 [list 1\r\n 2\r\n 3\r\n [string repeat 4 30]]
50760 string, including FILENAME, and also removes some uses of '.*' to make
50772 <92> DW_AT_linkage_name: (indirect string, offset: 0x156): _ZN9container8tlsvar_0E
50802 This simplifies auto_load_expand_dir_vars to first split the string,
51898 PR 13098 explains that if a user attempts to use a string with either
51911 as a string is TYPE_CODE_ARRAY but it's lval type is not_lval.
51913 printf_c_string will only attempt to print a string from the value's
51915 type is considered a string type:
51924 Otherwise, it attempts to read the value of the string from the target's
51960 patch removes the cases I found in python.texi. I also renamed some
52194 also added a skip-warning case in the first discard case, whose
52281 is the empty string (as the command itself is empty), but still
52424 return $expect_out(1,string)
52456 return $expect_out(1,string)
52648 [gdb/tui] Fix length of status line string
52651 + std::string string_val = string.release ();
52653 without updating subsequent uses of string.size (), which returns 0 after the
52654 string.release () call.
52657 - using string_val.size () instead of string.size (), and
52857 and there's also no reason to make the involved string literals longer
52876 because the string we're trying to match is split over two lines:
53011 over two lines:
53037 because it tries to match "(gdb) $cmd" but $cmd is split over two lines:
53089 when running the TUI testsuite (gdb.tui/*.exp and gdb.python/tui*.exp).
53112 [gdb/testsuite] Fix auto-indent in gdb.gdb/python-helper.exp
53113 When editing gdb.gdb/python-helper.exp, auto-indent is broken in my editor
53138 [gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2 -flto
53142 FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb
53143 FAIL: gdb.gdb/python-helper.exp: print integer from DWARF info
53144 FAIL: gdb.gdb/python-helper.exp: print *type->main_type
53153 (outer-gdb) FAIL: gdb.gdb/python-helper.exp: print *type->main_type
53270 [gdb/testsuite] Don't use string cat in gdb.dwarf2/dw2-abs-hi-pc.exp
53271 Test-case gdb.dwarf2/dw2-abs-hi-pc.exp uses string cat:
53273 set sources [lmap i $sources { string cat "${srcdir}/${subdir}/" $i }]
53334 "string is entier $num"
53397 Regenerated macro_op_32.d and add skip loongarch64-*-*.
53475 - Adjust add_set_language_command to hard-code the "auto" string,
53990 string sections.
54054 to the function need to be aware that due to the potential of string
54061 x86: parse_register() must not alter the parsed string
54068 The problem instead is that parse_register() alters the string handed to
54071 of the incoming string before invoking that function.
54074 string is const-qualified to signal that the string isn't altered, but
54081 x86: parse_real_register() does not alter the parsed string
54082 Follow the model of strtol() et al - input string is const-qualified to
54083 signal that the string isn't altered, but the returned "end" pointer is
54102 PowerPC: fix _Float128 type output string
54202 * dwarf.c (fetch_indexed_string): Sanity check string index.
54456 the PC after a displaced step over the fork syscall. So
54616 0 1 (indirect line string, offset: 0x2d):
54701 pauth: Create new feature string for pauth to prevent crashing older gdb's
54703 a target reports the pauth feature string in the target description and also
54710 QEMU has postponed inclusion of the pauth feature string in version 8, and
54717 This new feature string is org.gnu.gdb.aarch64.pauth_v2, and should be used
54721 gdb/gdbserver will still emit the old feature string for Linux since it doesn't
54769 # IHEX and TEKHEX. We skip those tests then.
54815 targets in this testsuite, use the "is64bitonly" flag to skip those
55055 string "[ No Assembly Available ]" ends up in that same spot:
55084 over.
55251 Fix an illegal memorty access when running gprof over corrupt data.
55749 gdb/python: allow Frame.read_var to accept named arguments
55755 either a gdb.Symbol or a string, while the second, optional, argument
55762 (gdb) python print(gdb.selected_frame().read_var("a1", "xxx"))
55764 File "<string>", line 1, in <module>
55771 (gdb) python print(gdb.selected_frame().read_var("a1", "xxx"))
55773 File "<string>", line 1, in <module>
55794 (gdb) python print(gdb.selected_frame().read_var(123))
55796 File "<string>", line 1, in <module>
55797 TypeError: Argument must be a symbol or string.
55803 (gdb) python print(gdb.selected_frame().read_var(123))
55805 File "<string>", line 1, in <module>
55817 gdb/python: convert Frame.read_register to take named arguments
55836 gdb/python: have PendingFrame methods accept keyword arguments
55860 gdb/python: have UnwindInfo.add_saved_register accept named args
56025 can correctly handle displaced stepping over a single instruction that
56092 (stab_push_string): Don't strdup string. Use it thoughout
56132 PASS: gdb.asm/asm-source.exp: next over macro
56150 FAIL: gdb.asm/asm-source.exp: next over foo3 (the program is no longer running)
56234 under bfd/po/, i.e. in maintainer mode.
56261 code still does that but copies over to bfd_alloc memory when
56284 fields over to debug_xalloc memory.
56285 (parse_coff_enum_type): Copy names and vals over the
56300 for string passed to debug_start_source and push_bincl. Copy
56980 gdb/testsuite: fix failure in gdb.python/py-unwind.exp
56986 gdb/python: make the gdb.unwinder.Unwinder class more robust
56994 (gdb) python global_test_unwinder.name = "foo"
56996 File "<string>", line 1, in <module>
57004 (gdb) python global_test_unwinder.name = "foo"
57006 File "<string>", line 1, in <module>
57039 A case of a string section ending with an unterminated string. Fix it
57044 to terminate string sections with a NUL. Adjust invocation.
57063 debug info. Necessary if we are to fuss over freeing up memory before
57074 stab string passed to parse_stab. Free stab string when
57078 * stabs.c (parse_stab): Add string_used param. Set if string
57922 errors still win over parsing errors, and their relative priorities
57995 range needs its own hard-coded string, which is a bit cumbersome
58223 ZA accesses. That's a bit over the top for one offset check, but the
58412 gdb/python: Add new gdb.unwinder.FrameId class
58437 gdb/python: Allow gdb.UnwindInfo to be created with non gdb.Value args
58527 While refactoring some other code in gdb/python/* I wanted to merge
58555 gdb/python: remove Py_TPFLAGS_BASETYPE from gdb.UnwindInfo
58580 gdb/python: add __repr__ for PendingFrame and UnwindInfo
58589 gdb/python: add some additional methods to gdb.PendingFrame
58616 - gdb.PendingFrame.language: Return a string containing the
58628 In every case I've just copied the implementation over from gdb.Frame
58636 gdb/python/lib/command/unwinders.py:
58680 gdb/python: add PENDING_FRAMEPY_REQUIRE_VALID macro in py-unwind.c
58713 gdb/python: remove unneeded nullptr check in frapy_block
58714 Spotted a redundant nullptr check in python/py-frame.c in the function
58725 gdb/python: make the gdb.unwinder.Unwinder class more robust
58734 2. We now validate that the name is a string in the
58738 output (how to display a non-string name for an unwinder?),
59230 complaints about it over the years. This patch changes varobj to emit
59231 this string when possible, and updates the test suite.
59242 reason string.
59260 [gdb/testsuite] Fix gdb.server/server-kill-python.exp for remote host
59261 Fix test-case gdb.server/server-kill-python.exp for remote host using
59575 patch later in the step-over-{thread-exit,clone] series will want to
59620 would miss the data directory (which is listed as the reason to skip
59626 It seems easier to just skip this on remote host.
59977 Add an option to the gold linker to put its version string into the .comment section.
59980 …* layout.cc (Layout::create_gold_note): If linker-version is enabled put the version string into t…
60149 string, so I just spent ten minutes auditing for obvious memory leaks
60152 a new string, and not so easily leakable).
60163 over multiple calls).
60388 increment string_ptr to end of new string.
60427 Fix this by only adding the quotes in mi_expect_stop if the string doesn't
60516 Fix minor grammar issue in python.texi
60745 Sanity check coff-sh and coff-mcore sym string offset
60747 string offset when setting up name for use by error messages.
60752 PR17910 sym string offset check
60755 can simplify the sym string offset check. This is just a tidy.
60762 check sym string offset.
60972 Update python-helper.exp for type allocation changes
60973 The type allocation changes introduced a failure in python-helper.exp
61042 eventually calls symbol_find_demangled_name, which loops over all
61109 skipping over template parameters. This allows GDB to match the
61112 that it has skipped over inside the completion_match_for_lcd object
61125 match string, and the full symbol name within the
61137 | | '--- completion match string
61138 | '---skip range
61142 string using the completion match string (parse), but excluding the
61143 skip range, as the stored skip range is before the start of the
61144 completion match string, then GDB tries to do some weird string
61150 the symbol, or reject the symbol without storing a skip range.
61190 '<int>' template argument will be added as a skip range. When GDB
61195 Again, GDB matches the 'foo', and now adds '<double>' as a skip
61198 place as a skip region, even though this occurs before the start of
61199 our match string, and this will cause GDB to crash.
61221 the skip ranges relate to the match pointer.
61354 completer to pass invalid arguments to string::append.
61463 Regen ld/po/BLD-POTFILES.in
61782 returned true before. This made update_global_location_list skip the
61875 optional CURRENT string. The default CURRENT string is set to "\}" to work
62029 But rather than manually adding escapes in a string, add a new proc
62412 * testsuite/ld-scripts/ld-version-2.d: Don't skip ft32 or pru.
62449 zero size string section.
62654 Prevent an over large memory allocation in readelf when parsing a corrupt DWARF file.
62886 - If the Value has an 'invalid' field that is a string, use that for
62939 either True, False, or a string.
62942 and for the 'invalid' property to be a string.
62947 Allowing a component to have both a predicate and an 'invalid' string
62966 predicate field set to True and the invalid field set to a string.
63012 and set its invalid attribute to a string.
63098 [gdb/testsuite] Fix gdb.python/tui-window-factory.exp for remote host
63099 When running gdb.python/tui-window.exp with host board
63102 FAIL: gdb.python/tui-window-factory.exp: msg_2: \
63114 [gdb/testsuite] Fix gdb.python/tui-window.exp for remote host
63115 When running gdb.python/tui-window.exp with host board
63118 UNSUPPORTED: gdb.python/tui-window.exp: TUI not supported
63119 FAIL: gdb.python/tui-window.exp: test title
63279 [gdb/obvious]: fix python formatting for test gdb.python/py-typeprint.py
63280 python black formatter was complaining about the formatting of
63281 gdb.python/py-typeprint.py, so this commit corrects it.
63286 PR python/17136 reported an unhandled exception when using typeprinters
63347 string if the directoty table has relative names.
63509 [gdb/testsuite] Fix gdb.python/py-completion.exp
63510 With test-case gdb.python/py-completion.exp and target board
63513 (gdb) PASS: gdb.python/py-completion.exp: discard #2
63514 completefilecommandcond $outputs/gdb.python/py-completion/py-completion-t^G\
63515 PASS: gdb.python/py-completion.exp: completefilecommandcond completion
63524 (gdb) PASS: gdb.python/py-completion.exp: discard #2
63525 completefilecommandcond $outputs/gdb.python/py-completion/py-completion-t^G\
63526 PASS: gdb.python/py-completion.exp: completefilecommandcond completion
63529 (gdb) PASS: gdb.python/py-completion.exp: discard #3
63539 [gdb/testsuite] Fix gdb.python/py-cmd.exp
63543 The test-case gdb.python/py-cmd.exp passes, but the handling of the
63550 $ppPASS: gdb.python/py-cmd.exp: verify pagination from test_multiline
63558 $ppPASS: gdb.python/py-cmd.exp: verify pagination from test_multiline: q
63582 $ppPASS: gdb.python/py-cmd.exp: verify pagination from test_multiline
63585 (gdb) PASS: gdb.python/py-cmd.exp: verify pagination from test_multiline: q
63598 With test-case gdb.python/py-autoloaded-pretty-printers-in-newobjfile-event.exp
63629 [gdb/testsuite] Fix gdb.python/py-event-load.exp for remote target
63630 Fix test-case gdb.python/py-event-load.exp for target board
63774 Fix another case of oss-fuzz tripping over gas static state,
63775 ie. starting over testing another input file with rubbish left
63994 Likewise in gdb.server/server-kill-python.exp.
64114 the bfd over to in-memory.
64117 Correct test target/skip lines to fix fails on alpha-dec-vms,
64227 a literal string, so has static storage duration. If we change
64228 interp_lookup to pass that name instead of the string that it receives
64233 Change interp::m_name to be a `const char *` rather than an std::string.
64326 [gdb/testsuite] Fix gdb.base/skip-solib.exp for remote target
64327 Fix test-case gdb.base/skip-solib.exp for target board
64334 [gdb/testsuite] Use shlib gdb_compile option in gdb.base/skip-solib.exp
64335 In test-case gdb.base/skip-solib.exp the linking against a shared library is
64657 gdb/python: Fix --disable-tui build
64658 As of 2023-02-13 "gdb/python: deallocate tui window factories at Python
64661 $src/gdb/python/py-tui.c: In function ‘void gdbpy_finalize_tui()’:
64662 $src/gdb/python/py-tui.c:621:3: error: ‘gdbpy_tui_window_maker’ has not been declared
64921 and gdb.threads/detach-step-over.exp). Those were not problematic on my
64980 gdb/python: replace strlen call with std::string::size call
64981 Small cleanup to use std::string::size instead of calling strlen on
64982 the result of std::string::c_str.
65074 uninitialized bytes of field u over from the temporary object to the new
65254 * macro.c (macro_expand): Ensure input string buffer is not
65310 [gdb/testsuite] Add another xfail case in gdb.python/py-record-btrace.exp
65313 (gdb) PASS: gdb.python/py-record-btrace.exp: function call: \
65314 python print(c.prev)
65315 python print(c == c.next.prev)^M
65317 File "<string>", line 1, in <module>^M
65320 (gdb) FAIL: gdb.python/py-record-btrace.exp: function call: \
65321 python print(c == c.next.prev)
65325 python print(len(insn))^M
65391 [gdb/testsuite] Fix gdb.python/py-breakpoint.exp timeouts
65394 FAIL: gdb.python/py-breakpoint.exp: test_watchpoints: \
65396 FAIL: gdb.python/py-breakpoint.exp: test_bkpt_internal: \
65526 convert the thread_info* into a string.
65640 The script gdb.python/py-finish-breakpoint.exp had some regressions
65684 gdb.python/py-finish-breakpoint.exp test fully passing again.
65708 The failure is caused by the 'evaluated-by="host"' string, which only
65930 * ecofflink.c (mk_fdrtab): Sanity check string offsets.
66442 not look at get_last_target_status, but to instead iterate over the
66578 changes later in this series, and the step-over-thread-exit changes,
66711 gdb: make-target-delegates.py: make one string raw
67359 gdb, python: do minor modernization in execute_gdb_command
67419 strings: std::string of course, but also obstack and even objalloc
67420 from BFD and dyn-string from libiberty. The previous patches in this
67425 This changes top.c to use std::string rather than struct buffer. Like
67427 requires a copy of the string.
67430 This changes event-top.c to use std::string rather than struct buffer.
67431 This isn't completely ideal, in that it requires a copy of the string
67435 This changes handle_qxfer_threads, in gdbserver, to use std::string
67440 gdbserver, to use std::string rather than struct buffer.
67444 std::string rather than struct buffer.
67447 This changes tracefile-tfile.c to use std::string rather than struct
67606 Enhance better_fit() function to prefer function symbols over non-function symbols.
67668 (since 740b42ceb7c "gdb/python/mi: create MI commands using python").
67670 The problem today is the python/py-cmd.c file. It is included in the
67677 >>> python/py-micmd.o:(micmdpy_install_command(micmdpy_object*))
67679 The python/py-cmd.c file should be included in the build if both Python
68078 [gdb/testsuite] Require python in gdb.dap/basic-dap.exp
68079 When running test-case gdb.dap/basic-dap.exp with a gdb without python
68090 Fix this by requiring python in the test-case.
68092 Tested on x86_64-linux, both with a gdb without and with python.
68392 python NORMAL_FRAME
68425 python NORMAL_FRAME
68477 [gdb/testsuite] Add xfail case in gdb.python/py-record-btrace.exp
68480 gdb) PASS: gdb.python/py-record-btrace.exp: prepare record: stepi 100
68481 python insn = r.instruction_history^M
68483 (gdb) FAIL: gdb.python/py-record-btrace.exp: prepare record: python insn = r.i\
68845 We also skip calling pd_activate
69063 Therefore there shouldn't be any at the end of the format string.
69163 …quit_flag (extlang=0x558c68f81900 <extension_language_python>) at ../../src/gdb/python/python.c:288
69166 …er (this=0x7fff2b70bb90, gdbarch=0x558c6ab9eac0, language=0x0) at ../../src/gdb/python/python.c:212
69167 …0b00, addr=0x555555558014, len=4, data=0x558c6af8a610 "") at ../../src/gdb/python/py-inferior.c:146
69451 gdb.python/py-xmethods.exp testcase to make sure of that.
69464 After doing that, I decided to write a testcase that iterates over all
69837 gdb: use std::string for internalvar::name
69838 Change internalvar::name to std::string, automating memory management.
69887 I went over all @findex calls in the manual, and most are like the
69895 There are findex entries in annotate.texinfo,python.texi, and
69929 …uite/ld-elf/merge4b.s: Use .asciz instead of .string in order to avoid the special behaviour of th…
69956 gas: buffer_and_nest() needs to pass nul-terminated string to temp_ilp()
69963 properly use sb_terminate() to mark the end of the string. (Note that
70060 [gdb/testsuite] Add xfail in gdb.python/py-record-btrace.exp
70073 (gdb) python insn = r.instruction_history^M
70076 (gdb) FAIL: gdb.python/py-record-btrace.exp: prepare record: \
70077 python insn = r.instruction_history
70109 This inserts a zero-terminated string into the output at the place where it is used.
70613 gdb/python: deallocate tui window factories at Python shut down
70682 gdb/python: allow Python TUI windows to be replaced
70781 gdb/testsuite: handle differences in guile error string output
70805 updates the test regexp to handle this optional 'ERROR: ' string.
71023 In iterate_over_minimal_symbols we iterate over two hash tables (using
71041 skip any parameters in the demangled symbol name when checking for a
71044 once the string we are looking for ('foo' here) is exhausted, if we
71067 iterated over (in iterate_over_minimal_symbols), we only consider the
71241 triggered when the user enters a long command line, which wrapped over
71393 python NORMAL_FRAME
71739 Use std::string in main_info
71740 This changes main_info to use std::string. It removes some manual
71760 (PRMS: next over longjmp)
71790 (PRMS: next over longjmp)
71835 python NORMAL_FRAME
72145 pe_ILF_build_a_bfd converts an archive entry over to BFD_IN_MEMORY,
72534 is modified to skip sections that do not have this flag set.
73115 Move the implementation over to target_desc_info. Remove the
74113 string.
74191 support converting a given enum_flags specialization to string, we
74192 just need to implement a function that provides the enumerator->string
74204 static std::string
74215 .. and then to_string(SOME_FLAG2 | SOME_FLAG3) produces a string like
74219 new enumerator, then the string representation will pretty-print the
74244 index, with the other always being the search string.
74376 cluster, where you have full control over the servers installed), so I
74505 I noticed that iterating over the index yields non-const
74732 Now however, we sometimes only write a partial string to the pad,
74741 If we want to copy this to the pad, but skip the first 3 characters,
75028 Use clean_restart in gdb.python
75029 Change gdb.python to use clean_restart more consistently.
75167 read the string, at gdb.cp/cpexprs.exp.tcl:725. The "correct" variable
75237 string "2" in JSON. By converting to TCL dicts, we lose that
75560 FAIL: bar: instruction 5: [string equal $fid $::main_fid]
75563 FAIL: bar: instruction 6: [string equal $fid $::main_fid]
75662 FAIL: gdb.base/unwind-on-each-insn.exp: insn 7: [string equal $fid $main_fid]
76162 skip relocations that have addresses before the symbol, so that they
76179 left over from an earlier change. This patch moves the "!" inside the
76183 An earlier patch failed to update a string in allow_aarch64_sve_tests.
76615 My obvious fix is just to skip the fixup for base types larger than a
76673 string sections (i.e. pointing to zeros). It made bootstrap.exp fail
76692 Faster string merging
76701 The overall effect is less usage in libz and much faster string merging
76734 To amortize for the otherwise reduced folding of string literals by the
76735 linker, use att_names_seg[] in place of string literals in append_seg()
76752 string table instead. While doing this also
76760 When generating the mnemonic string table we already set up an
76765 Compact the mnemonic string table such that the tails of longer
76774 efficient. With overall string size presently just slightly over 20k,
76822 GDB/testsuite: Expand for character string limiting options
76838 There are new tests for Ada and Pascal, as the string printing code for
76839 these languages is different than the generic string printing code used
76840 by other languages. Modula2 also has different string printing code,
76843 string printing.
76850 GDB: Add a character string limiting option
76854 which is used for controlling how many characters of a string are
76858 control over how data is printed, reflecting that, although strings can
76890 Limit on string chars or array elements to print is 200.
76901 This setting also applies to string chars when "print characters"
77046 [gdb/testsuite] Fix gdb.python/py-value-cc.exp for big endian
77049 (gdb) python print(u[u_fields[0]])^M
77051 (gdb) PASS: gdb.python/py-value-cc.exp: u's first field via field
77052 python print(u[u_fields[1]])^M
77054 (gdb) FAIL: gdb.python/py-value-cc.exp: u's second field via field
77147 incrementally change targets over to simple bfd_install_relocation
77421 Do the same fix in gdb.gdb/python-helper.exp.
77722 we will trip over it.
78102 Calling strncat with the size of the src string is not so meaningful.
78240 libctf: skip the testsuite from inside dejagnu
79298 * po/SRC-POTFILES.in: Regenerate.
79442 * readelf.c (process_dynamic_section): Correct format string.
79752 [gdb/python] Avoid queue.SimpleQueue for python 3.6
79753 On openSUSE Leap 15.4 with python 3.6, the gdb.dap/basic-dap.exp test-case
79763 set length $expect_out(1,string)
79776 at gdb/python/py-utils.c:396
79782 The python class queue.SimpleQueue was introduced in python 3.7.
79784 Fix this by falling back to queue.Queue for python <= 3.6.
80412 The cced7cacecad104fff0 ("gdb: preserve `|` in connection details string")
80430 that this string is being passed verbatim to gdbserver -- which seems
80443 [gdb/testsuite] Fix gdb.python/py-breakpoint.exp with libstdc++ debug info
80446 (gdb) python hbp1 = gdb.Breakpoint("add", type=gdb.BP_HARDWARE_BREAKPOINT)^M
80448 (gdb) FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: \
80453 $ gdb -q -batch outputs/gdb.python/py-breakpoint/py-breakpoint \
80528 cpu port (IQ10BF?), but that was over 20 years ago, and that port has
80580 string "Copyright (c) 2006, 2012, Oracle and/or its affiliates. All
80587 embedded cr in binutils/testsuite/binutils-all/ar.exp string match.
80689 [gdb/python] Fix gdb.python/py-finish-breakpoint2.exp for -m32
80702 (gdb) FAIL: gdb.python/py-finish-breakpoint2.exp: \
80764 (gdb) FAIL: gdb.python/py-finish-breakpoint2.exp: \
80775 (gdb) PASS: gdb.python/py-finish-breakpoint2.exp: \
80793 PR python/27247
81156 the m16 & igen builds over too.
81269 This code loops over available cpus with "c", but then looks up the
81279 This code loops over available cpus with "c", but then looks up the
81477 no need to force everyone to pull them in. A lot of this is a hold over
81624 ld: Generate PDB string table
81719 RISC-V: Relax the order checking for the architecture string
81865 (dump_sframe_func_with_fres): Emit a string if B key is used.
82239 format string to reduce translation work. elf64-ppc.c loses the
82365 need custom state over to the new layout. This includes mn10300 that,
82403 /bin/sh ../../gdb/../mkinstalldirs /src/gdb/inst/share/gdb/python/gdb
82445 Regen opcodes/po/POTFILES.in
82577 gprofng/testsuite: skip Java test without JDK
82723 to a string buffer, extends per_xvec_warn to support multiple errors/
82789 mangled RA, use string "[s]" in the output to indicate that the return
82888 [gdb/testsuite] Fix race in gdb.threads/detach-step-over.exp
82891 FAIL: gdb.threads/detach-step-over.exp: \
82942 python frame = gdb.selected_frame()
82943 python frame_pc = frame.pc()
82944 python block = gdb.current_progspace().block_for_pc(frame_pc)
82945 python symbol,_ = gdb.lookup_symbol('some_label', block, gdb.SYMBOL_LABEL_DOMAIN)
82946 python print(str(symbol.value()))
82978 (gdb) python print(str(symbol.value()))
82983 (gdb) python print(str(symbol.value().type))
82988 gdb: convert linux-osdata.c from buffer to std::string
82989 Replace the use of struct buffer in linux-osdata.c with std::string.
83000 that appends to an std::string, rather than a struct buffer. Call it
83001 "string" rather than "buffer" since it operates on an std::string rather
83003 appends to and does not replace the string's content. This mirrors
83017 gdb: clean up some inefficient std::string usage
83025 Introduced a couple of inefficient uses of std::string, both of which
83108 The passed in string can't be nullptr, it makes more sense to pass in a
83136 command_line_input and other related functions to return an std::string,
83138 don't need to return an allocated string, so this this an unnecessary
83139 pessimization. I changed it to passing in a reference to an std::string
83142 pointers to the C string inside. The callees that don't need to return
83149 pointer to an std::string's internal buffer to readline's history_value
83151 does not modify the input string, because I was able to change it (with
83226 string utility functions in common-utils.h; and furthermore that streq
83267 wraps all the logic for creating a string that describes a target
83326 the new assert will fire in, e.g. the gdb.python/py-inferior.exp test.
83377 This commit fixes a crash in gdb.python/py-inferior.exp where GDB
83721 string 'faked for "readnow"' in the output. This is implemented in
83733 gdb.python/py-symbol.exp
83742 for "readnow"' string, as a consequence the testsuite can no longer
83769 RISC-V: Add string length check for operands in AS
83782 * config/tc-riscv.c (arg_lookup): Add string length check for operands.
84057 [gdb/testsuite] Fix gdb.python/py-disasm.exp on s390x
84073 (gdb) FAIL: gdb.python/py-disasm.exp: global_disassembler=: disassemble test
84138 * python/py-breakpoint.c (gdbpy_breakpoint_cond_says_stop): Renamed
84348 The need for them on the operand-less string insns has gone away with
84417 Note that with the dropped CMPSD and MOVSD Intel Syntax string insn
84502 very little over half (not even accounting for any overhead
84565 (gdb) PASS: gdb.guile/scm-lazy-string.exp: bad length
84568 (gdb) FAIL: gdb.guile/scm-lazy-string.exp: ptr: print ptr
84574 +file scm-lazy-string
84576 Breakpoint 1 at 0x4005d2: file scm-lazy-string.c, line 23.
84579 Breakpoint 1, main () at scm-lazy-string.c:23
84597 when stepping over this insn:
84991 gdb: skip objfiles with no BFD in DWARF unwinder
85001 back to DWARF unwinder which in turn iterates over objfiles. Since the
85190 PASS: gdb.base/longjmp.exp: next over setjmp (1)
85192 PASS: gdb.base/longjmp.exp: next over setjmp (2)
85212 (gdb) PASS: gdb.base/longjmp.exp: next over longjmp(1)
85224 (gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1)
85237 (gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1)
85255 The next over the longjmp call at 4005e9 is supposed to stop at the longjmp
85762 PowerPC, fix gdb.reverse/finish-reverse-bkpt.exp and gdb.reverse/next-reverse-bkpt-over-sr.exp
85773 next-reverse-bpkt-over-sr.exp uses source file step-reverse.c A new
85775 next-reverse-bkpt-over-sr.exp. The new files use the new function
85786 gdb.reverse/next-reverse-bkpt-over-sr.exp.
85825 when looping over languages, the C++ case will canonicalize this type
85890 useful too, since we iterate over a potentially big number of index
85930 * po/POTFILES.in: Likewise.
86064 The problem is that we're using a hex string for the 128-bit IEEE quad long
86070 Fix this by using the hex string obtained by compiling test.c:
86157 statement we can actually pre-fill that one by going once over all input
86196 So we iterate over all sections of all files many many times (for each
86198 need the full iteration over all sections, only over all files), but
86436 gdb.python/py-objfile.exp accordingly.
86474 ERROR: Couldn't send python print(objfile.filename) to GDB.
86488 Couldn't send python print(objfile.filename) to GDB.
86489 UNRESOLVED: gdb.python/py-objfile.exp: objfile.filename after objfile is unloaded
86661 gdb/testsuite: remove use of then keyword from gdb.python/*.exp
86667 This commit removes all use of the 'then' keyword from the gdb.python/
86805 to throw an exception over libopcode code.
86882 such, an attempt to throw an exception over libopcodes code will cause
86915 gdb/python: avoid throwing an exception over libopcodes code
86950 …ff9ab9d2a8 "\220ӹ\232\377\177", len=1, info=0x7fff9ab9d558) at ../../src/gdb/python/py-disasm.c:510
86958 …assemble (self=0x7f2ab07f54d0, args=0x7f2ab0789790, kw=0x0) at ../../src/gdb/python/py-disasm.c:324
86962 … (gdbarch=0x5335560, memaddr=0x401195, info=0x7fff9ab9e3c8) at ../../src/gdb/python/py-disasm.c:783
87029 With this change in place the gdb.python/py-disasm.exp test should now
87510 using a modified version of the gdb.threads/detach-step-over.exp test
87513 In the gdb.threads/detach-step-over.exp test, we attach to a
87518 step-over for the conditional breakpoint in at least one thread.
87520 While detaching, if a step-over is in progress, then GDB has to
87521 complete the step over before we can detach. This involves calling
87571 gdb/testsuite: refactor gdb.threads/detach-step-over.exp
87572 Factor out some bits of gdb.threads/detach-step-over.exp to procs in
87581 gdb/testsuite: remove global declarations in gdb.threads/detach-step-over.exp
87830 …./gdb/testsuite/outputs/gdb.python/py-inferior-leak/gdb.log:4729:==3353335== definitely lost: 3…
88589 in string.h, which triggers a "shadows a global declaration" warning
88655 ERROR: Couldn't send python print(objfile.filename) to GDB.
88668 gdb_test "python print(objfile.filename)" "None" \
88685 Fix step-over-syscall.exp matching regexp for $bpnum.$locno matching
88686 step-over-syscall.exp has some specific tests for gdbserver.
88778 string is defined here
88997 are not being cleaned up after use, as reported in PR python/18655. This was
89413 Update ARM and AARCH64 to skip elf_backend_output_arch_local_syms when
89453 gdb/testsuite: fix failure in gdb.python/py-send-packet.exp
89455 target, the test gdb.python/py-send-packet.exp was failing:
89458 File "<string>", line 1, in <module>
89459 File "/tmp/build/gdb/testsuite/outputs/gdb.python/py-send-packet/py-send-packet.py",
89461 assert string == expected_result
89464 (gdb) FAIL: gdb.python/py-send-packet.exp: call python run_auxv_send_packet_test function
89475 want the actual string "\x000".
89493 After this the gdb.python/py-send-packet.exp test passes on AArch64
89507 gdb/fortran/testsuite: print values and types of string variables
89509 printing the value and type of a Fortran string defined using the
89515 The test also includes printing a string that includes some embedded
89564 …nction ‘virtual void procfs_target::create_inferior(const char*, const std::string&, char**, int)’:
89565 …t)’ output truncated before terminating nul copying as many bytes from a string as its length [-Ws…
91198 The python code maintains a list of threads for each inferior. This
91210 iterates over all remaining threads and marks each thread exited. This
91314 gdb/testsuite: skip gdb.cp/anon-struct.exp when using Clang
91559 The parser for boolean rules fails to skip over the , separator in
91885 testsuite/outputs/gdb.python/pretty-print-call-by-hand/pretty-print-call-by-hand \
91886 -x testsuite/outputs/gdb.python/pretty-print-call-by-hand/pretty-print-call-by-hand.py \
91891 …(/home/simark/src/binutils-gdb/gdb/testsuite/gdb.python/pretty-print-call-by-hand.c:41); saved rip…
91914 the gdb.python/pretty-print-call-by-hand.exp test to test that command.
91969 ld/testsuite: skip ld-size when -shared is not supported
92276 * elflink.c (elf_link_output_symstrtab): Don't skip local symbol
92320 iterate over these numbers to find the highest possible CPU id, and
92331 file from /proc or /sys and processes it as a string afterwards. I
92338 return an std::string, and because strtok doesn't play well with
92339 std::string (it requires a `char *`, std::string::c_str returns a `const
92340 char *`), change linux_common_core_of_thread to use std::string methods
92753 ld/testsuite: skip tests related to -shared when disabled
92778 an ISA string and/or disassembling, not to allow hard-float with RVE.
93048 PR record/29745, where we can't skip one funcion forward if we're using
93281 currently cannot). So switch it over to WITH_TRACE_ANY_P to simplify the
93680 opcodes/arm: don't pass non-string literal to printf like function
93689 string to the disassembler's fprintf_styled_func callback. This will
93693 …../../binutils-gdb/opcodes/arm-dis.c:6005:3: error: format not a string literal and no format argu…
93697 This commit fixes these by using "%s" as the format string.
93725 proposed solution is to initialize the reason variable to the string
93726 "??", this will silence the warning, and the "??" string should never
93739 contains a string that describes the assembler syntax of the
93761 'pld' is embedded within the assembler string. Some instructions also
93762 include comments within the assembler string, for example, also from
93802 of a 'base_style'. Every character from the assembler string will
94519 Commit 40f1a1a4564b ("RISC-V: Output mapping symbols with ISA string.")
94575 RISC-V: Output mapping symbols with ISA string.
94585 architecture string in the subset_list.
94587 architecture string.
94629 the architecture string once the ISA is different.
95581 ld/testsuite: skip ld-elf/exclude when -shared is not supported
95585 to skip for all targets without shared lib support.
95622 [gdb/testsuite] Add skip_python_tests in gdb.python/tui-window-names.exp
95623 I did a gdb build without python support, and during testing ran into FAILs in
95624 test-case gdb.python/tui-window-names.exp.
95681 FAIL: gdb.base/unwind-on-each-insn.exp - instruction 104340: [string equal $fid $main_fid]
95778 declaration, gdb can skip this type during lookups and when writing
95840 gdb/reverse: Fix stepping over recursive functions
95842 command "reverse next" to skip a recursive function, instead of skipping
95856 recursive function and attempt to both, skip it altogether, and to skip
95871 we were to attempt to skip that function, and this breakpoint should
95887 * po/hu.po: Updated Hungarian translation.
95892 Similarly to booleans and following the fix for PR python/29217 make
96022 gdb/python: break more dependencies between gdbpy_initialize_* functions
96024 explicit gdbpy_initialize_* calls from python.c and replace these
96046 python.c.
96059 gdb/python: break dependencies between gdbpy_initialize_* functions
96061 explicit gdbpy_initialize_* calls from python.c and replace these
96306 Regen ld/po/BLD-POTFILES.in
96443 This commit is mostly either changing the format string to match the
96460 This is a false positive - we over allocate engine_fn, and then only
96577 [gdb/testsuite] Fix ERROR in gdb.python/py-breakpoint.exp
96578 With test-case gdb.python/py-breakpoint.exp I run into:
96580 (gdb) ERROR: tcl error sourcing gdb.python/py-breakpoint.exp.
96631 PR python/16324 points out that comparing a frame id to null_frame_id
96688 gdb.python/py-breakpoint.exp
96789 provided (i.e. it is nullptr), iterate over objfiles in the initial
96822 iterate over objfiles and are not aware of linker namespaces.
96852 I stumbled over this while reviewing all objfiles traversals with regards
96864 Iterate over objfiles in search order using the objfile of the selected
96872 Iterate over objfile in search order using the objfile of the context
96883 gdb, python: use gdbarch_iterate_over_objfiles_in_search_order
96884 The implementation of gdb.lookup_objfile() iterates over all objfiles and
96885 compares their name or build id to the user-provided search string.
96896 When cleaning up after a compile command, we iterate over all objfiles and
97102 <1d3> DW_AT_linkage_name: (indirect string, offset: 0x106f): 11__mbstate_t
97394 some random string.
97415 set num_ran $expect_out(1,string)
97652 [gdb/testsuite] Drop unnecessary -Wl,-soname in gdb.base/skip-solib.exp
97653 I noticed in gdb.base/skip-solib.exp:
97664 outputs/gdb.base/skip-solib/skip-solib-lib.c.o -fdiagnostics-color=never \
97666 -o outputs/gdb.base/skip-solib/libskip-solib.so (timeout = 300)
98232 implementation-defined manner, the result with format string containing
98293 Also copy over config.acx.m4, and regenerate.
98514 Clang generates a warning if the format string of a printf-like function is
98551 Clang generates a warning if the format string of a printf-like function is
98563 Clang generates a warning if the format string of a printf-like function is
98578 Clang generates a warning if the format string of a printf-like function is
98590 Clang generates a warning if the format string of a printf-like function is
98602 Clang generates a warning if the format string of a printf-like function is
98614 Clang generates a warning if the format string of a printf-like function is
98626 Clang generates a warning if the format string of a printf-like function is
98737 gdb/testsuite: Fix formatting of python script
98738 The python black formatter was complaining about formatting on the
98739 script gdb.python/pretty-print-call-by-hand.py. This commit changed
98756 gdb_assert { [string equal $output "1"] }
98760 PASS: [string equal $output "1"]
98763 If we change the prefix string to a no-match, say "1 = ", and update the
98764 output string match accordingly, we get instead:
98767 FAIL: [string equal $output "\$1 = 1"]
98839 set code [catch {gdb_expect $code} string]
98880 for the string concatenation "\0" "1", gdb will print "\000\061" --
98913 generic_printstr prints an empty string like:
98945 if [string match "*\[\r\n\]" $command] {
99062 python/28856, that happened when printing frame arguments calls an
99084 This commit also adds a testcase that exercises the python/28856 bug with
99137 gdb/testsuite: use 'end' at the end of python blocks
99170 Plus copy over gcc's config/ax_cxx_compile_stdcxx.m4, then regenerate
99504 The format string is changed accordingly.
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.
99582 scanning of the operand string to find the matching opening parenthesis.
100371 returning the empty string.
100390 them with a return of the empty string.
100399 for the empty string.
100557 string.
100561 nullptr, or an empty string to indicate that a register is not
100565 and there are plenty of targets that return empty string in some
100577 string at this point, but that felt like a real hack, so I discarded
100587 nullptr OR the empty string to mean the same thing, so I wondered if
100600 API for gdbarch_register_name is to return an empty string for
100606 string.
101109 The problem is in matching this string:
101135 just for toolchains (if full ISA string is given by a vendor, we can
101221 The purpose of "i = staticp ? 0 : 1" is to skip the printing of the implicit
101611 gdb/testsuite: use gdb_test in gdb.gdb/python-helper.exp
101619 (outer-gdb) FAIL: gdb.gdb/python-helper.exp: pretty print type (timeout)
101634 When running gdb.gdb/python-helper.exp, I get some timeouts:
101640 FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb (timeout)
101668 binutils/testsuite: skip gentestdlls related tests if missing
101752 gdb/source.c: Fix undefined behaviour dereferencing empty string
101754 we end up trying to dereference the last character of an empty string
101755 with std::string::back, which results in undefined behaviour. A typical
101760 preceding the storage of the empty string is returned. The character
101763 we go on to call std::string::pop_back on the empty string which results
101792 "section extending past end of file", "corrupt string table index",
101971 +++ Inserting string '('
101973 +++ Inserted string '(', cursor: (17, 0) -> (17, 1)
101974 +++ Inserting string 'g'
101976 +++ Inserted string 'g', cursor: (17, 1) -> (17, 2)
101977 +++ Inserting string 'd'
101979 +++ Inserted string 'd', cursor: (17, 2) -> (17, 3)
101980 +++ Inserting string 'b'
101982 +++ Inserted string 'b', cursor: (17, 3) -> (17, 4)
101983 +++ Inserting string ')'
101985 +++ Inserted string ')', cursor: (17, 4) -> (17, 5)
101986 +++ Inserting string ' '
101988 +++ Inserted string ' ', cursor: (17, 5) -> (17, 6)
102387 gdb/python: restrict the names accepted by gdb.register_window_type
102453 gdb.base/skip.exp: Use finish to exit functions
102454 gdb.base/skip.exp was making use of a fixed number of step commands to
102460 Breakpoint 4, main () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:32
102465 (gdb) PASS: gdb.base/skip.exp: step after disabling 3: step 1
102467 foo () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:42
102469 (gdb) PASS: gdb.base/skip.exp: step after disabling 3: step 2
102471 main () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:34
102474 test_skip_file_and_function () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:59
102476 (gdb) FAIL: gdb.base/skip.exp: step after disabling 3: step 3
102478 test_skip () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:48
102480 (gdb) PASS: gdb.base/skip.exp: step after disabling 3: step 4
102482 test_skip_file_and_function () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:60
102484 (gdb) FAIL: gdb.base/skip.exp: step after disabling 3: step 5
102492 gdb_step_until is not feasible because we'd possibly gloss over stepping
102493 into baz and rendering the whole test useless. Instead, skip.exp now
102498 Breakpoint 4, main () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:32
102503 (gdb) PASS: gdb.base/skip.exp: step after disabling 3: step into bar
102506 main () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:32
102509 (gdb) PASS: gdb.base/skip.exp: step after disabling 3: return from bar
102511 foo () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:42
102513 (gdb) PASS: gdb.base/skip.exp: step after disabling 3: step into foo
102515 Run till exit from #0 foo () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:42
102516 main () at binutils-gdb/gdb/testsuite/gdb.base/skip.c:32
102519 (gdb) PASS: gdb.base/skip.exp: step after disabling 3: Return from foo
102522 (gdb) PASS: gdb.base/skip.exp: step after disabling 3: step and skip baz
102576 gdb/testsuite: fix testing gdb.base/skip-inline.exp with clang
102577 When testing gdb.base/skip-inline.exp using clang, we get failures
102591 Change gdb.base/skip-solib.exp deal with lack of epilogue information
102592 When running gdb.base/skip-solib.exp, the backtrace tests could fail with
102598 Breakpoint 1, main () at (...)/binutils-gdb/gdb/testsuite/gdb.base/skip-solib-main.c:5
102602 (gdb) PASS: gdb.base/skip-solib.exp: ignoring solib file: step
102607 (gdb) FAIL: gdb.base/skip-solib.exp: ignoring solib file: bt
102645 ld/testsuite: skip bootstrap.exp when OFILES are missing
102651 OFILES variable, skip bootstrap.exp if it doesn't exist.
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).
102853 This macro accesses indices 0 and 1 of the input string. However, `f`
102856 string, so in practice there's no harm. But as far as the string_view
102862 view over a null-terminated string. With that class, it would be
102934 flag when initial ISA string contains the 'Ztso' extension. However, GAS
102935 has a way to update the ISA string: ".option arch".
102963 name contains the DWARF name as a sub-string. Very likely the name
103235 gdb_bfd.c:1180:43: error: format string is not a string literal [-Werror,-Wformat-nonliteral]
103236 const std::string str = string_vprintf (fmt, ap_copy);
103310 ...in which over 900,000 BFD error messages are output when attaching
103313 …/libxul.so-100.0-2.fc35.x86_64.debug: attempt to load strings from a non-string section (number 38)
104988 gdb/python-config: replace deprecated distutils.sysconfig
104990 python-3.10.4, I see:
104992 checking for python... no
104994 …[...]/gdb/python/python-config.py:7: DeprecationWarning: The distutils package is deprecated and s…
104996 …[...]/gdb/python/python-config.py:7: DeprecationWarning: The distutils.sysconfig module is depreca…
104998 …[...]/gdb/python/python-config.py:7: DeprecationWarning: The distutils package is deprecated and s…
105000 …[...]/gdb/python/python-config.py:7: DeprecationWarning: The distutils.sysconfig module is depreca…
105002 …[...]/gdb/python/python-config.py:7: DeprecationWarning: The distutils package is deprecated and s…
105004 …[...]/gdb/python/python-config.py:7: DeprecationWarning: The distutils.sysconfig module is depreca…
105006 checking for python... yes
105009 removed in python-3.12.
105011 This patch migrates gdb/python/python-config.py from distutils.sysconfig
105015 python 3.2. Given that support for python < 3.2 has been removed by
105016 edae3fd6600f: "gdb/python: remove Python 2 support", this patch does not
105021 [1] https://peps.python.org/pep-0632/
105022 [2] https://docs.python.org/3/library/sysconfig.html
105360 value is a null-terminated string containing the name of the
105373 For unnamed namespaces dwarf2_name simply returns the constant string
105404 <47> DW_AT_name : (indirect string, offset: 0x63): f
105411 <5b> DW_AT_name : (indirect string, offset: 0x74): Foo<double, int, float>
105419 <6c> DW_AT_name : (indirect string, offset: 0x6c): B
105513 <39> DW_AT_linkage_name: (indirect string, offset: 0x39): _Z3fooif
105514 <3d> DW_AT_name : (indirect string, offset: 0x42): foo
105547 <39> DW_AT_name : (indirect string, offset: 0x37): foo
105671 (read_formatted_entries): Do not skip entry 0.
106536 from memory. GDB should not skip any instructions in this case.
107497 gas/Dwarf: properly skip zero-size functions
107502 time, in order to skip emitting any data for the function if the value
107949 string literals within with gettext macro.
108022 Augmentation string: 47 44 42 00 ("GDB")
108067 Augmentation string: 47 44 42 00 ("GDB")
108093 for a symbol error. If the symbol name is the last string in its
108226 over threads.
108228 Ensuring a fair distribution over the worker threads and main thread in terms
108373 (read_and_display_attr_value): Don't display string when
108381 in string.h, which triggers a "shadows a global declaration" warning.
108405 invoking mbstowc in order to check the validity of a wide string.
108451 are not interested) to seamlessly skip it without issues.
109065 assembler so downstream users wouldn't have to re-invent this over and
109066 over again.
109419 (what I witnessed all compilers do) the same string that was passed to
109830 into a string. Then, back in print_operands (aarch64-dis.c), the
109831 operand string is printed.
109833 Unfortunately, the string returned by aarch64_print_operand can be
109855 callback returns a string with special embedded markers that indicate
109877 an plain string.
110096 gdb/python: Add BreakpointLocation type
110097 PR python/18385
110192 source: file path and line number tuple: (string, long) / None
110218 struct "gdbpy_breakpoint_location_object" is found in python-internal.h
110581 This is done because those references might be used initialize a python
110583 to initialize the python context with default gdbarch and language_defn
110675 set/show python dont-write-bytecode fixes
110678 python modules when the "python dont-write-bytecode" setting
110686 https://docs.python.org/3/using/cmdline.html
110690 If this is set to a non-empty string, Python won't try to write
110694 an empty string check.
110697 "python dont-write-bytecode". The current doc was just a copy
110698 of that for set/show python ignore-environment.
110701 asked that the help text that I proposed for "set/show python
110707 gdb/python: fix invalid use disassemble_info::stream
110736 and causes the gdb.python/py-disasm.exp test to fail like this:
110738 …(gdb) PASS: gdb.python/py-disasm.exp: global_disassembler=GlobalPreInfoDisassembler: python add_gl…
110758 gdb.python/py-disasm.exp now passes.
111141 This patch adds a test case to try to clear an internal python
111659 [gdb/python] Fix typo in test_python
111662 Tested by running the selftest on x86_64-linux with python 3.11.
111666 [gdb/python] Fix python selftest with python 3.11
111667 With python 3.11 I noticed:
111669 $ gdb -q -batch -ex "maint selftest python"
111670 Running selftest python.
111671 Self test failed: self-test failed at gdb/python/python.c:2246
111678 $5 = "Traceback (most recent call last):\n File \"<string>\", line 0, \
111681 $6 = "Traceback (most recent call last):\n File \"<string>\", line 1, \
111877 This commit fixes a build error on machines lacking python headers
111910 https://github.com/python/cpython/issues/88279
111911 https://peps.python.org/pep-0587/
111912 https://docs.python.org/3.11/c-api/init_config.html
111998 step over the 3 lines below and land on the return statement. If
112154 from the expected python code format.
112372 * tc-arc.c (md_assembly): Update strspn string with the
112391 gdb/python: look for python, then python 3 at configure time
112393 python executable. For example, on my Fedora system the python2
112395 /usr/bin/python3, and the python-unversioned-command package provides
112396 /usr/bin/python, which picks between python2 and python3.
112400 Currently, when GDB configures, it looks for a 'python' executable.
112401 If non is found then GDB will be built without python support. Or the
112402 user needs to configure using --with-python=/usr/bin/python3.
112405 'python', and then 'python3'. Now, on a system that only has a
112407 to provide python support, no user supplied configure arguments are
112411 python-unversioned-command package, confirming that there is no longer
112412 a 'python' executable in my $PATH, and then rebuilding GDB from
112413 scratch. GDB with this patch has python support.
112448 of those handles 4 * 1817 == 7268, leaving 3 "left over" elements.
112456 Instead, distribute the left over elements over the worker threads, such that
112630 PR python/17291 asks for access to the current print options. While I
112844 * read.c (pseudo_set): Copy over entire O_register value.
113810 string. Values are similar, and in some cases not even a string.
113842 gas: use notes_calloc in string hash
113843 Using notes_calloc means all of the string hash table memory should
113865 gas: target string hash tables
113866 This allocates entries added to the string hash tables on the notes
113868 switch over the str_hash allocation to notes_calloc, which is why I
113869 haven't implemented deleting all the target string hash tables.
113872 notes obstack for string hash table entries.
113900 This tidies memory used by the two x86 gas string hash tables before
113906 for arc, but a later patch will move all the string hash memory to the
114040 macro.c: use string hash from hash.h for macro_hash
114062 read.c: use string hash from hash.h for po_hash
114073 free read_symbol_name string
114074 read_symbol_name mallocs the string it returns. Free it when done.
114148 PR python/27000 points out that gdb.block_for_pc will accept a Python
114163 PR python/29217 points out that gdb.parameter will return bool values,
114949 converting "skip" to bool and putting it earlier in a group of bitfields
115170 FAIL: gdb.base/early-init-file.exp: check startup version string has style \
115423 parentheses will no longer be a fixed string, so doing a full match will
115470 combined in a single string like this makes such styling harder.
115590 Re: ld/x86: skip p_align-1 tests with unsuitable compiler
115691 ld/x86: skip p_align-1 tests with unsuitable compiler
116026 Stop bogus warnings about DWARF indexed string offsets being too big.
116028 in string section as the length of every table in the section.
116033 [gdb/testsuite] Handle older python in gdb.python/py-send-packet.py
116034 With python 3.4, I run into:
116037 File "<string>", line 1, in <module>^M
116039 "outputs/gdb.python/py-send-packet/py-send-packet.py", line 128, in \
116045 while with python 3.6 this works fine.
116048 changing it into a string works:
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.
116166 But when trying to read the string offset at index 0 in the table (which
116265 Note that I didn't touch */po/*.po{,t} on the assumption that these
116480 lib/gdb.exp. In theory we could switch over all uses of gcc_compiled
116829 Use std::string for interpreter_p
116831 changes it to be a std::string instead, and removes some erroneous
116876 str_offsets_base to calculate the string offset.
116935 * testsuite/gas/riscv/h-ext-32.d: Added h to architecture string.
117235 gdb/python: Export nibbles to python layer
117531 && ![string equal $output "No MPX support\r\n"]]
117546 zero string terminator when fgets returns NULL.
117595 pass over FDE to cie->col_type[reg] if CIE specifies reg.
117598 call frame_need_space on second pass over FDE.
117624 While at it fixed format string for time-related types.
117636 PR python/28533 points out that the Python 'dont_repeat' documentation
117755 gdb/python: implement the print_insn extension language hook
117795 disassembler, it's really just a wrapper around a string (the text
117826 maint info python-disassemblers
117917 gdb/python: convert gdbpy_err_fetch to use gdbpy_ref
117973 string. Fix that by clearing u.str. The patch also adds missing
117980 (read_attribute_value): Clear u.str for indexed string forms when
118032 [gdb/testsuite] Handle unordered dict in gdb.python/py-mi-cmd.exp
118033 When running test-case gdb.python/py-mi-cmd.exp on openSUSE Leap 42.3 with
118034 python 3.4, I occasionally run into:
118043 FAIL: gdb.python/py-mi-cmd.exp: -pycmd dct (unexpected output)
118226 > Looking at elfcore.h, it seems to have not gotten changes made to elfcode.h over
118304 allocated string (that should be freed) by returning a char * rather
118326 (dwarf2_directive_loc): Free remap_debug_filename string.
118348 The problem is that the step is expected to step over the call to tcsetattr,
118414 Except over control registers, other registers, like gprs, hi, lo ...
118446 On openSUSE Leap 42.3 with python 3.4, I run into:
118448 (gdb) python import pygments^M
118450 File "<string>", line 1, in <module>^M
118453 (gdb) FAIL: gdb.base/style.exp: python import pygments
118454 ERROR: unexpected output from python import
118491 x86: avoid string copy when swapping Vex.W controlled operands
118776 [4] system.traceback.symbolic.value (system.address) return string at \
118818 What has happened, over time, is that these functions have been
119049 Then test_compiler_info will return an empty string. My assumption is
119051 the empty string hopefully will not match.
119070 Instead of using the empty string as the default language, and just
119087 passing the empty string to either get_compiler_info or
119115 The preferred way of getting the compiler string is via calling
119182 The perror_with_name function take a string, and adds ': <message>' to
119183 the end the string, so I don't think the string that we pass to
119225 be to move away from the operands being a single string that is built
119228 operand we would loop over the parts and print each part with the
119588 I noticed that solib_name_from_address returned a non-const string,
119596 _() around a string using in an error call.
119605 In skip_arch in gdb/selftest-arch.c we skip architecture fr300 because of
119627 varobj used to store 'print_value' as a C string, where NULL was a
119629 at some point this was changed to be a std::string, and so the code
119736 The stream() ui_file points into a string buffer, which the disassembler uses
119776 gdb/python: improve formatting of help text for user defined commands
119778 the test that was added (gdb.python/py-doc-reformat.exp) was missing a
119837 I've used as overflow string: "Integer literal is too large", based
120078 over all architectures.
120116 Fix this in print_one_insn_test, in the default case, by iterating over
120448 happen if the string starts in one file and finishes in another.
120456 sb_scrub_and_add_sb not draining input string buffer
120458 string buffer. If this happens for reasons explained in the comment,
120459 do_scrub_chars can leave pointers to the string buffer for the next
120461 that the behaviour for an empty string buffer is also changed,
120517 over all architectures.
120757 since derived_type contains a heap allocated string and the copy
120761 free on the heap allocated string which leads to a double free. Instead
120763 serve the test. The string is now just a const char* = ".." object
120884 to-be-completed string one can easily produce similar results:
120948 <30> DW_AT_name : (indirect string, ...): main
120951 <52> DW_AT_name : (indirect string, ...): argc
120954 <5e> DW_AT_name : (indirect string, ...): argv
120966 <80> DW_AT_name : (indirect string, ...): character(kind=1)
120968 <85> DW_AT_name : (indirect string, ...): prog
120976 compiler naming convention is). While string types are printed as
121049 later use the newly introduced check_optional_entry over check_entry.
121157 argument, the language string, which will be passed though to the
121218 over 10 years ago. The last .f files in the testsuite by now are all
121566 gdb/python: improve formatting of help text for user defined commands
121601 The problem of course, is that GDB is using the Python doc string
121613 function that rewrites the doc string text following the following
121636 suitably vague about how the doc string is used, so I think the new
121643 string in cmdpy_init (when creating a custom GDB command in Python).
121649 string even though the command would remain registered with GDB, which
121652 After this commit we release the doc string at the point that we hand
121653 it over to the command creation routines. If we throw _after_ the
121654 command has been created within GDB then the doc string will be left
121657 the doc string (I suspect we don't, but I think in general the
121748 The second '\0' is left over from the original buffer contents.
122138 This requires changing the users of the index to iterate over multiple
122172 Copy initialisation over from the elf.em before_parse. Commit
122249 are not interested) to seamlessly skip it without issues.
122365 the command string, and, it's also more explicit.
122629 gdbarch method to iterate over core file register note sections on LoongArch.
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
123362 Add a radix-256 trie over the address space to quickly map address to
123369 linked list over ranges uses about 10 MB, and the entire perf job uses
123473 …gdb/testsuite/gdb.base/step-over-no-symbols.exp: if { $displaced != "off" && ![support_displace…
123477 …gdb/testsuite/gdb.base/step-over-syscall.exp: if {$displaced == "on" && ![support_displaced…
123486 gdb/testsuite/gdb.python/py-evthreads.exp:if { ![support_displaced_stepping] } {
123487 …gdb/testsuite/gdb.threads/step-over-lands-on-breakpoint.exp: if { $displaced != "off" && ![supp…
123488 …gdb/testsuite/gdb.threads/interrupt-while-step-over.exp: if { ${displaced-stepping} != "off" &&…
123489 …gdb/testsuite/gdb.threads/step-over-trips-on-watchpoint.exp: if { $displaced != "off" && ![supp…
123509 IS_ABSOLUTE_PATH is normally used with null-terminated string. It's
123510 fine to pass an empty null-terminated string to IS_ABSOLUTE_PATH,
123511 because index 0 in such a string is valid. But not with an empty
123531 COFF: use hash for string table also when copying / stripping
123532 Otherwise the string table may grow and hence e.g. change a final binary
123563 don't over-align file positions of PE executable sections
123590 * bfdio.c (_bfd_real_fopen): Delete ccs string.
123841 constructs. If we skip these, line numbers (and possibly even file
123847 A string the first two characters of which do not match "if" also wont
123876 Fix gdb.python/py-connection.exp with remote targets
123878 specified, gdb.python/py-connection.exp started failing like so:
123880 $ make check TESTS="gdb.python/py-connection.exp" RUNTESTFLAGS="--target_board=native-gdbserver"
123881 (gdb) PASS: gdb.python/py-connection.exp: info connections while the connection is still around
123884 (gdb) FAIL: gdb.python/py-connection.exp: kill the inferior
123937 gdb.base/skip.exp: Don't abuse gdb_test's question support
123938 gdb.base/skip.exp abuses gdb_test's support for answering a GDB
123985 - gdb.python/py-parameter.exp, passing a spurious "1" as extra
123990 - gdb.python/py-xmethods.exp, a missing test message, resulting in
124306 [gdb/testsuite] Fix gdb.cp/break-f-std-string.cc with older gcc
124307 When running test-case gdb.cp/break-f-std-string.exp on openSUSE Leap 15.3
124310 (gdb) whatis /r std::string^M
124311 No symbol "string" in namespace "std".^M
124312 (gdb) FAIL: gdb.cp/break-f-std-string.exp: _GLIBCXX_USE_CXX11_ABI=1: \
124313 whatis /r std::string
124322 typedef basic_string<char> string;
124332 typedef basic_string<char> string;
124335 due to gcc commit 33b43b0d8cd ("Define std::string and related typedefs
124546 the "Symtabs:" string, and consequently the corresponding
124573 Rewrite the proc to iterate over all cases, and check if the test is supported
124710 Fix "b f(std::string)" when current language is C
124712 f(std::string)", and the current language is C, the breakpoint fails
124716 break f(std::string)
124717 Function "f(std::string)" not defined.
124721 The problem is that the code in GDB that expands the std::string
124745 I.e., std::string is expanded to "class std::..." instead of just
124751 "std::string" typedef symbol, which is a C++ symbol.
124756 Adjust the gdb.cp/break-f-std-string.exp testcase to try setting a
124757 breakpoint at "f(std::string)" in both C and C++.
124789 Fix "b f(std::string)", always use DMGL_VERBOSE
124793 break 'f(std::string)'
124794 Function "f(std::string)" not defined.
124795 (gdb) FAIL: gdb.cp/no-dmgl-verbose.exp: gdb_breakpoint: set breakpoint at 'f(std::string)'
124798 (gdb) PASS: gdb.cp/no-dmgl-verbose.exp: DMGL_VERBOSE-demangled f(std::string) is not defined
124816 So why is it that setting a breakpoint at "f(std::string)" fails with
124820 Itanium ABI mangling scheme has a shorthand form for std::string (and
124838 default, it expands it to the user-friendly typedef "std::string",
124858 mangled name of a function such as "void f(std::string)" that was
124861 "void f(std::string)".
124863 For example, the mangled name of "void f(std::string)" if you compile
124868 f(std::string)
124875 If, when the user sets a breakpoint at "f(std::string)", GDB would
124876 replace the std::string typedef for its underlying type using the same
124881 DMGL_VERBOSE, is "f(std::string)".
124884 names has an exception for std::string (and other standard
124885 abbreviation types), such that "std::string" is never
124888 And here lies the problem when you try to do "b f(std::string)" with a
124889 program compiled with the C++11 ABI. In that case, std::string
124899 for "std::string" anymore, it always demangles as:
124904 "f(std::string)", GDB's typedefs-in-parameters expansion code hits the
124905 exception for "std::string" and doesn't expand it, so the breakpoint
124910 one, not "f(std::string)".
124913 "std::string" exception from the typedef-in-parameters expansion
124914 logic. If we do just that, then "b f(std::string)" starts working
124923 standard abbreviation for "std::string" as "std::basic_string<char,
124925 the "std::string" typedef (etc.) too is no longer a problem.
124937 "DMGL_VERBOSE-demangled f(std::string) is not defined"
124941 new gdb.cp/break-f-std-string.exp testcase whose purpose is to make
124942 sure that setting a breakpoint at "f(std::string)" works. It
124976 gfortran 4.6). If this byte size evaluates to less than 8 we skip the
124978 lbound-ubound.f90. Similarly, in the lbound-ubound.exp testsfile we skip
126172 …(gdb) PASS: gdb.base/step-over-syscall.exp: detach-on-fork=off: follow-fork=child: break cond on t…
126181 testsuite/outputs/gdb.base/step-over-syscall/step-over-vfork \
126182 …-ex "tar rem | ../gdbserver/gdbserver - testsuite/outputs/gdb.base/step-over-syscall/step-over-vfo…
126238 [infrun] operator(): step-over queue now empty
126259 [infrun] operator(): step-over queue now empty
126531 It is not necessary to pass an empty string to mi_gdb_start, passing
126532 the empty string is equivalent to passing no arguments, which is what
126565 But that's fine, a single string like this works equally well as a
126605 the special 'args' parameter name, and then iterates over this list to
126720 Currently debuginfod is disabled when the string of server URLs
126721 is unset or set to be the empty string (via the $DEBUGINFOD_URLS
126756 …../gnulib/import/string.h:636:19: error: exception specification in declaration does not match pre…
126777 In file included from /usr/include/string.h:633,
126778 from ./string.h:41,
126780 ./string.h:1105:1: error: expected identifier or '(' before '__extension__'
127060 longer provides any benefit over the DWARF scanner). So, I think this
127147 [infrun] operator(): step-over queue now empty
127425 unfortunately since we are working over a dynhash in essentially
127661 * Makes the testcase iterate over all architectures, thus covering all
127844 code could fail. First, it might return a zero-length string, but in
127861 std::string rather than simple char * pointers freed by xfree.
127922 This changes the .gdb_index writer to skip linkage names. This was
127971 an inline step over breakpoint, we do not want to resume non stepping
127978 …FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=off: single step over vfork (GDB internal e…
127981 does not check if a step over is active when restarting other threads:
127993 - Call start_step_over before restart_threads. If a step over is already
127996 all threads just to stop them right away for a step over breakpoint.
127997 - Only call restart_threads if no step over is in progress at this
128004 they all seem to check that there is no step over currently active
128127 thread list at that time. But that felt more like papering over the
128239 the fixes needed to support correctly printing the 'quit' string.
128441 and to avoid the use of alloca by instead using std::string.
128443 Use std::string in coff-pe-read.c
128444 coff-pe-read.c uses xsnprintf and alloca, but using std::string is
128454 coff-pe-read.c iterates over BFD sections using bfd_map_over_sections,
128636 string "set temporary breakpoint", hence removing the differentiator.
128642 mi_continue_to_line passes that "test" string to mi_get_stop_line, that
128643 is a bit superfluous. mi_get_stop_line only uses that string in case of
128706 cleaner), but each string within the vector can be unique, which fixes
128764 gdb/testsuite: add binary testcases to py-format-string.exp
128837 Trailing whitespace in the string of debuginfod URLs causes an
129086 string when there is no parent entry.
129167 Also use this iterator range in run_tests so all iterations over the
129248 gdbsupport: make gdb_realpath_keepfile return an std::string
129249 I'm trying to switch these functions to use std::string instead of char
129258 gdbsupport: make gdb_abspath return an std::string
129259 I'm trying to switch these functions to use std::string instead of char
129756 already does. This change is needed to make string-reading usable by
129761 there -- I forgot to copy over the definition when making this file.
130011 …/home/smarchi/src/binutils-gdb/gdb/complaints.c:130:65: error: format string is not a string liter…
130159 Change subfile::name to be a string, for easier memory management.
130458 If the "interesting" flag is false, GDB knows to skip the DIE
130537 Let skip_one_die not skip children
130538 This patch adds an option to skip_one_die that causes it not to skip
130566 refer to a CU coming from the dwz file, the fix is to simply skip such
130924 actually print the internally used type over the default type name.
131525 gdb: change file_file_name to return an std::string
131526 Straightforward change, return an std::string instead of a
131598 "skip_macro_tests" that can be used to skip over them.
131776 In gdb/python/py-registers.c, the register group iterator needed to
131808 when we iterate over the register groups using reggroup_next and
131938 gdb: use 'const reggroup *' in python/py-registers.c file
131939 Convert uses of 'struct reggroup *' in python/py-registers.c to be
132166 * doc/as.texi: Add z16 and arch14 to CPU string list.
132167 * doc/c-s390.texi: Add z16 to CPU string list.
132171 * s390-mkopc.c (main): Enable z16 as CPU string in the opcode
132368 source, and it too has moved over to using interp_factory_register.
132379 return the address, rather than a string.
132457 includes in mep-tdep.c and python/py-registers.c are no longer needed,
132785 signal" and non "syscall signal" cases, we would ideally skip over all
133004 is reading all the shared libraries over GDB's remote protocol, which
133011 libraries are no longer copied over the remote protocol, and I no
133032 precedence over prologue analyzers. So if we have to debug a program
133118 set the prologue_end marker. Tests done with GCC 11.2.0 (not over the
133497 of strings, and then loops over the array printing the arguments out
133885 undefined, and so expands to the empty string. As a result TAGS does
133984 I think it would be nicer if the delta was spread more evenly over the
134122 The fingerprint for a layout is represented as a string, the string is
134172 and that the cmd window has been placed over the border of the asm
134235 that handles any left over space. Usually, in "Step 2", each
134237 when all sizes are calculated we may have some space left over.
134245 space to the windows, can also be used to reclaim space (in the over
134262 is the possibility that we have some space left over.
134286 over all the sub-layouts. We take care to respect the min/max sizes,
134564 Regen bfd po/SRC-POTFILES.in
135015 [infrun] clear_step_over_info: clearing step over info
135020 [infrun] operator(): step-over queue now empty
135069 … [threads] thread_needs_step_over: Need step over [LWP 713931]? Ignoring, should remain stopped
135070 … [threads] thread_needs_step_over: Need step over [LWP 713932]? Ignoring, should remain stopped
135072 …[threads] thread_needs_step_over: Need step over [LWP 713935]? No, no breakpoint found at 0x555555…
135074 …[threads] thread_needs_step_over: Need step over [LWP 713936]? No, no breakpoint found at 0x7ffff7…
135075 [threads] resume: Resuming, no pending status or step over needed
135140 … [threads] thread_needs_step_over: Need step over [LWP 724595]? Ignoring, should remain stopped
135141 … [threads] thread_needs_step_over: Need step over [LWP 724596]? Ignoring, should remain stopped
135143 …[threads] thread_needs_step_over: Need step over [LWP 724597]? No, no breakpoint found at 0x555555…
135145 …[threads] thread_needs_step_over: Need step over [LWP 724598]? No, no breakpoint found at 0x7ffff7…
135146 [threads] resume: Resuming, no pending status or step over needed
135667 [infrun] operator(): step-over queue now empty
135772 gdb/testsuite: fix copy & paste error in gdb.python/py-format-address.exp
135773 The test gdb.python/py-format-address.exp, added in commit:
135778 gdb/python: add gdb.format_address function
135918 lex the next token after handling a string token. This is also fixed
135994 Change call_site_target to iterate over addresses
136076 libtool.m4: fix the NM="/nm/over/here -B/option/with/path" case
136176 gdb/testsuite: remove gdb.python/pretty-print-call-by-hand.exp
136182 … UNRESOLVED: gdb.python/pretty-print-call-by-hand.exp: frame print: backtrace test (PRMS gdb/28856)
136316 The last section in a CTF dict is the string table, at an offset
136433 gdb/python: remove Python 2/3 compatibility macros
136438 python-internal.h contains a number of macros that helped make the code
136446 gdb/python: remove Python 2 support
136450 the user passes --with-python=python2, this will cause a configure
136455 string and integer types are subtle. It requires a lot of effort and
136534 gas/Dwarf5: re-use file 0 line string table entry when faking file 0
136535 No need to emit the same string a 2nd time for file 1 in this case.
136606 successive string literals. However, in any event is the above different
136816 gdb/python: add gdb.format_address function
136820 This method takes an address, and returns a string with the format:
137274 gdb/testsuite: reformat gdb.python/pretty-print-call-by-hand.py
137539 gdb/python: remove gdb._mi_commands dict
137544 CXX python/py-micmd.o
137545 …/home/smarchi/src/binutils-gdb/gdb/python/py-micmd.c: In function ‘int micmdpy_uninstall_command…
137546 …/home/smarchi/src/binutils-gdb/gdb/python/py-micmd.c:430:20: error: ‘PyDict_GetItemWithError’ …
137560 (std::unordered_map<std::string, gdbpy_ref<micmdpy_object>>). While
137799 Set GPROFNG_BROKEN_JAVAC to "yes" only with a broken javac and skip the
137920 * po/SRC-POTFILES.in: Regenerate.
138012 Notice the 'quit' was printed over the prompt.
138076 we can print the 'quit' string, and then call rl_deprep_terminal
138094 correctly print the 'quit' string.
138106 In this commit I change GDB to print the 'quit' string on the line
138132 This started as a patch to implement string concatenation for Ada.
138155 the Ada expression evaluator. In particular, a string literal may be
138156 converted to a wide or wide-wide string depending on context.
138826 iterating over block symbols") caused a regression. The bug is that
138923 gdb/python/mi: create MI commands using python
138928 mi_command_py. A new file, gdb/python/py-micmd.c contains the logic
138975 lists, iterators, or an object that can be converted to a string.
139016 python/python.c that would search the mi command table, and delete the
139029 over it from within GDB's python related code.
139031 This patch handles command redefinition entirely within GDB's python
139045 (gdb) python cmd = MyMICommand("-abc")
139046 (gdb) python cmd.__init__("-def")
139054 into a subclass of mi_command, the python mi_command_py, which
139139 now fail during validation. For all the other fields we skip the
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]"
139932 gdb/python: add Type.is_signed property
139948 gdb/python: add Type.is_scalar property
140020 ada_print_floating rewrites a floating-point string representation to
140159 Don't pre-size result string in ada_decode
140160 Currently, ada_decode pre-sizes the output string, filling it with 'X'
140162 std::string do the work here, and simply append characters to the
140163 string as we go. This turns out to be useful for a subsequent patch.
140237 Use function view when iterating over block symbols
140600 delete the entire build directory and start over.
140768 …../../binutils-gdb/gdb/python/py-infthread.c:102:30: warning: ‘extra_info’ may be used uninitializ…
140779 literals. gdb does not generally seem to handle the Ada wide string
140791 <1130> DW_AT_name : (indirect string, offset: 0x19ff): QW0178
140833 gdb/python: Add gdb.InferiorThread.details attribute
140835 attribute contains a string, the results of target_extra_thread_info
140838 As the string returned by target_extra_thread_info is unstructured,
140842 they need access to this string.
140844 Given that the string produced by target_extra_thread_info varies by
140847 None, or a string.
140972 gdb: add operator+= and operator+ overload for std::string
140974 gdb::unique_xmalloc_ptr<char> to a std::string. I could only find 3
141051 to parse the multi-letter prefix in the architecture string.") changed
141077 With this patch, users will be able to "gloss over" the details of matching
141079 to strncmp_iw_with_mode to skip parameter lists if none is explicitly given
141136 This patch attempts to cover the basics of string matching, white
141220 gdb: use a range based for loop when iterating over an array
141221 Make use of a range based for loop to iterate over a static global
141231 gdb/darwin: skip over WIFSTOPPED wait4 status
141274 string to specify the number of characters to print.
141292 parameters. Change the string + length output parameters (permissions
141294 for (a non-NULL terminated view on a string). No changes in behavior
141411 used to return the extension string for each INSN_CLASS_*.
141729 disable pagination, and in aae1c79a03a (PR python/12227..., 2010-12-07)
141742 RISC-V: Maintain a string to hold the canonical order
141756 string.
141835 for just the ^done,value="\"FIRST COMMAND\"" string, then I can start
141839 be sure than nothing is left over in the expect buffer to muck up
141899 gdb: make use of std::string in dbxread.c and xcoffread.c
141901 where making use of std::string would remove the need for manual
142106 * macro.c (buffer_and_nest): Don't read past end of string buffer.
142580 gdb/python: move styling support to gdb.styling
142583 python.c so GDB can find the functions in their new location.
142604 gdb: use python to colorize disassembler output
142868 * elf-properties.c (_bfd_elf_parse_gnu_properties): Don't skip
143199 I also reformatted one of the index_cache_debug where a string will
143232 gdb/python: allow Value.format_string to return styled output
143236 When this argument is True, then the returned string can contain output
143239 When this argument is False, then the returned string will not contain
143242 If the returned string is going to be printed to the user, then it is
143247 in gdb.python/py-format-string.exp in an environment where styling
143355 string, character by character into gdb's buffer, then handle the
143361 glibc gets the string:
143627 (gdb) python gdb.execute("do-setup", False, True)
143925 over all filetabs, for example, those cases would use compunit_filetabs,
144236 Don't abort for undefined symbol when finishing DT_RELR. Instead, skip
144523 case it uses the symbol lookup if the string contains a +. When it isn't
144605 at /gdb-up/gdb/python/python.c:1063
144677 Stop the BFD library complaining about compressed dwarf debug string sections being too big.
144701 is done in Python. We extended a classes __doc__ string with some
144704 The classes doc string looks like this:
144721 string is merged with the dynamically generated text.
144778 The problem here is that in cli/cli-cmd.c:list_command, the string
144838 string in question is not empty, so, after calling
144839 string_to_event_location, if non of the string has been consumed, then
144840 the content of the string must be junk - it clearly doesn't look like
144890 gdb: add empty string check in parse_linespec
144891 If parse_linespec (linespec.c) is passed ARG as an empty string then
144933 2. I've removed the mention that the returned string is malloc'd,
144995 gdb/python: fix gdb.Objfile.__repr__ () for dynamically compiled code
145089 of XXXX over XXXX.NUMBER for info symbol on gfortran symbols.
145692 In remote_btrace_maybe_reopen() we iterate over threads and use
145705 This, in turn, led to find_inferior_pid() asserting when we iterated over
145738 gdb/python: handle non utf-8 characters when source highlighting
145769 PyUnicode_FromString in Python 3), this function converts a C string
145773 string for the purpose of the conversion. And here of course, is the
145791 incoming content is not already a Unicode string. This is what
145802 content being a Unicode string (for Python 3), lets just make the
145847 the argument be an int, rather than a string. This patch is the
145852 gdb/python: improve the auto help text for gdb.Parameter
145858 sources: the class documentation string, and the set_doc/show_doc
145863 """This is the class documentation string."""
145884 This is the class documentation string.
145915 This is the class documentation string.
145934 This is the class documentation string.
145936 # Nothing provided by the user, the first string is now different:
145941 # Only the class documentation is provided, the first string is
145945 This is the class documentation string.
145958 (gdb) python Param_None ('print param-none')
145971 (gdb) python Param_None ('print param-none')
145991 show_doc string to create a sentence that would display the current
145996 by displaying the show_doc string with the current value appended, see
146019 I've updated the existing gdb.python/py-parameter.exp test to cover
146027 gdb/python: add gdb.history_count function
146110 string buffer, because it is the result of the computation that we want
146111 to return. It is the reason why string_file::string returns a non-const
146113 have a dedicated method for that instead and make string_file::string
146118 resulting string was copied. With the new version, it's not possible to
146142 This is PR python/10790.
146152 (gdb) python print(gdb.parameter('endian'))
146154 (This is related to PR python/12188, though this patch isn't going to
146839 Use std::string in event_location
146840 This changes event_location to use std::string, removing some manual
146841 memory management, and an unnecessary string copy.
146874 gdb: preserve `|` in connection details string
146884 (gdb) python conn = gdb.selected_inferior().connection
146885 (gdb) python print(conn.details)
146895 a similar fashion, I think that the `details` string of the
146901 removed in gdb/serial.c. The string passed to the pipe_ops
146907 store the full string (including the `|`) in the serial::name member
146912 gdb/ser-pipe.c), and in pipe_open, we now know to skip over the `|`.
147429 + string is less than length computed by dlang_number.
147440 + * d-demangle.c (dlang_identifier): Skip over fake parent manglings.
147548 new function to convert the thread_info::state variable to a string.
147550 The new debug might be useful to others, and the state to string
147638 gdb: testsuite: make string[] type as char in gdb.base/charset.c
147705 gdb/python: add gdb.host_charset function
147711 gdb/testsuite: fix gdb.python/py-events.exp for finding process id
147713 gdb.python/py-events.exp test errors out with
147715 ERROR: tcl error sourcing /path/to/gdb/testsuite/gdb.python/py-events.exp.
147719 (file "/path/to/gdb/testsuite/gdb.python/py-events.exp" line 103)
147721 "source /path/to/gdb/testsuite/gdb.python/py-events.exp"
147724 "uplevel #0 source /path/to/gdb/testsuite/gdb.python/py-events.exp"
147748 Debugging a target over a serial line.
147982 -z pack-relative-relocs is chosen over the similar option in lld,
148279 string length of the directory, instead emit the "CU: dir/name"
148309 when call fill_run() in EBCDIC-US and IBM1047, but the type of string[] is
148315 Make the type of string[] as unsigned char to fix the following six failed
148320 FAIL: gdb.base/charset.exp: check value of parsed string literal in EBCDIC-US
148323 FAIL: gdb.base/charset.exp: check value of parsed string literal in IBM1047
148411 relocation over internal symbols.
149175 The actual test explicit names do not add much over the command from
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.
149303 doc-string]
149313 [#:prefix? prefix] [#:doc doc-string]
149333 from i 2.1, users need to add them in the architecture string if they need
149419 rather than printing the same output with an empty string as
149460 functions. I did a grep over the testsuite, and don't believe the
149479 of a string. I am not certain, but that is why I think the existing
150355 out */po/*.pot which we don't update frequently.
151348 'GNU/Linux native target'. The body string for this setting has been
151444 incoming string.
151603 being disabled. So, we skip to the next step which is to call
151680 my plan is to switch both users over to using ::stop_reply_queue so
151950 Leaving entries on mips_hi16_list from a previous pass over relocs
151997 …dwarf.c:11300:3: error: format not a string literal and no format arguments [-Werror=format-securi…
152261 offset/constant reference DW_FORMs being given an indexed string
152263 an error string instead. The address of the string varies with PIE
152265 Fix this by validating integer attribute forms, as we do for string
152406 In file included from /usr/include/string.h:519,
152407 from ../gnulib/import/string.h:41,
152415 …r*, long unsigned int)’ output may be truncated copying 107 bytes from a string of length 107 [-We…
152433 the code to check that the source string length is smaller than the
152509 and add an assert, if we are not using the argument string then the
152510 string should be nullptr. Also removed a cryptic 'gdb_????' comment,
152543 section is over the 32-bit address range.
152545 * code-model-02.ld: the text section is over the 32-bit address range, but
152702 I updated the gdb.gdb/python-helper.exp test to cover all of these
153213 user want to reset the whole architecture string. So the formats are,
153217 .option arch, <ISA string>
153220 directive. Instead, users should reset the whole architecture string
153231 architecture string. Besides, Don't allow to add or remove
153245 when resetting the whole architecture string.
153506 equivalent) to loop over a static array. This patch changes some of
153529 gdb/python: Use tp_init instead of tp_new to setup gdb.Value
153560 https://docs.python.org/3/c-api/typeobj.html#c.PyTypeObject.tp_new
153789 replacing it with a simpler use of std::string.
153839 symbol implementations skip any filename checks.
154083 of the target string, most notably in that "-little" wasn't actually
154086 noticed that the input_target string wasn't being copied but rather
154149 than too little but accidentally over-aligned.
154281 handle name string wasn't freed. When register a file handler with an
154283 ended up creating a new std::string object and overwriting the
154284 file_handler::name pointer, without free-ing the old std::string.
154324 any string that must be computed. Finally, the CU's objfile will only
154588 gdb: make saved_filename an std::string
154589 Make this variable an std::string, avoiding manual memory management.
154597 are not paired with an error string, but we had an assert that the
154618 A test in gdb.python/py-send-packet.exp added in this commit:
154623 gdb/python: add gdb.RemoteTargetConnection.send_packet
154699 That xstrdup is not correct, since we are assigning an std::string. The
154700 result of xstrdup is used to initialize the string, and then lost
154768 debugformat field") changes the debug format string in "info source" to
154772 string to see if the test program is compiled with DWARF debug
154778 could find to use "DWARF [0-9]" instead (that string is passed to TCL's
154779 string match).
155044 an int and a string.
155769 happen, get_mnemonic_name would return an empty string.
155784 gdb/python: don't use the 'p' format for parsing args
155785 When running the gdb.python/py-arch.exp tests on a GDB built
155854 gdb/testsuite: check the python module is available before using it
155855 The gdb.python/py-inferior-leak.exp test makes use of the tracemalloc
155860 This commit adds a new helper function to lib/gdb-python.exp that
155861 checks if a named module is available. Using this we can then skip
155918 accept either the "Cannot access memory ..." string, or the newer
155919 "unknown disassembler error ..." string. With this change done the
155927 expect to get the "Cannot access memory ..." error string.
155946 gdb/python: add gdb.RemoteTargetConnection.send_packet
155951 This new sub-class has one additional method over its base class,
155956 The outgoing packet can either be a bytes object, or a Unicode string,
155957 so long as the Unicode string contains only ASCII characters.
155995 the reply treated the reply as a C string, it assumed that the string
156023 gdb/python: introduce gdb.TargetConnection object type
156058 'details': A string or None. Extra details for the connection, for
156070 they are set over 8-bits. I think this is a bug that we used to support
156151 are NULL string in the riscv_vsew and riscv_vlmul, so dump the
156290 Update description of string's -n option.
156371 can still skip all the tests.
156483 default syscall table over to it. Ports using unique syscall tables
156486 Switching common ports over is easy by checking NL_TARGET, but the
156619 copy it over to the cris forks of the test+run functions.
156760 These haven't been used in over 20 years. The sim testsuite used to
156858 gdb/python: make some global variables static
156963 * po/BLD-POTFILES.in: Regenerate.
156964 * po/SRC-POTFILES.in: Regenerate.
156969 * po/fr.po; Updated French translation.
156990 gdb/python: make some global variables static
156991 Make a couple of global variables static in python/python.c. To do
157166 the help string, and forgot to update it. Change it for a real help
157167 string.
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.
157449 think that a target_waitkind-to-string function would be useful. While
157452 The debug messages will show a string matching exactly the
157456 string it got as a parameter. This allows doing this:
157477 it is almost impossible that the input string will be NULL. Therefore,
157571 Debugging gdb revealed that the string offset is:
157588 0 (indirect line string, offset: 0x128): /data/gdb_versions/devel
157589 1 (indirect line string, offset: 0x141): /home/vries
157835 srchilite::SourceHighlight::SourceHighlight(std::string const&)
157855 In the enable_source_highlight=auto scenario, this allows the build to skip
158082 .option arch, =<ISA string>
158388 gdbsupport: make gdb_assert_not_reached accept a format string
158389 Change gdb_assert_not_reached to accept a format string plus
158392 Because the format string passed by the caller is prepended with a "%s:"
158394 string (`_(...)`). Make the gdb_assert_not_reached include the _(),
158415 match LE sytems. The expected string is updated to capture both Big Endian
159046 gdb/nat/linux-osdata.c: fix build on gcc-12 (string overfow)
159056 huge core count. The change switches to std::string for memory
159080 logic to port over there. We have to duplicate that into the cris
159303 Provide explicit control over the program's environment with the
159473 DEBUGINFOD_URLS_ENV_VAR), or use a dummy string to store the setting,
159648 casts all over the place. There is however the xtensa architecture,
159656 COFF: avoid modifications over C_FILE filename aux entries.
159691 0 (indirect line string, offset: 0x25): /current/directory
159692 1 (indirect line string, offset: 0x38): /full/path
159696 0 0 (indirect line string, offset: 0x43): /full/path/test.c
159855 The 'show user' command (which shows the definition of non-python/scheme
159976 * po/POTFILESin: Regenerate.
160095 skip system call in skip_prologue":
160111 according to the generated architecture string. This patch resolves the
160167 architecture string to rv64g by bfd/elfxx-riscv.c:riscv_set_default_arch.
160169 set the default architecture string to rv64gc for disassembler, to keep
160204 to set the default architecture string.
160214 architectrue string to rv64gc.
160220 can use target_compile directly. So switch it over to simplify.
160230 to use %s with an empty string to avoid the compiler warning but not
160300 fixed in commit a50bdb99afe "[gdb/tdep, rs6000] Don't skip system call in
160369 string table if needed.
160959 loop over threads in continue_1, when "non_stop && all_threads" is true.
160966 that it was correct. There is a similar iteration over threads, and
161212 uses the return value all over the place, so for there disable
161374 I suspect that the line number has, over time, come adrift from where
161480 scalar. This means that string-based settings will still use
161547 to parse the architecture string from the elf attribute before
161636 …r function 'virtual void gnu_nat_target::create_inferior(const char*, const string&, char**, int)':
161757 asan: dlltool buffer overflow: embedded NUL in string
161760 the xstrdup allocated string buffer. xmemdup quite handily avoids
161761 this problem, even writing the terminating NUL over the trailing
161771 * ldlex.l (double quote string): Use xmemdup.
161851 (ppc64_elf_edit): Move func_desc_adjust iteration over syms to..
161860 [gdb/tdep, rs6000] Don't skip system call in skip_prologue
161884 by default, don't skip, such that the breakpoint is set at 0x00007ffff7e42eb8
162136 these casts over to uintptr_t.
162312 Add a new ECHO_STAMP helper and convert existing stamp code over
162447 Add 'set/show debuginfod urls' commands. Accepts a string of
162850 [gdb/testsuite] Require python in gdb.server/server-kill-python.exp
162851 I came across this when running test-case gdb.server/server-kill-python.exp
162852 with a gdb configured without python:
162856 -ex source outputs/gdb.server/server-kill-python/file1.py^M
162857 FAIL: gdb.server/server-kill-python.exp: ensure inferior is running
162864 Fix this by testing for python support in the test-case.
162866 Tested on aarch64-linux (with python support disabled) and x86_64-linux (with
162867 python support enabled).
162893 Consider a fortran routine where a string variable s is modified:
162906 $ gdb -q -batch outputs/gdb.opt/fortran-string/fortran-string \
162910 Breakpoint 1 at 0x4006f7: file fortran-string.f90, line 21.
162912 Breakpoint 1, f (s=..., _s=_s@entry=3) at fortran-string.f90:21
162934 The test-case is based on gdb.opt/fortran-string.exp from
163242 gdbserver: make target_pid_to_str return std::string
163252 target_pid_to_str to return an std::string to avoid this. I don't think
163452 (dump_ctf_archive_member): Likewise. Never stop iterating over
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.
163809 gdb/python: move gdb.Membuf support into a new file
163811 new file within gdb/python/py*.c. Currently all gdb.Membuf objects
163816 and left the new function in gdb/python/py-inferior.c, however, it
163821 gdb/python/py-membuf.c, the interface is gdbpy_buffer_to_membuf, which
163835 gdb/python: new gdb.architecture_names function
164191 PR28417, std::string no longer allows accepting nullptr_t
164194 std:string undefined behaviour.
164212 another pass over relocations before decisions are made about GOT
164228 Use std::string in print_one_catch_syscall
164229 This changes print_one_catch_syscall to use std::string, removing a
164272 [gdb/testsuite] Reimplement gdb.gdb/python-interrupts.exp as unittest
164273 The test-case gdb.gdb/python-interrupts.exp:
164276 - calls a python command
164348 remote occurs over tcp.
164714 [gdb/testsuite] Fix test name in gdb.python/python.exp
164715 When running test-case gdb.python/python.exp, we have:
164717 PASS: gdb.python/python.exp: starti via gdb.execute, not from tty
164718 PASS: gdb.python/python.exp: starti via interactive input
164731 PASS: gdb.python/python.exp: starti via gdb.execute, not from tty
164732 PASS: gdb.python/python.exp: starti via gdb.execute, from tty
165128 [gdb] Make execute_command_to_string return string on throw
165131 std::string output;
165151 Fix this by returning the string using a parameter instead:
165156 Also add a variant without string parameter, to support places where the
165440 gdb.python/flexible-array-member.exp expected pattern":
165447 As in gdb.python/flexible-array-member.exp, change the test to accept the two
165568 is over-engineered nonsense and an attractive target for fuzzers.
165664 Limit on string chars or array elements to print is unlimited.
165749 The PR28401 testcase has a section named "", ie. an empty string.
165910 gdb/python: fix memory leak in python inferior code
166010 gdb/python: add a new gdb_exiting event
166039 gdb/python: update events test to handle missing exit_code
166040 The test gdb.python/py-events.exp sets up a handler for the gdb.exited
166074 gdb_demangle to also return this type. In one spot, std::string is
166267 The change "make string-like set show commands use std::string
166271 const std::string &sysroot = gdb_sysroot;
166283 Since python 2 is no longer supported on most distributions, update the
166284 script to run under python while while still being runnable under
166375 std::string.
166422 gdb: make string-like set show commands use std::string variable
166426 "mordernize" this by changing them to use an std::string for storage.
166428 An obvious reason is that string operations on std::string are often
166433 string often both have the same meaning of "no value". String settings
166435 "set foo" (where `foo` is a string setting), the setting now points to
166436 an empty string. For example, solib_search_path is nullptr at startup,
166437 but points to an empty string after doing "set solib-search-path". This
166441 is very easy to forget one or the other. With std::string, we at least
166443 representing an empty string setting, that is with an empty string.
166448 optional<string> anyway.
166454 history_filename is an empty string, it means the setting was explicitly
166455 cleared, so it leaves it as-is. With the change to std::string, this
166463 give string parameters initial values, by simply initializing the global
166466 In Python and Guile, when registering a string-like parameter, we
166467 allocate (with new) an std::string that is owned by the param_smob (in
166471 take an `std::string *` instead of a `char **` and fixing everything
166472 that failed to build. That includes of course all string setting
166475 string_option_def now uses an std::string also, because there's a
166480 rather not try to change it to work on an std::string right now.
166481 Instead, I added an overload that copies the std:string to a `char *`
166668 gdb/python: fix a few flake8 warnings
166938 gdb.python/py-pp-registration.exp, remove "message" passed to runto.
167401 [gdb/testsuite] Fix gdb.python/py-breakpoint.exp with python 2
167402 With a gdb build using python 2.7, I run into:
167404 (gdb) python \
167406 File "<string>", line 1^M
167411 (gdb) FAIL: gdb.python/py-breakpoint.exp: test_bkpt_auto_disable: \
167417 - in python 2, print is a statement, while in python 3 it's a function
167432 [gdb/testsuite] Fix breakpoint detection in gdb.gdb/python-helper.exp
167433 With a gdb configured to be somewhat minimal, while still supporting python:
167449 --with-python=/usr
167450 --with-python-libdir=/usr/lib
167460 (gdb) PASS: gdb.gdb/python-helper.exp: start inner gdb
167465 (xgdb) FAIL: gdb.gdb/python-helper.exp: hit breakpoint in inner gdb (timeout)
167645 I made a mistake in the previous patch. Adjust the format string to
168121 child instead. Doing this breaks doing "next" over fork(). When "next"
168240 format string.
168262 length, but we fail to skip this check when this is not a NEWFUNCINFO
168764 - skip the hw breakpoint testing if not supported
168895 Fix 'FAIL: gdb.perf/disassemble.exp: python Disassemble().run()'
168899 python Disassemble().run()
168901 File "<string>", line 1, in <module>
168904 File "<string>", line 25, in warm_up
168907 (gdb) FAIL: gdb.perf/disassemble.exp: python Disassemble().run()
168940 …PATH: gdb.perf/backtrace.exp: python sys.path.insert(0, os.path.abspath("/home/pedro/rocm/gdb/buil…
168941 …PATH: gdb.perf/backtrace.exp: python exec (open ('/home/pedro/rocm/gdb/build/gdb/testsuite/outputs…
168946 -PASS: gdb.perf/backtrace.exp: python import os, sys
168947 …-PASS: gdb.perf/backtrace.exp: python sys.path.insert(0, os.path.abspath("/home/pedro/rocm/gdb/bui…
168948 …-PATH: gdb.perf/backtrace.exp: python sys.path.insert(0, os.path.abspath("/home/pedro/rocm/gdb/bui…
168949 …-PASS: gdb.perf/backtrace.exp: python exec (open ('/home/pedro/rocm/gdb/build-master/gdb/testsuite…
168950 …-PATH: gdb.perf/backtrace.exp: python exec (open ('/home/pedro/rocm/gdb/build-master/gdb/testsuite…
168951 +PASS: gdb.perf/backtrace.exp: setup perftest: python import os, sys
168952 …+PASS: gdb.perf/backtrace.exp: setup perftest: python sys.path.insert(0, os.path.abspath("${srcdir…
168953 …+PASS: gdb.perf/backtrace.exp: setup perftest: python exec (open ('${srcdir}/gdb.perf/backtrace.py…
168959 with_test_prefix. Add explicit test names to python invocations,
168973 All those duplicate test names come from gdb.perf/skip-command.exp.
168979 * gdb.perf/skip-command.exp (run_skip_bench): Wrap each for
168991 <14ff> DW_AT_name : (indirect string, offset: 0x215e): nb_bytes
169002 <1650> DW_AT_name : (indirect string, offset: 0x218d): nb_bytes
169552 [gdb/testsuite] Fix gdb.python/py-events.exp
169553 With test-case gdb.python/py-events.exp on ubuntu 18.04.5 we run into:
169558 src/gdb/testsuite/gdb.python/py-events-shlib.c:19^M
169559 (gdb) FAIL: gdb.python/py-events.exp: get current thread
169900 missed looping over subsegments, which resulted in some u.filename
169904 * dwarf2dbg.c (purge_generated_debug): Iterate over subsegs too.
170089 file name string.)
170274 RISC-V: Merged extension string tables and their version tables into one.
170308 architecture string, but now we move ext_version_table from
170342 report error when the architecture string is empty.
170482 when calculating space for a string list.
171007 It's unclear why -H was picked over the more standard -h, but since
171017 [gdb/testsuite] Reimplement gdb.gdb/python-selftest.exp as unittest
171018 The test-case gdb.gdb/python-selftest.exp:
171020 - checks that the output of a python command is "Python not initialized"
171022 Reimplement gdb.gdb/python-selftest.exp as unittest, using:
171036 [gdb/testsuite] Fix DUPLICATE in gdb.base/skip-solib.exp
171037 Fix DUPLICATE in gdb.base/skip-solib.exp by using with_test_prefix.
171140 @object, .4byte instead of .long, and .asciz instead of .string.
171254 - std::string
171262 gdb/python: remove all uses of Py_TPFLAGS_HAVE_ITER
171266 python-internal.h (when IS_PY3K is defined).
171274 https://docs.python.org/release/2.3/api/type-structs.html). And so,
171298 https://docs.python.org/2.7/c-api/typeobj.html).
171534 sim: ppc: align format string settings with common code
171695 gdb: make use of std::string in utils.c
171696 Replace some of the manual string management (malloc/free) with
171697 std::string when creating commands in utils.c.
171701 string, while creating the actual set/show commands (using
171702 add_setshow_enum_cmd) does copy the doc string.
171705 prefix command doc strings, but switched to using std::string when
171761 gdb/python: new function to add values into GDB's history
172106 extension languages (python and guile).
172206 FAIL: gdb.gdb/python-helper.exp: breakpoint in captured_main \
172208 FAIL: gdb.gdb/python-helper.exp: run until breakpoint at captured_main
172218 (gdb) FAIL: gdb.gdb/python-helper.exp: breakpoint in captured_main \
172231 (gdb) UNTESTED: gdb.gdb/python-helper.exp: Cannot set breakpoint at \
172374 * po/BLD-POTFILES.in: Regenerate.
172397 …pport patches we have been grooming and maintaining for quite a few years over on git.haiku-os.org…
172663 The <type> is string, and the <insn-length> and <value> are constants.
172791 [gdb/cli] Don't assert on empty string for core-file
172802 empty-string case, such that we have instead:
172818 empty-string case.
173034 that string is non-NULL.
173251 being iterated over -- a classic mistake. Also, because a TU can be
173982 This change will quite likely trip over issues similar to those
174186 Improve forward progress test in python.exp
174758 allowing a relocation to write over memory anywhere. This was true
176158 gdb.python/amd64-py-framefilter-invalidarg.S. Originally, expression
176175 * gdb.python/amd64-py-framefilter-invalidarg.S : Update argc
176364 gdb/testsuite: update test gdb.base/step-over-syscall.exp
176366 gdb.base/step-over-syscall.exp. This test includes a call to kfail
176367 when we are testing a displaced step over a clone syscall.
176375 PR gdb/19675 describes how, when we displaced step over a clone, the
176487 string forms, even with DWARF 5. So it still doesn't add a
176502 …During symbol reading: use of DW_MACRO_define_strx with unknown string offsets base [in module /ho…
176528 …db/gdb/bsd-kvm.c:241:18: error: ISO C++11 does not allow conversion from string literal to 'char *…
176714 linux-nat target. when a process forks, it needs to carry over some
176732 process target copied over from the parent. The child's target stack is
176759 - hand over to the targets in the parent's target stack (including the
176761 the child's target stack. Also hand over the responsibility to the
177187 Total memory used for string cache: 4064^M
177331 when calculating string table file location.
177442 * thread #1, stop reason = step over
177628 string and fix a typo.
178560 gdb: make inferior::m_terminal an std::string
178567 gdb: make inferior::m_cwd an std::string
178578 gdb: make inferior::m_args an std::string
178579 With the current code, both a NULL pointer and an empty string can mean
178580 "no arguments". We don't need this distinction. Changing to a string
178582 string), which makes the code a bit simpler in my opinion.
178610 string. The other one is the `argc`/`argv` fields.
178675 gdb/testsuite: split gdb.python/py-parameter.exp in procs
178688 Fix for gdb.python/py-breakpoint.exp
178694 * gdb.python/py-breakpoint.exp (test_hardware_breakpoints): Add
179469 map_symbol_filenames can skip type units -- in fact I think it has to,
179485 file_and_directory carries a std::string in case the compilation
179487 string without also having to maintain the storage for it. So, this
179488 patch arranges for the compilation directory string to be stored in
179489 the per-BFD string bcache instead.
179916 I've had a good look over target usage of fx_subsy, and think I've
180017 * gdb.python/tui-window-disabled.exp: Same.
180018 * gdb.python/tui-window.exp: Same.
180144 BFD is written in C and thus throwing exceptions over such frames may
180672 values). Add a ptid_t::to_string method that returns a string
180813 gdb: use intrusive list for step-over chain
180814 The threads that need a step-over are currently linked using an
180890 /* Step-over chain. A thread is in the step-over queue if these are
181667 Fix problems translating messages when a percentage sign appears at the end of a string.
181675 * po/gas.pot: Regenerate.
181682 * po/bfd.pot: Regenerate.
181893 File "<string>", line 1, in <module>
181896 File "<string>", line 35, in execute_test
181903 (gdb) FAIL: gdb.perf/single-step.exp: python SingleStep(1000).run()
181905 ... many times over.
181913 https://docs.python.org/3.10/library/time.html
181970 python BackTrace(64).run()
181972 File "<string>", line 1, in <module>
181975 File "<string>", line 49, in execute_test
181982 (gdb) PASS: gdb.perf/backtrace.exp: python BackTrace(64).run()
181989 UNRESOLVED: gdb.perf/single-step.exp: python SingleStep(1000).run()
182003 * gdb.perf/skip-command.exp: Use gdb_test_python_run.
182004 * gdb.perf/skip-prologue.exp: Use gdb_test_python_run.
182129 rather than string literal.
182160 main loop over all CUs and TUs. (An earlier patch applied this same
182265 string length of a string argument is int, not size_t.
182276 $integer4 for size of string length.