Lines Matching +refs:po +refs:mark +refs:bash +refs:string
69 --enable-default-hash-style=gnu, like [x86_64 mark-plt tests].
75 [x86_64 mark-plt tests]: 16666ccc91295d1568c5c2cb0e7600694840dfd9
228 Update x86-64: Add -z mark-plt and -z nomark-plt
229 Pass --hash-style=both to ld for -z mark-plt tests to support linker
232 * testsuite/ld-x86-64/mark-plt-1b-x32.d: Pass --hash-style=both
234 * testsuite/ld-x86-64/mark-plt-1b.d: Likewise.
235 * testsuite/ld-x86-64/mark-plt-1d-x32.d: Likewise.
236 * testsuite/ld-x86-64/mark-plt-1d.d: Likewise.
415 2024-01-15 Mark Wielaard <mark@klomp.org>
1536 unwind_infopy_repr, where we currently return a different string.
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
1795 File "<string>", line 1, in <module>^M
1796 File "<string>", line 7, in kill_and_detach^M
1853 of opcodes. When opc->format is an empty string, no extra
2287 ld: Add --enable-mark-plt configure option
2288 Add --enable-mark-plt linker configure option to mark PLT entries with
2292 * NEWS: Mention -z mark-plt/-z nomark-plt and --enable-mark-plt.
2295 * configure.ac: Add --enable-mark-plt.
2306 When -z mark-plt is used to add DT_X86_64_PLT, DT_X86_64_PLTSZ and
2328 also add GLIBC_2.36 version dependency for -z mark-plt on the shared C
2352 * testsuite/ld-x86-64/mark-plt-1a.rd: New file.
2353 * testsuite/ld-x86-64/mark-plt-1b.rd: Likewise.
2354 * testsuite/ld-x86-64/x86-64.exp: Run -z mark-plt test for
2834 it is impossible to mark both operands 1 and 2 as optional for an
2943 sim: warnings: mark local funcs/vars as static
2944 These are only used in the respective files, so mark them as static.
3169 This patch changes this code to just use a std::string. A new type is
3241 MIPS/GAS: mips.exp, mark all mipsisa32*-linux as addr32
3441 ld: Adjust x86 and x86-64 tests for -z mark-plt
3442 To support -z mark-plt enabled by default, adjust x86 tests to accept
3444 x86-64 tests if -z mark-plt changes the expected outputs.
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
4455 sim: arm: mark local read-only arrays as static const
5744 sim: cgen: mark cgen_rtx_error noreturn
5745 Since this function never returns, mark it as such to fix some unused
6274 sim: signal: mark signal callback funcs as noreturn since they don't return
6284 sim: rx: mark abort func as noreturn since it doesn't
6301 sim: common: mark engine restart as noreturn
6308 sim: ppc: mark halt & restart funcs as noreturn
6326 human readable string when store tracing is enabled.
6808 s390: Use safe string functions and length macros in s390-mkopc
6810 and use macros for string lengths, such as mnemonic, instruction
7439 Let's mark the fields to avoid unused variable warnings.
7744 the code for string handling writes the address fetching callback
7746 rather than option_def::var_address::string.
8671 the pcrel_hi relocs, mark as done while with `-mno-relax'. For
8672 PCREL_LO12_I/S relocation, do fixup and mark as done while with
9319 - the string "[ No Source Available ]".
10006 sim: rx: mark unused static var as unused
10008 helper, so mark it as unused rather than delete.
10705 index() in string.h, which triggers a "shadows a global declaration"
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
11256 gnulib: mark configure +x
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
12426 completions available. Only string elements of the sequence
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.
14489 Windows and AIX. Use std::string instead. I'm not able to test this
15048 - A string: The handler can return a filename, which is the file
15361 2023-11-13 Mark Wielaard <mark@klomp.org>
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
17266 * po/bfd.pot: Regenerate.
17281 * po/bfd.pot: Regenerate.
17295 * po/bfd.pot: Regenerate.
17805 gdbsupport: mark array_view::slice with [[nodiscard]]
18127 producer string.
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
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.
20222 sim: mips: fix printf string
20560 we'll mark it again at the end if needed. If the target is not in
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.
21921 BFD, the filename for this BFD is literally the string
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
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
22806 string.
23096 x86-64: Add -z mark-plt and -z nomark-plt
23113 The dynamic tags have been added to the x86-64 psABI to mark such PLT
23118 Add an x86-64 linker option, -z mark-plt, to mark PLT entries with
23139 in PLT entry for -z mark-plt.
23142 -z mark-plt.
23164 * ld.texi: Document -z mark-plt and -z nomark-plt.
23168 * testsuite/ld-x86-64/mark-plt-1.s: Likewise.
23169 * testsuite/ld-x86-64/mark-plt-1a-x32.d: Likewise.
23170 * testsuite/ld-x86-64/mark-plt-1a.d: Likewise.
23171 * testsuite/ld-x86-64/mark-plt-1b-x32.d: Likewise.
23172 * testsuite/ld-x86-64/mark-plt-1b.d: Likewise.
23173 * testsuite/ld-x86-64/mark-plt-1c-x32.d: Likewise.
23174 * testsuite/ld-x86-64/mark-plt-1c.d: Likewise.
23175 * testsuite/ld-x86-64/mark-plt-1d-x32.d: Likewise.
23176 * testsuite/ld-x86-64/mark-plt-1d.d: Likewise.
23177 * testsuite/ld-x86-64/x86-64.exp: Run -z mark-plt tests.
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…
24162 root 1 0 0 11:45 pts/0 Ss 0:00 /bin/bash
24165 Fix this by also accepting bash as a valid cmd.
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.
25644 value_free_to_mark (const struct value *mark)
25647 auto iter = std::find (all_values.begin (), all_values.end (), mark);
26453 not using the actual contents of the string.
26457 scenario where a string like this can really be returned.
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.
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.
27807 ensuring "string" is freed. Use get_absolute_expression in
28645 2023-08-28 Mark Wielaard <mark@klomp.org>
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
28981 2023-08-25 Mark Wielaard <mark@klomp.org>
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.
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.
33726 [gdb/symtab] Fix data race on dwarf2_per_cu_data::{mark,is_debug_types}
33803 - the main thread writing to dwarf2_per_cu_data::mark.
33805 The two bitfields dwarf2_per_cu_data::mark and
33808 Fix this by making dwarf2_per_cu_data::mark a packed<unsigned int, 1>.
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.
35164 …p_debug_symbols_for_elf_relocatable): Do not add sections containing the string "debug_" to the li…
36924 std::string. Return section name for STT_SECTION symbols with
36938 bpf: format not a string literal
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
38666 script, and the intention is that, should this proc fail, we'll mark
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
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.
41653 using the address offset style, and mark the memory access instructions'
41693 Add a flag in the pinfo field for being able to mark certain specialized
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
43457 [gdb/testsuite] Remove f-string in gdb.python/py-unwind.py
43459 "SyntaxError: invalid syntax" due to usage of an f-string in test-case
43462 Fix this by using string concatenation using '+' instead.
44212 Transfer ownership of exception string to ada_catchpoint
44214 ownership of the exception string can be transferred to the catchpoint
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
44634 Co-Authored-By: Mark Wielaard <mark@klomp.org>
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
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.
45561 xfail_from_runlist: remove an element and mark it xfail.
45791 [gdb/python] Fix doc string of valpy_const_value
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.
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,
46732 configuration string.
47453 mark value to NULL to indicate that the value chain had already
47454 been freed to mark.
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
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,
48758 set expected_lbound $expect_out(1,string)
48992 "&str" is an important type in Rust -- it's the type of string
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
49407 prints complete string, which is not what the user asked for.
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.
49555 as the DisassemblerResult.string attribute, but can be useful
49898 Next, rw_pieced_value did not mark these bits as optimized-out,
50435 * debug.c (struct debug_type_s): Add mark.
50436 (debug_write_type): Set mark and check before recursing into
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,
51093 2023-05-03 Mark Wielaard <mark@klomp.org>
51251 2023-05-02 Mark Wielaard <mark@klomp.org>
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
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:
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"
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.
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
55055 string "[ No Assembly Available ]" ends up in that same spot:
55755 either a gdb.Symbol or a string, while the second, optional, argument
55764 File "<string>", line 1, in <module>
55773 File "<string>", line 1, in <module>
55796 File "<string>", line 1, in <module>
55797 TypeError: Argument must be a symbol or string.
55805 File "<string>", line 1, in <module>
56092 (stab_push_string): Don't strdup string. Use it thoughout
56234 under bfd/po/, i.e. in maintainer mode.
56300 for string passed to debug_start_source and push_bincl. Copy
56996 File "<string>", line 1, in <module>
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.
57074 stab string passed to parse_stab. Free stab string when
57078 * stabs.c (parse_stab): Add string_used param. Set if string
57995 range needs its own hard-coded string, which is a bit cumbersome
58616 - gdb.PendingFrame.language: Return a string containing the
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?),
59231 this string when possible, and updates the test suite.
59242 reason string.
59372 /bin/bash: line 0: exec: non-existing-program: not found^M
59383 /bin/bash: line 0: exec: non-existing-program: not found^M
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).
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
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.
61125 match string, and the full symbol name within the
61137 | | '--- completion match string
61142 string using the completion match string (parse), but excluding the
61144 completion match string, then GDB tries to do some weird string
61199 our match string, and this will cause GDB to crash.
61354 completer to pass invalid arguments to string::append.
61463 Regen ld/po/BLD-POTFILES.in
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
62449 zero size string section.
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.
63347 string if the directoty table has relative names.
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.
64423 bash: $outputs/gdb.base/signals-state-child/signals-state-child-standalone: \
64436 bash: signals-state-child-standalone: command not found^M
64901 rather than bash, I get:
64913 difference is listed in the documentation for bash's POSIX-correct mode
64953 [1] https://www.gnu.org/software/bash/manual/html_node/Bash-POSIX-Mode.html
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.
65254 * macro.c (macro_expand): Ensure input string buffer is not
65317 File "<string>", line 1, in <module>^M
65526 convert the thread_info* into a string.
65708 The failure is caused by the 'evaluated-by="host"' string, which only
65899 2023-02-28 Mark Harmstone <mark@harmstone.com>
65930 * ecofflink.c (mk_fdrtab): Sanity check string offsets.
66711 gdb: make-target-delegates.py: make one string raw
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
69063 Therefore there shouldn't be any at the end of the format string.
69358 bash: line 1: foobar: command not found
69837 gdb: use std::string for internalvar::name
69838 Change internalvar::name to std::string, automating memory management.
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
70109 This inserts a zero-terminated string into the output at the place where it is used.
70781 gdb/testsuite: handle differences in guile error string output
70805 updates the test regexp to handle this optional 'ERROR: ' string.
71044 once the string we are looking for ('foo' here) is exhausted, if we
71739 Use std::string in main_info
71740 This changes main_info to use std::string. It removes some manual
74113 string.
74117 2023-01-30 Mark Wielaard <mark@klomp.org>
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.
74732 Now however, we sometimes only write a partial string to the pad,
75013 2023-01-27 Mark Harmstone <mark@harmstone.com>
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
75344 2023-01-25 Mark Harmstone <mark@harmstone.com>
75348 2023-01-25 Mark Harmstone <mark@harmstone.com>
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]
75950 2023-01-24 Mark Harmstone <mark@harmstone.com>
75958 2023-01-23 Mark Harmstone <mark@harmstone.com>
75969 2023-01-23 Mark Harmstone <mark@harmstone.com>
76183 An earlier patch failed to update a string in allow_aarch64_sve_tests.
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
76890 Limit on string chars or array elements to print is 200.
76901 This setting also applies to string chars when "print characters"
77195 2023-01-19 Mark Wielaard <mark@klomp.org>
77291 2023-01-18 Mark Harmstone <mark@harmstone.com>
77674 2023-01-15 Mark Wielaard <mark@klomp.org>
77726 need to mark the igen tool as a recursive dep. Each port depends on
78102 Calling strncat with the size of the src string is not so meaningful.
78525 2023-01-10 Mark Harmstone <mark@harmstone.com>
78534 2023-01-10 Mark Harmstone <mark@harmstone.com>
78542 2023-01-10 Mark Harmstone <mark@harmstone.com>
78553 2023-01-10 Mark Harmstone <mark@harmstone.com>
79298 * po/SRC-POTFILES.in: Regenerate.
79442 * readelf.c (process_dynamic_section): Correct format string.
79503 Older bash looks to improperly deal with backslashes in here-documents,
79763 set length $expect_out(1,string)
80056 2023-01-04 Mark Harmstone <mark@harmstone.com>
80412 The cced7cacecad104fff0 ("gdb: preserve `|` in connection details string")
80430 that this string is being passed verbatim to gdbserver -- which seems
80580 string "Copyright (c) 2006, 2012, Oracle and/or its affiliates. All
80587 embedded cr in binutils/testsuite/binutils-all/ar.exp string match.
80659 2022-12-31 Mark Harmstone <mark@harmstone.com>
80665 2022-12-31 Mark Harmstone <mark@harmstone.com>
81330 or need them to be writable, so mark them all const.
81604 2022-12-23 Mark Harmstone <mark@harmstone.com>
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
82445 Regen opcodes/po/POTFILES.in
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
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
83721 string 'faked for "readnow"' in the output. This is implemented in
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.
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
84534 assembly data, move it there. While doing so mark respective entities
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
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:
86798 gdb: mark disassembler function callback types as noexcept
86812 In this commit I mark all the callback types as noexcept. This means
86873 gdb/disasm: mark functions passed to the disassembler noexcept
86909 new use of the disassembler classes in the future, and forgets to mark
88297 2022-11-24 Mark Harmstone <mark@harmstone.com>
88430 2022-11-23 Mark Harmstone <mark@harmstone.com>
88582 need to test for gcc in gdb.dwarf2/clang-cli-macro.exp and mark it as
88589 in string.h, which triggers a "shadows a global declaration" warning
88778 string is defined here
89458 File "<string>", line 1, in <module>
89461 assert string == expected_result
89475 want the actual string "\x000".
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…
91563 sim: igen: mark error func as noreturn since it exits
91565 sim: igen: mark output funcs with printf attribute
92078 2022-11-10 Mark Harmstone <mark@harmstone.com>
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
92778 an ISA string and/or disassembling, not to allow hard-float with RVE.
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
94057 These functions only read from memory, so mark the pointer as const.
94060 These functions only read from memory, so mark the pointer as const.
94063 These functions only read from memory, so mark the pointer as const.
94187 2022-10-31 Mark Harmstone <mark@harmstone.com>
94381 # bash$ make check RUNTESTFLAGS="--target_board=remote-stdio-gdbserver \
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.
94826 /bin/bash: connect-with-no-symbol-file: Permission denied^M
94827 /bin/bash: line 0: exec: connect-with-no-symbol-file: cannot execute: \
95400 (_riscv_relax_delete_piecewise): Just mark the deleted bytes as R_RISCV_DELETE.
95681 FAIL: gdb.base/unwind-on-each-insn.exp - instruction 104340: [string equal $fid $main_fid]
95887 * po/hu.po: Updated Hungarian translation.
96211 2022-10-20 Mark Harmstone <mark@harmstone.com>
96306 Regen ld/po/BLD-POTFILES.in
96418 sim/ppc: mark device_error function as ATTRIBUTE_NORETURN
96443 This commit is mostly either changing the format string to match the
96885 compares their name or build id to the user-provided search string.
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)
97585 evsubiw before evsubifw and mark EXT.
98232 implementation-defined manner, the result with format string containing
98242 After the recent series of fixes to mark more functions in the
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
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] {
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
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)
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);
103313 …/libxul.so-100.0-2.fc35.x86_64.debug: attempt to load strings from a non-string section (number 38)
103523 bfd, binutils, gas: Remove/mark unused variables
103797 2022-09-13 Mark Harmstone <mark@harmstone.com>
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
107313 PPC_OPERAND_PLUS1 fits perfectly to mark that maximal value should be
107456 2022-08-10 mga-sc <mark.goncharov@syntacore.com>
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
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.
108810 x86: properly mark i386-only insns
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.
110192 source: file path and line number tuple: (string, long) / None
110690 If this is set to a non-empty string, Python won't try to write
110694 an empty string check.
111678 $5 = "Traceback (most recent call last):\n File \"<string>\", line 0, \
111681 $6 = "Traceback (most recent call last):\n File \"<string>\", line 1, \
112372 * tc-arc.c (md_assembly): Update strspn string with the
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
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.
114935 x86: introduce fake processor type to mark sub-arch entries in cpu_arch[]
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.
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.
116037 File "<string>", line 1, in <module>^M
116048 changing it into a string works:
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
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.
117531 && ![string equal $output "No MPX support\r\n"]]
117546 zero string terminator when fgets returns NULL.
117624 While at it fixed format string for time-related types.
117795 disassembler, it's really just a wrapper around a string (the text
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
117983 2022-06-15 Mark Wielaard <mark@klomp.org>
118304 allocated string (that should be freed) by returning a char * rather
118326 (dwarf2_directive_loc): Free remap_debug_filename string.
118400 instead of bash.
118450 File "<string>", line 1, in <module>^M
118491 x86: avoid string copy when swapping Vex.W controlled operands
118776 [4] system.traceback.symbolic.value (system.address) return string at \
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
119588 I noticed that solib_name_from_address returned a non-const string,
119596 _() around a string using in an error call.
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
119837 I've used as overflow string: "Integer literal is too large", based
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,
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
121157 argument, the language string, which will be passed though to the
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
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
122365 the command string, and, it's also more explicit.
122780 2022-05-23 Mark Harmstone <mark@harmstone.com>
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
123590 * bfdio.c (_bfd_real_fopen): Delete ccs string.
123847 A string the first two characters of which do not match "if" also wont
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
124358 2022-05-12 Mark Wielaard <mark@klomp.org>
124546 the "Symtabs:" string, and consequently the corresponding
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
126008 2022-05-04 Mark Wielaard <mark@klomp.org>
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
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__'
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.
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
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.
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
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.
131525 gdb: change file_file_name to return an std::string
131526 Straightforward change, return an std::string instead of a
132082 2022-04-07 Mark Harmstone <mark@harmstone.com>
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
132379 return the address, rather than a string.
133885 undefined, and so expands to the empty string. As a result TAGS does
134122 The fingerprint for a layout is represented as a string, the string is
134564 Regen bfd po/SRC-POTFILES.in
135133 The fix I came up with is to mark the secondary thread as !stopped (or
135918 lex the next token after handling a string token. This is also fixed
136316 The last section in a CTF dict is the string table, at an offset
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
136820 This method takes an address, and returns a string with the format:
137560 (std::unordered_map<std::string, gdbpy_ref<micmdpy_object>>). While
137920 * po/SRC-POTFILES.in: Regenerate.
138029 https://lists.gnu.org/archive/html/bug-bash/2018-01/msg00097.html
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.
138975 lists, iterators, or an object that can be converted to a string.
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]"
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.
140301 The vDSO objfile is not a real file, so mark it as such. I noticed
140779 literals. gdb does not generally seem to handle the Ada wide string
140791 <1130> DW_AT_name : (indirect string, offset: 0x19ff): QW0178
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
141136 This patch attempts to cover the basics of string matching, white
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_*.
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
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.
142279 sim/testsuite/cris: If failing compilation, mark C tests as errors
143199 I also reformatted one of the index_cache_debug where a string will
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:
144523 case it uses the symbol lookup if the string contains a +. When it isn't
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,
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
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.
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
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
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
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
147429 + string is less than length computed by dlang_number.
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
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
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
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.
151038 calls are what would serve to mark the new thread as resumed.
151348 'GNU/Linux native target'. The body string for this setting has been
151444 incoming string.
151687 mark the async event token. I've modified this so we only mark the
151691 back on (see remote_target::async) we will mark the event token if
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,
152601 gdb: Powerpc mark xfail in gdb.base/catch-syscall.exp
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.
153789 replacing it with a simpler use of std::string.
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
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
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.
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.
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
156058 'details': A string or None. Extra details for the connection, for
156151 are NULL string in the riscv_vsew and riscv_vlmul, so dump the
156290 Update description of string's -n option.
156524 sim: hw: mark hw_descriptors const
156963 * po/BLD-POTFILES.in: Regenerate.
156964 * po/SRC-POTFILES.in: Regenerate.
156969 * po/fr.po; Updated French translation.
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&)
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
159473 DEBUGINFOD_URLS_ENV_VAR), or use a dummy string to store the setting,
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
159976 * po/POTFILESin: Regenerate.
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.
160230 to use %s with an empty string to avoid the compiler warning but not
160369 string table if needed.
160850 We have to mark the psh* tests as shdsp only (to match what the exp
160851 file was doing), mark the fsca & fsrra tests as failing (since they
160858 Move some unused funcs under existing #if 0 protection, mark a few
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
161771 * ldlex.l (double quote string): Use xmemdup.
161775 sim: mloop: mark a few conditionally used funcs as unused
161785 fast-build mode settings, so mark it unused too.
162447 Add 'set/show debuginfod urls' commands. Accepts a string of
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
163037 This patch changes windows-nat.c to mark all threads needing a debug
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
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.
164191 PR28417, std::string no longer allows accepting nullptr_t
164194 std:string undefined behaviour.
164228 Use std::string in print_one_catch_syscall
164229 This changes print_one_catch_syscall to use std::string, removing a
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
165664 Limit on string chars or array elements to print is unlimited.
165749 The PR28401 testcase has a section named "", ie. an empty string.
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;
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 *`
167104 Also use with_test_prefix to mark the nodebug part, such that we have:
167406 File "<string>", line 1^M
167645 I made a mistake in the previous patch. Adjust the format string to
168036 (intel_operand_size): mark invalid broadcast with no_broadcast=1.
168240 format string.
168901 File "<string>", line 1, in <module>
168904 File "<string>", line 25, in warm_up
168991 <14ff> DW_AT_name : (indirect string, offset: 0x215e): nb_bytes
169002 <1650> DW_AT_name : (indirect string, offset: 0x218d): nb_bytes
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.
171140 @object, .4byte instead of .long, and .asciz instead of .string.
171254 - std::string
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
172374 * po/BLD-POTFILES.in: Regenerate.
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.
172831 to mark the start addresses of data and instructions. The $d means
172871 * Use $d and $x to mark the distribution of data and instructions.
173034 that string is non-NULL.
173927 and only one versioned symbol, don't remove the symbol. Instead, mark
173942 if it is used on relocation. Instead, mark it as to be removed
174407 exits, in bash for example "Segmentation fault" rather than "Aborted".
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 *…
177187 Total memory used for string cache: 4064^M
177331 when calculating string table file location.
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.
179043 Also mark this FAIL:
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.
180034 …/nix/store/26a78ync552m8j4sbjavhvkmnqir8c9y-bash-4.4-p23/bin/bash: ./make-init-c: /usr/bin/env: ba…
180672 values). Add a ptid_t::to_string method that returns a string
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
181972 File "<string>", line 1, in <module>
181975 File "<string>", line 49, in execute_test
182129 rather than string literal.
182265 string length of a string argument is int, not size_t.
182276 $integer4 for size of string length.