Lines Matching +refs:clang +refs:rename +refs:format +refs:message
100 original Binutils commit message that mistakenly included it only in armv9.4-a.
797 Note that, GAS instruction (ginsn) format does not support
1095 - gcc and clang (to trigger both the has_stderr_symbol true and false cases)
1167 input format is not recognized. This problem occurs in the function
1540 format; if the UnwindInfo references an invalid frame, then the
1661 exited message that GDB prints.
1852 Determine whether to output operands through the format
1853 of opcodes. When opc->format is an empty string, no extra
1905 While gcc propagates the printf attribute via the typedef, clang
2092 … gcc/gengtype-parse.cc:142:21: error: ‘%s’ directive argument is null [-Werror=format-overflow=]
2923 sim: igen: fix format-zero-length warnings
3798 files (which should have their copyright message removed).
3872 the places in GDB where we catch an error and repackage the message
3997 sim: ppc: rename local ALU SIGNED64 macros
4054 earlier message by Pedro Alves <pedro@palves.net>:
4205 42 shr1 ("message 1\n"); /* shr1 one */
4248 options are supported on clang and gcc version 7 and newer.
4250 Patch has been tested on PowerPC with both gcc and clang.
4411 sim: ppc: rename igen max_insn_bit_size
4701 and tls le insn format check.
5825 Easiest way around it is to rename the per-substep vars as needed as
5836 Delete redundant decls, and rename conflicting vars.
5889 Remove duplicate nested variable declarations, rename some to avoid
5953 Fix build with clang 16
5954 clang 16 reports a missing declaration in new-op.cc. We believed
6299 rename syscall since we can't rename files that have been removed.
6351 be four bytes in the DWARF 32-bit format and eight bytes in the DWARF
6352 64-bit format, while DWARF Version 2 specifies that such references have
6811 format, and instruction description.
6826 When the s390-mkopc utility detects an error it prints an error message
6833 prints an error message to stderr and sets the final return code to
6911 * format.c (io_reinit): Revert last change. Comment.
6967 However, clang doesn't use the CFA and instead relies on specifying when
6977 that handled this exact flaw in clang.
7190 (1) The 'Thread-specific breakpoint 3 deleted ....' message, and
7701 * format.c (io_reinit): Free BFD_IN_MEMORY iostream.
7868 gdb: rename gdbarch_pseudo_register_write to gdbarch_deprecated_pseudo_register_write
8408 That the error message mentions '/tmp/hello', which does exist, but
8412 Also, I find the 'mkstemp' in the error message confusing for a user
8414 they do, that it appears in the error message is an internal GDB
8514 error message:
8946 message.
9372 gdb.python/py-symtab.c with clang, I noticed that it was going wrong
9376 not true for clang compiled binaries.
9441 syslog (the format), so use %s as the static format instead since
9487 message "Process record does not support instruction 0xf01f9".
9800 message:
10482 --rename-section.
10803 format.
11009 and rename to riscv_is_valid_mapping_symbol.
11098 standard approach that, presumably, clang supports.
11318 The BPF assembler has been updated to follow the clang convention in
11325 The BPF assembler in clang uses semi-colon (;) to separate statements,
12614 Fix building for the s390 target with clang
12697 * config/tc-s390.c: Add support to insert operand for format
12698 R_CP16_28, reusing existing logic for format V_CP16_12.
12733 wrong RR register format must be retained. Since the superfluous second
13726 gdbsupport/format.h:format_piece::format_piece.
13839 …c (_bfd_generic_link_add_one_symbol): When issuing a warning message, also display a message about…
13845 In AIX, we are not able to see the message of a signal recieved if a debugee recieves a signal.
14288 - in particular, remove get_thread_arch_regcache, and rename
14323 DAP specifies that a request can fail with the "notStopped" message if
14426 x86: conditionally hide object-format-specific functions
14962 XXX: Consume first worker thread message
15236 …New function. Contains common code found in dump functions. Adds a note message if a compressed s…
15359 * lexsup.c (ld_options): Ensure that the --format option is correctly recognised.
15365 changed gas/config.in to rename USE_E_MIPS_ABI_O32 to USE_EF_MIPS_ABI_O32
16933 supports the IBM double 128-bit floating point format and IEEE 128-bit
16934 format. The IBM double 128-bit floating point format uses two 64-bit
16936 floating point format stores the value in a single 128-bit vector-scalar
18251 This matches clang's assembler behavior.
18407 [4] https://clang.llvm.org/cxx_status.html
18723 gdb/testsuite: add a clang XFAIL to gdb.python/py-watchpoint.exp
18733 gdb/testsuite: fix running gdb.python/py-explore-cc with clang
18735 failure. This was due to how clang mapped instructions to lines,
18739 add XFAILs for existing clang releases, if this gets solved in future
18838 Added format attribute to several gprofng functions.
18853 * libcollector/libcol_util.h: Added format attribute.
18941 so it can output an error message normally.
19325 gdb: rename struct so_list to shobj
19527 gdb: rename lm_info_base to lm_info
19708 hipDeviceSynchronize and friends, and print an error message when
20168 message. (md_parse_option): Accept "lp64e".
20171 Change error message.
20295 (nto_create_output_section_statements): rename nto_after_open
20589 Make remote_async_inferior_event_token private (rename to
21320 * elf64-alpha.c (elf64_alpha_check_relocs): Correct error message.
21970 the output should be a warning rather than just a message printed to
22002 warning message correctly.
22006 a really weird case, as after printing this message GDB just does a
22020 procfs.c, I noticed that we used a static errmsg buffer to format some
22025 message format that needed updating. In one case we gained an extra
22054 there is a diagnostic message that can be printed, and in some cases
22055 we might use the wrong filename in the message.
22059 If this file has been removed from disk then we print a message that
22580 slightly reworded warning message.
22618 In preparation to the SME support patches, rename the SVE-specific files to
23225 Also, while testing with CC_FOR_TARGET=clang, I found that
23226 'additional_flags=-Wl,-soname=${binsharedbase}' caused clang
23231 but I've done additional testing with CC_FOR_TARGET=clang as
24016 and c-exp.c.tmp. Just include it in the list of symbols we rename.
24440 The new Synopsys ARCv3 ISA has a similar instruction format like
25197 produce a similar warning message when stopping due to a watchpoint if
25426 compilers such as clang don't add debug information about stderr by
26071 gdb/doc: rename "x86 Architecture-specific Issues" section to "x86"
26873 gdb/testsuite: Make hook-stop.exp ignore termination message from GDB stub
27181 arm: Make 'conflicting CPU architectures' error message more user-friendly
27197 message.
27359 x86: rename CpuPCLMUL
27481 Add these two methods, rename the field to m_bitsize to make it pseudo
27506 Add these two methods, rename the field to m_artificial to make it
27651 format." Tom further observed, "...it seems like it could result in an
28564 standard format as queried from CPUID.
28618 "compact" format which uses an alternate layout, but existing OS's
28649 an error message. Use hex_string instead.
28847 flavour may be incorrect. The format won't have changed but checking
28857 format.
28929 i386: warning: format ‘%u’ expects argument of type ‘unsigned int’,
28933 * i386-gen.c (process_i386_opcodes): Correct format string.
29279 testing with clang-15 from around 150 to 2, and correctly identifies
29290 anything, whereas clang assumes that the output is in %rax, and writes
29315 gdb/testsuite: fix testing gdb.reverse/step-reverse.exp with clang
29328 emitted when using clang.
29334 gdb/testsuite: fix gdb.reverse/solib-*.exp tests when using clang
29337 function. Not all compiles do this, one example being clang. To fix
29354 gdb/testsuite: Fix many errors in gdb.reverse with clang
29761 To address this I've reworked the message that is printed to include
29783 correct location, and the error message describes which signal caused
29788 error message, but, in the end, I opted not too. I wasn't sure it was
29908 exit_inferior_silent are all equivalent, so rename exit_inferior_1 to
30089 uint64_t to match format string.
30091 use PRIx64 in format string.
30387 the entry count uleb is ridiculously large, and format attributes
31004 When building gdb with clang 15 and -std=c++20, I run into:
31021 When building gdb with clang 15 and -std=c++20, I run into:
31067 overflows the same way than the clang BPF assembler:
31398 thread, read the commit message for the justification for this change.
33578 Remove extra '.' from error message
33579 A local gdb test failed with this error message:
34084 [gdb/symtab] Fix data race on bfd::{cacheable,format}
34130 #0 bfd_check_format_matches bfd/format.c:323 (gdb+0x1492db4)
34131 #1 bfd_check_format bfd/format.c:94 (gdb+0x1492104)
34171 the process reading bfd::format, and
34175 The two bitfields bfd::cacheable and bfd::format share the same bitfield
34317 gdb/testsuite: Disable gdb.compile when testing with clang
34318 Attempting to test the gdb.compile with clang as the compiler results in
34695 Avoid the use of sprintf with a "%s" format string, replacing with
34799 /usr/include/bits/stdio2.h:30:10: error: null destination pointer [-Werror=format-overflow=]
36609 comment character, which clang -S seems to use.
36707 The change to use -nostdlib and rename main to _start was originally added
36938 bpf: format not a string literal
36980 instructions. The templates match the strings emitted by clang -S for
37305 consistency, if the message I've updated also talks about the sibling
37315 and resume_stopped_resumed_lwps is called. Previously the message
37320 After this change we now get a message saying that the thread is not
37322 With this message the already resumed nature of the thread is much
37552 bytes of the instruction in an implementation-defined format. This
37554 bytes as the format.
37780 and with gcc 7.5.0 and clang 13.0.1, for which we still consistently get:
38034 some more printf format problems when the host is 32-bit.
38038 * od-elf32_avr.c (elf32_avr_dump_mem_usage): Correct format
38045 * config/tc-d10v.c (find_opcode): Correct format specifier vs.
38711 * emultempl/pe.em (read_addend): Use %H in error message.
39027 error message look cryptic. It was reported in bugzilla as PR cli/30497.
39221 Merge and rename to tui_border_kind_translate_corner.
39331 because gdb never prints that message anyway.
39690 gdb: include location number in breakpoint error message
39696 gdb: include breakpoint number in testing condition error message
39698 The earlier commit extended the error message:
39946 string, we're just constructing a printf format specifier for a hex
40066 "rename" conflicts with a function of that name, which gcc from that
40392 block, and then a message to show how many more were elided (if any).
40405 message containing the size of the dictionary ... so we don't really
40546 which should be the current thread. The above message is reported
40572 and, when these are found, should rename these sections using some
40773 1" message. This is caused because linux_core_pid_to_str reports
40775 second, the "The current thread has terminated" message. This is
41307 * config/tc-riscv.c (validate_riscv_insn): Add 'l' as new format
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'.
41764 Add details for the changes made from Version 1 to Version 2 of the format.
41766 Also add details about alignment in the SFrame format. A portion of the
41767 SFrame stack trace format has an unaligned on-disk representation. Add
41773 sframe: bfd: gas: ld: format bump to SFrame version 2
41775 in the format. Add information in the SFrame FDE to convey the size
41792 SFRAME_VERSION_2 format. If the input sections offered to the linker
41793 are not all in the SFRAME_VERSION_2 format, the linker issues an error
41796 objdump/readelf will show the following message to the user if .sframe
41797 section in SFRAME_VERSION_1 format is seen:
41803 format version, i.e., SFRAME_VERSION_2 is supported by the textual dump
41846 format is seen.
41865 format evolves.
41918 encoded in the format, as it may be different for each ABI.
41920 In SFrame Version 2 of the format, we will move towards encoding it
42023 format error when dynamic symbol table is used.
42326 Use uint8_t consistently for identifying ABI/arch in SFrame format.
42468 include/sframe.h (the SFrame binary format definition). This ties up
42740 Python 3.11 changed the AttributeError message - see commit
42742 messages (GH-31311)"). Add the new message to the expectations.
42808 DAP allows a source breakpoint to specify a log message. When this is
42809 done, the breakpoint acts more like gdb's dprintf: it logs a message
42813 format. However, my initial attempt at this did not work, because
42983 PR30536, ppc64el gold linker produces unusable clang-16 binary
43070 'prepare_resume_reply' for a more readable log message.
43755 relocation special_function, and construct the message using asprintf.
43766 * bfd.c (_input_error_msg): Make global and rename to..
43961 performs a similar check and outputs a suitable error message.
43975 message notes that it was not tested with armflang.
43993 …$ clang-13: warning: argument unused during compilation: '-fdiagnostics-color=never' [-Wunused-com…
44454 bytes by libsframe. In next version of the SFrame format, we can encode
44848 This patch makes it so the warning message is printed only once per
44960 Add extra linker warning message about discrepancies between normal and common symbols.
44962 …bfd * elflink.c (elf_link_add_object_symbols): Add a message indicating that alignment and size di…
45084 output message when "memory-tag check" is issued with no arguments. That's
45085 because I coded the message using "error" and missed a period at the end. Other
45293 message is new, but copies bits from everyone's earlier work.
45485 currently leak memory. Keep a static pointer to the message and free
45518 We also add an extesion format of cftc2/cttc2/mftc2/mfthc2/mttc2/mtthc2:
45779 [gdb/tdep] Fix typo in debug message
45869 [gdb/compile] Fix typo in debug message
45881 [gdbserver] Fix typo in debug message
45960 Reduce translation work of "invalid symbol index" error message.
45976 libsframe, and use it. Note that the SFrame format does not define such
46169 noticed that it implied that the format parameter is optional, which
46290 This commit adds a new format for the printf and dprintf commands:
46291 '%V'. This new format takes any GDB expression and formats it as a
46370 The new %V format solves all these problems: the string is computed
46372 actual arrays rather than pointers, and we can pass named format
46410 When dprintf-style is 'call' the format string and arguments are
46416 any restrictions on the format string when operating in 'call' style.
46418 custom print format specifiers (maybe including '%V') so, I claim, it
46425 process the format string and send the dprintf command to the remote,
46443 Unrecognized format specifier 'V' in printf
46447 This is exactly how GDB would handle any other invalid format
46465 Unrecognized format specifier 'Q' in printf
46469 The error message isn't the greatest, but improving that can be put
46706 signal stop message. Since the amdgpu and the CLI code both use
46712 that the amdgpu message gets printed after the CLI message, since
46900 (loongarch_elf_adjust_dynamic_symbol): Fix code format.
46903 (RELOCATE_CALC_PC32_HI20): Fix code format.
47224 Enhance objdump's --private option so that it can display the contents of PE format files.
47225 * od-pe.c: New file: Dumps fields in PE format headers.
47226 …c (od_vectors): Add objdump_private_desc_pe for PE format targets. (od_files): Add od-pe for PE fo…
48056 When testing gdb.arch/disp-step-insn-reloc.exp with clang in an x86_64
48100 The epilogue of set_point0 (11cf for clang, 401146 for gcc) is the main
48102 based on rbp, while clang adds the same constant to rsp that it
48536 message.
49373 parent. This lets us avoid a clang dependency in the test.
49629 gdb: fix error message for $_gdb_maint_setting
49907 downloaded if the size information is available at the time the message
49917 A pattern in crc_mismatch.exp fails to be matched if a progress message
49919 the progress message whether or not it includes the file size.
51425 fix) and a message:
51926 error message).
52037 target or object format.
52389 newline at the end of any warning message.
52397 of the warning message (in addition to the trailing newline), which
52400 message isn't even that long (71 characters), so I think removing this
52596 clang/llvm and is also used in inline asm templates in kernel code, so
52836 arranging for a guaranteed subsequent error message by marking the
53478 - Remove auto_language, rename auto_or_unknown_language to
54097 gdb: re-format Python code with black 23
54118 and format fields from the _Float128 typedef are copied to the long
54876 * format.c (struct bfd_preserve): Move some fields. Add
54898 * format.c (io_reinit): New function.
55191 * format.c (struct bfd_preserve): Add iovec and iostream fields.
55247 Replace an assertion in the dwarf code with a warning message.
55263 Fix an attempt to allocate an overlarge amount of memory when decoding a corrupt ELF format file.
55699 Clang with LTO (clang -flto) garbage collects unused global variables,
55705 RUNTESTFLAGS="CC_FOR_TARGET='clang -flto' CXX_FOR_TARGET='clang++ -flto'"
55733 format it with black:
55758 I'm now using 'O!' as the format specifier for the second argument,
55785 2. New error message gives argument position and expected argument
55791 message we see above. If the first argument has the wrong type then
55868 as the argument format for the function's value argument. This means
55872 message (at least, I think so). Previously we would get something
56115 gdb/testsuite: Default to assembler's preferred debug format in asm-source.exp
56116 The stabs debug format is obsolete and there's no reason to think that
56118 format wasn't set in asm-source.exp then leave it to the assembler to
56406 that GDB reports the segfault, and then gives an error message that
56414 message GDB currently prints might give the impression that GDB is
56417 Also, I find the second stop message draws attention away from
56419 message, and this second stop might be thought of as replacing in
56420 someway the earlier message.
56422 In short, I think things would be clearer if the second stop message
56466 I've updated the existing tests that checked the error message printed
56622 gdb: include breakpoint number in testing condition error message
56624 whatever reason, the error message looks like this:
56642 was #1 because in the final line of the message GDB reports the stop
56688 breakpoint #1 will be lost from the error message.
56718 error message in detail.
57002 verbose error message, like this:
57618 FRINT*, which share the same format.
57621 FCLAMP, SCLAMP and UCLAMP share the same format, although FCLAMP
57625 [BSU]MOP[AS] share the same format.
57640 BFDOT, FDOT and USDOT share the same instruction format.
57641 SDOT and UDOT share a different format. SUDOT does not
57646 SMLALL, SMLSLL, UMLALL and UMLSLL have the same format.
57748 SME2 adds a new format for the existing SVE predicate registers:
57838 possibilities to be summed up in a single message.
57933 "did you mean this?" message.
57982 Also, the register list operands used a general error message,
58168 This patch tweaks the error message that is printed when
58507 generic meaningless error message, but we still get the "missing 'sp'
58990 gdb: move displaced_step_dump_bytes into gdbsupport (and rename)
59452 ld:watch.rs: file format not recognized; treating as linker script
59907 casts are no longer needed, and where printf format strings or tests
60649 relocated addresses again") changed the format of that command, but
61245 commit message as I originally wrote it, but it should be read within
63223 [gdb/testsuite] Fix untested message in gdb.tui/corefile-run.exp
63850 The problem is that the new thread message doesn't match the regexp, which
63856 Fix this by accepting this form of new thread message.
63879 message which we do see with native testing:
63886 The fact that the message is missing was reported as PR remote/30129.
63889 to test has nothing to do with the message, so it should pass. I only added
63890 matching of the message in commit 2e5843d87c4 ("[gdb/testsuite] Fix
63894 Fix this by matching the "Thread-specific breakpoint $decimal deleted" message
64065 "invalid" in error message.
64078 OBJF_REORDERED is set for nearly every object format. And, despite
64491 When building with clang 16, I see:
64519 When building with clang 16, we get:
64528 The error message does not make it clear in the context of which enum
64533 clang is right that the value -1 is invalid for the enum type we cast -1
64760 …{"request_seq": 5, "type": "response", "command": "stackTrace", "success": false, "message": "'Non…
64867 (get_relocs): Adjust for struct rename. Don't call bfd_fatal
65198 priority. By reading the format with the most detail last, we ensure it has
65451 from the user. We also print a message indicating that the breakpoint
65628 added in commit 49fa26b0411d, but the commit message offers no clues
65888 …chew.c:1434:59: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 3 has type…
66062 suitable message regarding SIGTERM might be printed; therefore, I
67110 <syscall name="rename" groups="file"/>
68342 more common format.
68367 - non-gcc producers (say, clang).
68532 - clang 4.0.1, 13.0.1
69063 Therefore there shouldn't be any at the end of the format string.
70007 gdb/dwarf2: rename some things, index -> gdb_index
70023 These warnings come from clangd, so ultimately from one of the clang
70024 static analyzers (probably clang-tidy).
71497 a missing source file. The following error message should instead be
71506 to open a source file. Use this value to generate the error message
71523 error message.
71939 x86: move (and rename) opcodespace attribute
72040 "Cause GDB to print structures in an indented format with one member per line"
72157 host pointer, so the test is better done in format-specific code.
72643 Fix this by using UNSUPPORTED instead, and make the message less cryptic:
72793 [gdb/testsuite] Improve untested message in gdb.ada/finish-var-size.exp
72798 The message only tells us that the compiler version too old, not what compiler
73096 The use of a narrow size to handle the mask CGEN in instruction format
73637 SFrame format is meant for generating stack traces only.
73645 SFrame format is meant for generating stack traces only.
73659 SFrame format is meant for generating stack traces only.
73677 SFrame format is meant for generating stack traces only.
73685 SFrame format is meant for generating stack traces only.
73865 gdb/dwarf: rename cooked_index_vector to cooked_index
73866 See previous patch's commit message for rationale.
73873 gdb/dwarf: rename cooked_index to cooked_index_shard
73874 I propose to rename cooked_index_vector and cooked_index such that the
73932 Print the "Cooked index in use" message after the nullptr check, such
73933 that if the cooked index failed to build, that message is not printed.
73967 This is because the format of the "Cooked index in use" line changed
73977 ERROR: wrong # args: should be "xfail message"
74101 …format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 2 has type ‘std::__underly…
74112 The die_offset's underlying type is uint64, so use PRIx64 in the format
74775 descriptor for gdb_stderr, and, as a result, does not currently format
74804 ability to scroll back to view the error message and all of the
74987 interface due to the name being used in the error message, and exposed
75185 …{"request_seq": 17, "type": "response", "command": "disassemble", "success": false, "message": "Ca…
75221 gdb/testsuite/dap: rename dap_read_event to dap_wait_for_event_and_check
75810 a message about the terminal lacking the required abilities.
75841 gdb/testsuite: rename test source file to match test script
75930 When building GDB with clang 16, I got this,
75946 Tested by rebuilding on x86_64-linux with clang 16 and gcc 12.
76112 gcc 7.5.0 and clang 13.0.1.
76885 To make people's life easier the message shown by `show print elements'
76972 Use said error message in all cases (citing the invalid value requested)
76980 message.
77465 gas: arm: Change warning message to not reference specific A-class architecture revision
77466 We noticed that a warning message about the use of scalar fp16
77471 the warning message had become misleading. Here we just change
77472 the message to not specify an architecture revision at all and
77480 ARMv8.2-A from the warning message.
78053 message beginning with _UNTESTED_, appending the `message' argument.
78236 warning message into the right dict.
78270 ctf: fix various dreadful typos in the ctf_archive format comments
78271 When defining a format it helps to a) get the endianness right when you
78338 HTML doc format is gdb/doc/gdb_html, rather than gdb/doc/gdb previously.
78566 https://learn.microsoft.com/en-us/windows/win32/debug/pe-format, and
79415 '-diag-disable=10441' to disable this message.
79440 PR29972, inconsistent format specification in singular form
79442 * readelf.c (process_dynamic_section): Correct format string.
79549 output format.
79557 will print M::x, and using clang 16.0.0 prints N::x. Not only is this
79595 gdb/testsuite: Fix FAILs in gdb.linespec/cpcompletion.exp when using clang
79596 When using clang 16.0.0 to test gdb.linespec/cpcompletion.exp, I get 99
79599 overload3_function or anon_ns_function. This happens because clang is
79632 and printing the "end" message. Decrementing the debug_print_depth
79726 rename it to the less collision-prone `xtensa_rmap` name.
80065 https://learn.microsoft.com/en-us/windows/win32/debug/pe-format, which
80416 This results in the error message below for MinGW hosts:
80557 gdb/copyright.py: Adjust following rename of sim/ppc/ppc-instructions...
80566 Update copyright year in help message of gdb, gdbserver, gdbreplay
80568 and gdbreplay's help message from 2022 to 2023, as per our Start
80720 in a rather confusing "exception did not finish" message. So the problem is
80721 that this message doesn't show up, in other words, the out_of_scope callback
80729 Note that the message does show up later, at thread exit:
81133 sim: mips: rename "igen" generation mode to "single"
81139 this generation mode. So rename the set of rules from "igen" to
81164 sim: mips: rename multi_flags to igen_itable_flags
81166 for merging the itable logic among all ports, rename "multi_flags" to a
81234 (on-disk format). When the host is big-endian, the address of the
81543 Also rename the file to standardize it a bit better with other ports.
81552 Also rename the file to standardize it a bit better with other ports.
81895 Analogous to the above, in SFrame format V1, a bit is reserved in the SFrame
81950 XSAVES, unconditionally using compacted format, in turn effectively
82214 x86: rename CheckRegSize to CheckOperandSize
82239 format string to reduce translation work. elf64-ppc.c loses the
82717 matches. It was quite limited in the style of message supported, only
82718 one message could be printed, and didn't really meet the stated aim of
82748 * format.c (print_warnmsg): New function.
82814 DW_CFA_GNU_window_save in the DWARF format.
82844 The behaviour of the mangled-RA info bit in SFrame format closely
83189 SFrame format is an unaligned on-disk format. As such, there are other blobs
83298 Tested on x86_64-linux, with gcc 4.8.5, 7.5.0 and clang 13.0.1.
83359 not just rename decref_target to target_ops::decref?
83471 As mentioned at the start of the commit message, this commit changes
83632 the printed debug message included the function name, the new debug
83949 function, so first rename the static one in extension.c.
84648 libsframe: rename API sframe_fde_func_info to sframe_fde_create_func_info
84682 future, when the format does evolve to make use of the currently unused
85081 Only rename debug sections when decompressing for linker.
85323 * elf.c (_bfd_elf_make_section_from_shdr): Only rename zdebug
86065 double format, but the actual long double float format is:
86255 return format[0]->name;
86480 fail "$message (GDB internal error)"
88127 gdb: fix typo in debug output message
88128 Spotted a minor type, a missing ')', in a debug message.
88230 …c17f from gcc mainline. Fix gas's acinclude.m4 to stop a potwntial configure time warning message.
88283 * objdump.c (load_specific_debug_section): Use PRIx64 format.
88285 Constify nm format array
88286 * nm.c (formats, format): Make const.
88528 * elfcomm.c (setup_archive): Update error format.
88580 gdb/testsuite: remove gcc restriction from gdb.dwarf2/clang-cli-macro.exp
88582 need to test for gcc in gdb.dwarf2/clang-cli-macro.exp and mark it as
88661 fail "$message (GDB internal error)"
88770 …20: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘ULONGEST’ {a…
88777 /vol/src/gnu/gdb/hg/master/local/gdb/sol-thread.c:416:40: note: format
88813 This patch changes the message so that bkpt_print_id prints the precise
89014 …rintf_chk’ may write a terminating nul past the end of the destination [-Werror=format-overflow=]
89032 PR build/29798 shows a similar error message but on Solaris.
89055 clang, and should work on most, if not all, architectures.
89114 gdb/testsuite: rename source file gdb.debuginfod/main.c
89160 gdb/testsuite: fix gdb.compile/compile-ops.exp with clang
89176 # however, this isn't portable, because other compilers, such as clang,
89836 - using file tail in the untested message.
89907 * binutils/objdump.c: Add support for SFrame format.
90046 with their error message strings are also defined.
90183 FDE are not representable in the SFrame unwind format.
90276 sframe.h: Add SFrame format definition
90277 The header sframe.h defines the SFrame format.
90279 The SFrame format is the Simple Frame format. It can be used to
90283 More details of the SFrame format are included in the documentation
90759 With this patch, the five test cases still fail but with the message "Value
90765 Thus the message "Cannot determine contents" is appropriate in this case.
90999 * testsuite/binutils-all/rename-section-01.d: xfail xcoff.
91014 * testsuite/binutils-all/rename-section-01.d: New test.
91278 so I removed the C++ compilation option. Alternatively we could rename
91368 gdb/testsuite: account for clang's nested destructor calls on gdb.cp/mb-ctor.exp
91390 gdb/testsuite: enable running gdb.cp/classes.exp with clang
91436 …Executing on host: clang++ -fdiagnostics-color=never -Wno-unknown-warning-option -c -g -o /hom…
91437 …builtin_spawn -ignore SIGHUP clang++ -fdiagnostics-color=never -Wno-unknown-warning-option -c -g -…
91555 sim: v850: rename v850.dc to align with other ports
91570 sim: ppc: rename ppc-instructions to powerpc.igen
91571 To make it clear this is an input to the igen tool, rename it with an
91680 Commit 041de3d73aa changed the output format of all error messages when
91950 This commit also adds a testcase confirming that the message is only
92174 The error() function expects a trailing newline in its message.
92523 a log message for users at runtime instead of silent corruption.
92853 We still have to maintain custom install rules due to how we rename
93228 we're able to read the /bin/sh format before failing at a diff
93313 running gdb.base/macro-source-path when using clang.
93688 introduced two places where a register name was passed as the format
93693 …utils-gdb/opcodes/arm-dis.c:6005:3: error: format not a string literal and no format arguments [-W…
93697 This commit fixes these by using "%s" as the format string.
94032 distro. The gdb record error message is:
94077 gas/config/tc-i386.c:5039:16: error: too many arguments for format [-Werror=format-extra-args]
94153 gdb/testsuite: fix gdb.cp/converts.exp to run with clang
94164 gdb/testsuite: add XFAIL to gdb.cp/ptype-flags.exp when using clang
94341 message and a prompt.
94347 Fix this by consuming the "Remote connection closed" message and prompt.
94484 This commit improves internal error message
94492 Change error message slightly.
95449 both gcc and clang, so I've removed the SIM_WERROR_CFLAGS line from
95474 sim/ppc: fix for operator precedence warning from clang
95475 In the ppc simulator, clang was warning about some code like this:
95499 which silences the warning from clang, and is, I am guessing, what the
95718 When building GDB with clang and --enable-ubsan, I get:
95831 * ldmisc.c (vfinfo): Return early if the message is a warning and
96240 RUNTESTFLAGS="CC_FOR_TARGET=clang" on all of the above expect for
96241 Fedora 28. The (old) version of clang available on F28 did not
96245 made significant progress, I was ultimately stymied by this message
96431 sim/ppc: fix warnings related to printf format strings
96439 where commit 182421c9d2ee addressed issues with printf format
96443 This commit is mostly either changing the format string to match the
96817 clang.
97125 When building with clang 15 on Ubuntu 20.04, I get:
97147 This is because clang 15 warns for something like this:
97701 [gdb/testsuite] Fix gdb.base/infoline-reloc-main-from-zero.exp with clang
97702 With test-case gdb.base/infoline-reloc-main-from-zero.exp and clang I run into:
97704 gdb compile failed, clang-13.0: warning: -e main: 'linker' input unused \
97706 clang-13.0: warning: -Wl,-Ttext=0x00: 'linker' input unused \
97708 clang-13.0: warning: -Wl,-N: 'linker' input unused \
97744 out with the standard error message "nopie failed to prevent PIE executable".
98223 …Fix objcopy's error message when it cannot add a .gnu_debuglink section because the section alread…
98232 implementation-defined manner, the result with format string containing
98246 arguments being the wrong size, or type, for the printf format being
98253 later on thinks the print format should change, please feel free to do
98278 gdb: rename target_read_auxv(target_ops *) to target_read_auxv_raw
98452 "gdb_test_multiple $command $message {*}$opts $user_code"
98466 label provide a more helpful error message to the user.
98514 Clang generates a warning if the format string of a printf-like function is
98518 To avoid this warning, this commit now uses vsnprintf to format error
98519 message and pass the message to sim_engine_abort function with another
98551 Clang generates a warning if the format string of a printf-like function is
98556 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98563 Clang generates a warning if the format string of a printf-like function is
98568 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98578 Clang generates a warning if the format string of a printf-like function is
98583 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98590 Clang generates a warning if the format string of a printf-like function is
98595 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98602 Clang generates a warning if the format string of a printf-like function is
98607 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98614 Clang generates a warning if the format string of a printf-like function is
98619 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98626 Clang generates a warning if the format string of a printf-like function is
98631 __attribute__((format)) and we have ATTRIBUTE_PRINTF macro for this reason.
98718 label provide a more helpful error message to the user.
98774 because the gdb_test_multiple is called with an empty message argument.
98833 @@ -1301,6 +1301,7 @@ proc gdb_test_multiple { command message args } {
98835 set gdb_test_name "$message"
98941 [gdb/testsuite] Fix error message for cmd with trailing newline
98942 I noticed that the error message in gdb_test_multiple about trailing newline
98946 error "Invalid trailing newline in \"$message\" test"
99090 Regression tested on x86_64, using both gcc and clang.
99504 The format string is changed accordingly.
99541 "%x" format specifier requires unsigned type, not int. This commit
99547 the format specifier is "%x".
99867 but that warning is only checked for clang, resulting in:
99944 inheritance is linked to the typedef, such as how clang does it,
100078 sum-file A test summary file with the format of those
100092 sum-file A test summary file with the format of those
100102 found' message, followed by some other noise. This other noise is
100124 (3) For check-single, print the 'No matching tests found' message
100127 than the current 'Illegal Argument' error message.
100139 tests found' message is printed when appropriate.
100232 that will format '#' and all other text on the line, as a comment,
100683 opcode format, right?
100785 This commit changes the format of 'disassemble /r' to match GNU
100901 gdb/testsuite: new test for -data-disassemble opcodes format
100903 new check validates the format of the 'opcodes' field, specifically,
100971 C99's PRId64/PRIu64 format specifiers.
101178 [gdb/c++] Print destructor the same for gcc and clang
101191 and with clang++ (13.0.1):
101203 There's a difference in debug info between the two cases: in the clang case,
101229 - in the clang case, the loop is not entered and we print "void".
101237 such that we have the same for both gcc and clang:
101263 gdb: make target_auxv_parse static and rename
101467 egrep is deprecated and to use "grep -E". The nag message causes a ld
101823 * format.c (clear_warnmsg): New function.
102034 Every format that might appear inside a generic archive needs to call
102041 be set up too, since pdb claims to be of format bfd_archive.
102045 (pdb_archive_p): Set up tdata for bfd_archive format.
102242 format specifier "Xs5@20".
102335 Mechanically rename all_comp_units to all_units:
102442 unfortunate, as clang does not emit epilogue information, so using clang
102445 this from other tests and have them working with clang.
102455 exit some functions. This caused some problems when using clang to test
102526 fix gdb.base/jit-elf.exp when testing with clang
102527 When using clang as the compiler for the target, gdb.base/jit-elf.exp
102570 When trying to test gdb.base/msym-bp-shl.exp using clang, it would have
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
102578 when trying to step out of functions, since clang requires one fewer
102586 step 2 or step 3, so when we identify that clang is being used, those
102618 whereas clang links it to the last statement of the function. This
102768 gdbsupport: move fileio_errno_to_host to fileio.{h,cc} and rename
103097 that for all subsequent calls. (The object format has one set of
103172 * objcopy.c (copy_object): Do not issue a warning message when
103179 Bug 29580 - typo in warning message: .note.gnu.build-id data size is too bug
103232 I see this error when building with clang,
103235 gdb_bfd.c:1180:43: error: format string is not a string literal [-Werror,-Wformat-nonliteral]
103242 Tested on x86_64-linux with gcc 12 and clang 14.
103288 BFD error message suppression test case
103317 than one message. Of course, if BFD should output some
103318 other/different message, it should be output too, but all future
103330 identical message. A new GDB command, perhaps a 'maintenance'
103331 command, could be added to print out each message along with the
103333 its utility. Also, the BFD message printer has support for BFD-
103334 specific format specifiers. The BFD message strings that GDB stores
103356 Tested on x86_64-linux, with gcc 7.5.0 and clang 13.0.
103362 [gdb/tdep] Fix PowerPC IEEE 128-bit format arg passing
103592 Binutils: Readelf testcase failing with clang
103740 make clang tests fail like so:
103799 Add pdb archive format
103922 add xfails to gdb.base/complex-parts.exp when testing with clang
103923 clang doesn't add encoding to the name of complex variables, only says
103960 $ nm -A call-ar-st.clang | grep integer_
103971 fix gdb.base/access-mem-running.exp for clang testing
103975 update gdb.base/info-program.exp to not fail with clang
103977 stops, however it was still testing for a specific location. The clang
103980 patch the test works even with clang.
103984 gdb/testsuite: change gdb.base/nodebug.exp to not fail with clang
103992 clang:
104085 The error message we see is due to the destructor of thread being called while
104131 [gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp with clang
104132 When running test-case gdb.dwarf2/dw2-dir-file-name.exp with clang, we run
104148 to cause problem with clang, as documented in the comment for proc
104153 Tested on x86_64-linux, with both gcc 7.5.0 and clang 13.0.0.
104339 substitution must have a Makefile format but commit 171fba11ab27 used shell
104340 format "$srcdir/../bfd/development.sh".
104342 This commit fixes this issue by substituting "$srcdir" (shell format) to
104343 "$(srcdir)" (Makefile format). It preserves the dependency as Pedro
104629 In this commit, it adds following format:
104727 In this commit, it adds following format:
105385 names there is one for clang/icpx. Consider the following example
105399 'A' and 'C' makes clang emit a bunch of template tags without names:
105483 e.g. clang or gcc will make the disassemble command look like:
105485 >> clang --version
105486 clang version 10.0.0-4ubuntu1
105488 >> clang -O0 -g ./c.cpp
105519 Now, let's rename the C++ file and compile it as C:
105522 >> clang -O0 -g ./c.c
105580 internally rename members of such libraries. At that point, the
105645 clang in -std=c++17 mode (I did not test fully with clang in -std=c++11
106268 bytes at the start of a file. If they are not the ELF format
106269 magic values, then attempts to generate a helpful error message.
106404 gdb, testsuite: Adapt gdb.base/callfuncs.exp for new clang warning.
106430 This patch adds the same option that already exists for clang for icx and
106822 When working on windows-nat.c, it's useful to see an error message in
107324 Prefixed instruction format implementing SV. Funded by NLnet through EU
107537 a container format. This format has been added to elf based loongarch64 targets
107551 PASS: Check if efi app format is recognized
107554 tmpdir/loongarch64copy.o: file format pei-loongarch64
107564 [1] https://docs.microsoft.com/en-us/windows/win32/debug/pe-format
107640 converted to floating point format and stored in the register. Prior
107655 To fix this test I now print the float registers using the /f format
107806 ../../binutils-gdb/gdb/csky-linux-tdep.c:194:18: error: format ‘%ld’
107808 {aka ‘unsigned int’} [-Werror=format=]
108128 error message but that shouldn't matter in the least.
108170 warning message is fixed.
108440 Following the same format as the implementation in ld:
108612 BFD_VMA_FMT can't be used in format strings that need to be
108649 with printing to a buffer in order to properly format output.
108719 …Fix a conflict between the linker's need to rename some PE format input libraries and the BFD libr…
108742 When building with clang 15, I got this,
108759 Tested by rebuilding on x86_64-linux with clang 15 and gcc 12.
108815 First of all rename the meanwhile misleading Opcode_SIMD_FloatD, as it
109290 have observed some specific versions of gcc and clang generate. We want
109307 …$ make check TESTS="gdb.base/macro-source-path.exp" RUNTESTFLAGS="CC_FOR_TARGET=clang --target_boa…
109381 $ clang --version
109382 clang version 13.0.1
109383 $ clang test.c -gdwarf-5 -fdebug-macro
109533 $ clang --version
109534 clang version 13.0.1
109538 $ clang ./test.c -g3 -O0 -gdwarf-4
109570 $ clang ./test.c -g3 -O0 -gdwarf-5
109572 clang create two entries that refer to the same file but are of in a different
109594 producer clang version 13.0.1
109853 When aarch64_print_operand needs to format part of its output this can
109890 …Stop the linker from complaining about unrecognised DW_FORM-rnglistx and DW_FORM_loclistx format a…
110119 Renamed section at the bottom of commit message "Patch Description".
110167 Rewritten commit message, shortened + reworded,
110364 [gdb/testsuite] Fix gdb.opt/inline-small-func.exp with clang
110365 When running test-case gdb.opt/inline-small-func.exp with clang 12.0.1, I run
110370 clang-12.0: error: linker command failed with exit code 1 \
110482 gdb: rename gdbarch_tdep struct to fix g++ 4.8 build
110499 'struct gdbarch_tdep' to 'struct gdbarch_tdep_base'. This rename
110631 gprofng: fix bug 29392 - Unexpected line format in summary file
110653 gprofng: fix bug 29352 - Fix the message Hexadecimal number > 0xffffffff non-portable
110793 for mingw+clang. While adding that, I wrote some unit tests to make
110829 Attribute gcc_struct is not implemented in "clang -target
111156 gdb/testsuite: rename get_maint_bp_addr and move it to gdb-utils.exp
111864 …error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘bfd_vma…
112154 from the expected python code format.
112163 The format is documented in the Linux Kernel documentation [1].
112185 per mapped range. The format and documentation can be found in the Linux
112561 message to be printed to stderr indicating that gdb was not built with
112587 PowerPC: Add support for IEEE 128-bit format.
112595 made the default starting with GCC 12. The floating point format
112618 gdb.print_options. For the former, it lets Python code format values
112659 additional_flags-qtable=none and the clang optons
112941 As stated in the error message the default "-fcf-protection" and
113045 When building with clang 15, I got this error:
113053 Tested by rebuilding on x86_64-linux with clang 15.
113681 gdb_disassembler::dis_asm_fprintf (void *stream, const char *format, ...)
113751 member functions, and rename it to m_length.
113943 gas: rename md_end to md_finish
113946 and rename target implementation. The renaming of target functions
114629 (riscv_parse_check_conflicts): Change error message to include
115158 functions, and rename it to m_dwarf_version.
115193 Fix this instead by updating the regexp to allow the message.
115420 Match the whole error message expected to be given rather than omitting
115424 ensure the algorithm correctly builds the message expected here. Also
115514 fail "$message (GDB internal error)"
115996 Replace a run-time assertion failure with a warning message when parsing corrupt DWARF data.
115999 message.
116271 For clang compiled objects with dwarf-5, location list offset address dump
116974 RISC-V: Fix inconsistent error message (range)
116975 This commit fixes inconsistent error message format involving compressed
116976 funct<n> fields. In specific, funct6 had an error message with range
116982 * config/tc-riscv.c (riscv_ip): Fix inconsistent error message.
117243 (gdb) py print (gdb.Value (1230).format_string (format='t', nibbles=True))
117247 Note that the parameter nibbles is only useful if format='t' is also used.
117497 gprofng: fix build with -Werror=format-truncation
117501 * configure.ac: Remove -Wno-format-truncation.
117505 * common/hwctable.c: Fix -Werror=format-truncation errors.
117610 sim: fix BFD_VMA format arguments on 32-bit hosts [PR gdb/29184]
117611 Noticed format mismatch when attempted to build gdb on i686-linux-gnu
117615 error: format '%lx' expects argument of type 'long unsigned int',
117616 but argument 4 has type 'bfd_size_type' {aka 'long long unsigned int'} [-Werror=format=]
117624 While at it fixed format string for time-related types.
118005 The help message from 'gprofng collect app -h', in
118019 gprofng: fix build with -Werror=format-security
118027 * src/Print.cc: Fix -Werror=format-security errors.
118174 Fix the FAIL by accepting the error message.
119176 Notice the '.:' in the middle of this error message.
119182 The perror_with_name function take a string, and adds ': <message>' to
119302 The following commit changes the output format for the isel instruction on
119501 format.
119926 Older gcc without __int128 support, as well as clang use an unsigned type, but with
119927 a warning. Interestingly, clang uses "unsigned long long" while gcc uses
119946 Test more interesting values, both in decimal and hex format, as well as
120699 failures in the test when running the test with CC_FOR_TARGET='clang'
120700 CXX_FOR_TARGET='clang' F90_FOR_TARGET='flang'"
121091 gdb/testsuite: rename intel next gen c/cpp compilers
121119 clang/flang ..). This commit enables GDB to detect C and Fortran
121199 format. Therefore, this needs adjustment to make more tests pass in the
122052 The first issue observed is in the message printed when hitting the
122297 regression: Before, you could specify an explicit empty message to
122303 no-message-specified vs empty-message, so tests that previously would
122318 we would now end up with an empty message in gdb.sum, due to a
122319 gdb_test being passed both no message and empty command. E.g., this
122329 I fixed such cases by passing an explicit message. We may want to
122343 regression: Before, you could specify an explicit empty message to
122349 no-message-specified vs empty-message, so tests that previously would
122363 the old way of supressing PASS with an empty message, this has the
122364 advantage that you can specify a FAIL message that is distinct from
122447 [gdb/testsuite] Fix gdb.opt/clobbered-registers-O2.exp with clang
122448 When running test-case gdb.opt/clobbered-registers-O2.exp with clang 12.0.1, I
122470 Adding the clang-specific attribute optnone in start_sequence does, but since
122472 test-case, and it would work only for clang and not other compilers that
123394 (elf_static_list_options): Adjust help message conditions.
123454 we can see the following message in gdb/testsuite/gdb.sum:
123990 - gdb.python/py-xmethods.exp, a missing test message, resulting in
123991 the next gdb_test being interpreted as message, question and
124344 - clang 8.0.1, 12.0.1
124373 There are assumptions in the test about the long double format
124382 Lastly, not every long double format has invalid values. Some formats
124396 - Use long double values appropriate for the long double format.
125555 gdb/readline: fix extra 'quit' message problem
125570 accepted (by pressing return) an unexpected 'quit' message will be
126336 Dwarf: rename yet another instance of "index"
126644 the FAIL listed at the top of this message is resolved.
126679 get an error message from gdbserver (which matches the pattern), and
126715 Tested on x86_64-linux, with gcc 7.5.0, gcc 12.1 and clang 12.0.1.
126743 - GDB build with clang + glibc < 2.33.
126750 clang shows this error:
126752 make[2]: Entering directory '/home/smarchi/build/binutils-gdb-clang/gdbsupport'
127866 I noticed that these files failed to format with Black, because they use
127877 The format for printing the floating point values was changed by commit:
127897 the hexadecimal format for both big endian and little endian systems. The
127911 This fixes build breakage using clang with libc++ on FreeBSD where
128207 new function we can now print the 'quit' message, this replaces the
128685 Note the message mentions the 'p' packet. This is a regression since
128764 gdb/testsuite: add binary testcases to py-format-string.exp
128767 binary format.
128778 Also, by using "confirm off", the message GDB prints if Debuginfod
128820 * testsuite/ld-cris/warn3.d: Modify "is not implemented" message
129347 …$ make check TESTS="gdb.base/jit-elf.exp" RUNTESTFLAGS="CC_FOR_TARGET=clang LDFLAGS_FOR_TARGET=-fu…
129349 …gdb compile failed, clang-13: warning: -Xlinker -Ttext-segment=0x7000000: 'linker' input unused [-…
129353 …$ make check TESTS="gdb.base/jit-elf.exp" RUNTESTFLAGS="CC_FOR_TARGET=clang LDFLAGS_FOR_TARGET=-fu…
129881 Building with clang++-14, I see:
129936 rename the typedef to task_t to fix them.
129968 Fix this by detecting the "No MPX support" message in have_mpx.
130008 Fix this error when building with clang++-14:
130011 …/home/smarchi/src/binutils-gdb/gdb/complaints.c:130:65: error: format string is not a string liter…
130019 gdb: fix clang build failure in msymbol_is_mips
130020 Building with clang++-14, I see:
130044 * config.bfd (x86-haiku): Add i386_pei_vec as a selectable format.
130841 gdb/fortran: rename f77_keywords to f_keywords
131588 Right now it only handles clang specially (using -fdebug-macro) and
131593 gcc nor clang. After this patch, the tests will attempt to run (the -g3
131617 The problem is that the libthread_db message occurs at a location where it's
131881 contain the message 'Register Values Unavailable', and at the console
131882 you'll see the message "unknown register group 'next'".
131884 The same happens with 'tui reg prev' (but the error message is
131888 prev' and you'll keep getting the error message.
132070 After this change GDB prints the error message, the backtrace, and
132134 its return type can only ever be one object format's type (and this
132608 I see there are lots of other cases of undocumented number format for error
132728 (After writing the commit message, I realized this also fixes a similar
133057 hipcc (i.e. clang). The problem is as follows: There's a function
133117 clang/clang++ (version 10.0.0) since at the time of writing GCC does not
133400 gdb: rename start_symtab/end_symtab to start_compunit_symtab/end_compunit_symtab
134458 gdb/tui: rename tui_layout_split:set_weights_from_heights
134479 gdb/tui: rename tui_layout_base::adjust_size to ::set_height
134572 gdb: rename floatformats_ia64_quad to floatformats_ieee_quad
134573 It is better to rename floatformats_ia64_quad to floatformats_ieee_quad
135436 happens is now up to the stream. So, rename it. (This function is
135443 happens is up to the stream. So, rename it.
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:
136820 This method takes an address, and returns a string with the format:
136847 In order to format an address for a different inferior.
137581 error message to "name is already in use" rather than "may already be
137671 gdb: run black to format some Python files
138061 GDB prints the 'quit' message from command_line_handler (in
138072 The solution to this problem is to print the 'quit' message earlier,
138183 at the closing bracket for main. The message printed is:
138190 message printed it:
138370 gprofng: Don't hardcode -Wno-format-truncation/-Wno-switch
138371 Use -Wno-format-truncation and -Wno-switch only if they are supported.
138375 AC_SUBST for -Wno-format-truncation.
138379 * src/Makefile.am (AM_CFLAGS): Replace -Wno-format-truncation
138452 of those notes. msgpack is a structured format, a bit like JSON, except
138517 the msgpack format.
138631 The ELF format for this architecture is documented here:
138866 gdb/testsuite: rename a proc and fix a typo
139354 gdb/auto-load: Remove repeating "auto-load" from debug message
139355 Remove "auto-load:" from a format string passed to auto_load_debug_printf.
140193 bal.o: file format elf32-tradlittlemips
140742 message for the "During startup..." error message when running with gdbserver.
140890 Clarify the wording of the error message when an obsolete configuration is encountered.
140892 * config.bfd: Update error message for obsolete configurations.
141233 MACH_NOTIFY_DEAD_NAME message can be received, and which was not
141239 - Read and ignore such messages (counting on the next exception message
141401 This patch expands that error message to include the missing extension
141402 information. For example, now the error message would be "unrecognized
141404 If the opcode is not a part of any extension, the error message reverts
141427 This patch expands that error message to include the missing extension
141428 information. For example, now the error message would be "invalid CSR
141582 fbsd-nat: Various cleanups to the ::resume entry debug message.
141583 Move the message from 'show debug fbsd-lwp' to 'show debug fbsd-nat'
141587 Use target_pid_to_str to format the ptid and log the step and signo
141857 format, with only limited support in GDB.
141924 …8b3 in fputs_maybe_filtered (linebuffer=0x60c0000f4000 " [...quite big message...]", stream=0x60…
141925 …4708e57 in fputs_unfiltered (linebuffer=0x60c0000f4000 " [...quite big message...]", stream=0x60…
141976 failure with clang that Simon pointed out.
142208 prints an appropriate message to the user and does not proceed with the
142562 * microblaze-opc.h: Follow 'fsqrt' rename.
142909 the error message as shown below.
142932 would just behave as "next". This was noticeable in clang-compiled
142934 to this problem, as running gdb.base/watchpoint.exp with clang
143020 allow for the new output format.
143176 I have no info on the format of a "SUNPRO C++ Namespace" stab, so am
143247 in gdb.python/py-format-string.exp in an environment where styling
143968 gdb: rename compunit_primary_filetab to compunit_symtab::primary_filetab
144578 "Couldn't get registers: No such process." message twice. The second
144602 #19 0x0000555555fa5e47 in get_selected_frame (message=0x0) at /gdb-up/gdb/frame.c:1810
144759 here, see the commit message for the previous commit.
144986 the error message isn't as clear as it could be. See
144989 Improve the error message in a few cases.
145057 gdb: fix some clang-tidy readability-misleading-indentation warnings
145059 thought I'd run clang-tidy with this diagnostic on all the files (that I
145320 gdb/build: Fix Wpessimizing-move in clang build
145321 When building with clang, I run into an error:
145338 Build on x86_64-linux with clang 13.0.0.
145722 gdb, btrace: rename record_btrace_enable_warn()
145781 without styling, but would also avoid the annoying exception message.
146092 # Please enter the commit message for your changes. Lines starting
146094 # An empty message aborts the commit.
146268 Always print the "host libthread-db" message to stdout
146270 prints a message, but decides whether to print to gdb_stdout or
146496 bfd: rename core.texi to corefile.texi
146953 bfd/elf64-ppc.c: fix clang -Wbitwise-instead-of-logical warning in ppc64_elf_check_init_fini
146954 I see this error with clang-14:
147077 gdb/infrun: rename variable and move to more specific scope
147078 Move the "started" variable to the scope it's needed, and rename it to
147419 + * testsuite/d-demangle-expected: Add missing format for new test
147468 # Please enter the commit message for your changes. Lines starting
147483 Because clang can provide helpful warnings with this flag.
147523 strict, is gcc check. As such, GCC is set to 'yes' for clang, which
147524 would mean the flag was not included for clang or gcc. The entire
147525 point of the original commit was to add this flag for clang, so
147530 GDB_COMPILER_TYPE to either 'gcc', 'clang', or 'unknown'. In future
147537 I've tested this with both gcc and clang and see the expected results,
147539 clang continues to use it.
148137 gdb: rename lin-lwp to linux-nat in set/show debug
148156 GNU linker for XCOFF format.
148186 ELF format.
148190 * testsuite/ld-elfvsb: rename as ld-vsb.
148191 * testsuite/ld-elfvsb/hidden0.d: move to ld-vsb and rename with
148263 objdump, readelf: Emit "CU:" format only when wide output is requested
148271 changing options to get the wide format, so as to keep the name of the
148273 options for the gas test as I believe the "CU:" format is preferable.
148280 format only if wide output is requested.
148543 offset table) and data sections in a compact format:
149106 duplicate message.
149226 * config/tc-riscv.c: Add 1.12 to the usage message.
149228 * configure.ac: Add 1.12 to the help/usage message.
149385 Fix a stack exhaustion bug parsing malicious STABS format debug information.
149409 "Detaching from program" message printing"). There, Pedro wrote:
149418 some targets will print a different message when exec_file==NULL,
150047 ld: Improve thin archive member error message
150048 Improve thin archive member error message with:
150101 of the message. The 'on connection 1 [...]' part is unexpected.
150104 part of the message.
150150 Remove a spurious debugging message.
151366 debug message is the only mechanism to see the thread being added.
151368 announce when the thread object is deleted, I've added a debug message
151371 Additionally, having message printed through the debug system will
151827 Documentation on the format will come in a subsequent patch.
151997 …dwarf.c:11300:3: error: format not a string literal and no format arguments [-Werror=format-securi…
152232 gdb: re-format with black 21.12b0
152242 gdb: re-format with black 21.9b0
152292 If you have X threads, that message will be repeated X times.
152421 Note that _FORTIFY_SOURCE changes the message a bit, but I get a similar
152445 bfd: fix -Wunused errors with clang 13+
152455 gcc won't warn, but clang will.
152473 gdb/mi: rename build_table to add_builtin_mi_commands
152479 gdb/mi: rename mi_cmd to mi_command
152529 gdb/mi: rename mi_lookup to mi_cmd_lookup
152857 was this message:
153085 Fix this, seen when building with clang 14:
153097 Fix these, seen when building with clang 14:
153119 print anything. "no-message" is prependend to "args", so if "message"
153125 ("gdb/testsuite: make runto_main not pass no-message to runto"), tests
153154 Remove the line that prepends no-message to args, that should make
153293 Update the gdb.threads/pending-fork-event.exp test (and rename it to
153641 helpful message out, but GDB doesn't print this message.
153643 The reason this message goes missing is the call stack, it looks like
153663 the screen; in the above case the helpful message will now be shown.
153679 If the disassembler returns -1 without printing a helpful message then
153691 Notice however, that the error message is always printed on a new line
153802 gdb: rename "maint agent" functions
153804 maintenance commands, rename them accordingly (with the maint_ prefix),
154085 errors and "FAIL: Check if efi app format is recognized". I also
154152 Tested on x86_64-linux, with both gcc and clang.
154157 When running test-case gdb.arch/i386-avx.exp with clang I ran into:
154183 Tested on x86_64-linux, with both gcc and clang.
154383 readability improvements") change the output format of "maint info
154550 target_waitstatus by value. Do that, and rename to
154766 gdb/testsuite: update tests looking for "DWARF 2" debug format
154768 debugformat field") changes the debug format string in "info source" to
155186 instruction. This patch adds a line number to the message,
155201 message.
155303 both gcc and clang.
155425 Compiled with DWARF 2 debugging format.
155437 Compiled with DWARF 5 debugging format.
155587 Fix that by having a single with_test_prefix around that message and
155784 gdb/python: don't use the 'p' format for parsing args
155788 this method uses 'p' as an argument format specifier in a call to
156066 https://github.com/riscv/riscv-v-spec/blob/master/vtype-format.adoc
156200 are signed in C++"). The message says:
156266 "/usr/src/debug/llvm13-13.0.0-1.2.x86_64/tools/clang/lib/AST/Decl.cpp"
156377 a single input & output format. ld is a bit better, but requires
156636 sim: testsuite: rename global_sim_options to SIMFLAGS_FOR_TARGET
156638 the dejagnu settings of XXX_FOR_TARGET, rename global_sim_options to
156973 gdb: rename source_styling_changed observer
156981 seems unnecessary right now, so, in this commit, I plan to rename
157132 output of the command. After the commit, the message is unified and it's no
157253 a container format. This format has been added to elf based aarch64 targets
157289 [1] https://docs.microsoft.com/en-us/windows/win32/debug/pe-format
157466 gdb: rename target_waitstatus_to_string to target_waitstatus::to_string
157979 message before issuing the "info breakpoint command".
158257 When a "Don't know how to run message" is received, the test is
158321 gdb: rename rs6000-nat.c to rs6000-aix-nat.c
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:"
158924 assertion with a warning message.
159051 …sprintf_chk' may write a terminating nul past the end of the destination [-Werror=format-overflow=]
159631 To allow it, rename all gdbarch_tdep types to <arch>_gdbarch_tdep, and
159703 sim: cris: make error message test a little more flexible
159712 get a chance to output an error message about incorrect usage.
160041 [gdb/build] Fix Wimplicit-exception-spec-mismatch in clang build
160042 When building with clang 13 (and -std=gnu++17 to work around an issue in
160061 Build on x86_64-linux, using gcc 7.5.0 and clang 13.0.0.
160125 temp.o: file format elf32-littleriscv
160147 temp.o: file format elf32-littleriscv
160494 In the output shown above, only the first dprintf message is printed.
161030 gdb: remove bpstat typedef, rename bpstats to bpstat
161037 So, remove the bpstat typedef and rename struct bpstats to bpstat (since
161044 libctf: add CTF format specification
161047 complete insofar as it goes: it documents format v3 (the current
162138 sim: ppc: clean up printf format handling
162140 printf format specifier whether it be a 64-bit type or a pointer.
162155 printf format specifier whether it be a 64-bit type or a pointer.
162679 * elfcode.h (elf_swap_shdr_in): Don't repeat error message.
162804 (reg_expected_msgs): Add message for pseudo reg type.
162871 [gdb/testsuite] Fix assembly comments in gdb.dwarf2/clang-debug-names.exp.tcl
162874 clang-debug-names-debug.S:72: \
162885 $ sed -i 's% #\([^"]*\)%/*\1 */%' clang-debug-names.exp.tcl
162949 clang compiler:
162961 initialized (or used), then clang emits the symbol "p_union" which
163054 available, and it handles either this message:
163251 static buffer, so my message would show twice the same ptid. Change
164000 message:
164588 [gdb/exp] Improve <error reading variable> message
164609 Improve the error message by printing the details of the error, such that we
165045 and consequently, add a missing UNTESTED message.
165332 fail "$message (GDB internal error)"
165606 * format.c (bfd_reinit): Clear build_id.
165627 due to a message related to libthread_db:
165711 message and return.
165994 Following 2 test points are failing with clang compiler
166006 Tested on x86_64-linux with gcc and clang.
166696 …:44: error: format '%lx' expects argument of type 'long unsigned int', but argument 4 has type 'ui…
166921 gdb/testsuite: make runto_main not pass no-message to runto
166926 ... make runto_main not pass no-message to runto. This means that if we
166936 default (without an explicit no-message argument), runto prints a
166938 gdb.python/py-pp-registration.exp, remove "message" passed to runto.
167373 After googling the error message with context valgrind gdbserver, I found
167385 will report an error message when using the "target" command. Debugging will
167545 DWARF revision 5 changes .debug_line format quite extensively, and in
167645 I made a mistake in the previous patch. Adjust the format string to
167656 …/Users/smarchi/src/binutils-gdb/gdb/darwin-nat.c:1175:19: error: format specifies type 'unsigned l…
167720 Invalid format: [z|h|s|zvm|x][0-9a-z]+[0-9]+p
168153 gdb.base/foll-fork.exp: rename variables
168240 format string.
168251 format never read by any extant libctf. We can detect such CTF dicts by
168267 message at the same time).
168273 function index symtypetab sections if this is an old-format
168357 Libtool needs to get BSD-format (or MS-format) output out of the system
168365 has only been worked around by assuming that the error message has a
168368 BSD-format output, even though the test never actually got anything
168369 but an error message out of nm -B. This is fixable by nm'ing *nm
168375 also flags forcing BSD-format output. Worse yet, one such "user" is
168377 nor specifies any BSD-format flags. So platforms needing BSD-format
168707 happen then we now give a more informative error message.
168854 the field private (rename to m_name) and add some accessors.
169872 binary format. Before the patch, the disassembler output is invalid
169971 info section which now share the same format of their contents - an array
170309 gas/config/tc-riscv.c to here, and rename it to riscv_supported_std_ext.
170416 but with clang, I run into:
170460 Tested on x86_64-linux with gcc and clang-7 and clang-12.
171045 The documentation of mi_gdb_test states that the command, pattern and message
171056 - if there are 1 or 2 arguments, use the command as the message.
171061 message. Fix a few other trivial-looking FAILs.
171148 etc: rename configure.in to configure.ac
171231 Then I ran with clang and found another FAIL, fix by updating the regexp.
171233 Tested on x86_64-linux with gcc-4.8.5, gcc-7.5.0, gcc-11.2.1, clang-7.0.1 and
171234 clang-12.0.1.
171534 sim: ppc: align format string settings with common code
171536 build errors for mingw targets. Turning format warnings on triggers
171847 gdb: rename gdb/testsuite/gdb.arch/riscv64-unwind-prologue-with-ld-lw.c
172143 Compiler support for gcc and clang is in progress, see e.g.:
172708 Unrecognized format specifier 'j' in printf
172718 also reported by John Baldwin, using a clang that uses libc++.
173228 debug message during conversion to the new debug output scheme. These
173326 [gdb] Fix 'not in executable format' error message
173330 "0x7ffc87bfc8d0s": not in executable format: \
173331 file format not recognized
173531 Move this function to solib.c and rename it to gdb_bfd_scan_elf_dyntag.
173600 sim: rename ChangeLog files to ChangeLog-2021
173948 message.
174030 * testsuite/gas/csky/v2_float_part2.d: Following the new format.
174297 therefore marked obsolete, per the instructions in the last message.
174406 but in many shells, the user will see a more specific message once GDB
174449 gdb: rename async_init_signals to gdb_init_signals
174677 hex_float() (taking the opportunity to adjust error message wording).
174683 AMX-BF16 insns. While not part of the IEEE standard, the format is
174711 format (dec vs hex).
174737 (where output sizes currently differ depending on input format).
174949 rather than just displaying a message that might be ignored.
174954 (rl78_compute_complex_reloc): Add status and error message params.
174957 (rl78_special_reloc): Return status and error message from
175328 message.
175359 Print it using the same format used for TARGET_WAITKIND_STOPPED and
175381 The ptid_t::to_string method was introduced recently, to format a ptid_t
176442 gdb/testsuite: fix gdb.base/info-macros.exp with clang
176449 The current state is problematic when testing with CC_FOR_TARGET=clang,
176454 compiler is clang.
176499 complaint by inverting the condition and using a clang-compiled binary,
176540 * s390-opc.c (INSTR_SIY_RD): New instruction format.
176542 * s390-opc.txt: Change instruction format of lpswey to SIY_RD.
176693 PR28156, rename.c doesn't compile with MinGW
176697 * rename.c (get_stat_atime, get_stat_mtime): Don't compile
176850 [gdb/testsuite] templates.exp to accept clang++ output
176866 Please note that error message contains '&' for cstring, which is absent
177485 If the test fails, the added check prints an message to the log file if
178396 an error message is returned:
178530 gdb: rename cfunc to simple_func
178931 and with clang-10, I have instead:
178946 tree_check (lines 40-43) (so, with the clang trace we get that right).
178960 Tested on x86_64-linux, with gcc-8, gcc-9, gcc-10, gcc-11, clang-8, clang-10
178961 and clang-12.
179114 * testsuite/gas/i386/ifunc-2.l: Adjust to suit changed error message.
179260 the error message.
181011 Tested on x86_64-linux, with both gcc 7.5.0 and clang 12.0.1.
181496 line of the error message starts with the same prefix as the first:
181674 * testsuite/gas/all/overflow.l Change expected output format.
182251 clang" I see: