Lines Matching +refs:po +refs:active +refs:comment +refs:regexp
738 opcodes: i386-reg.tbl: Add a comment to reflect dependency on ordering
741 of these register entries in the table. Add a comment to make it clear.
744 * i386-reg.tbl: Add a comment.
1120 The cause of this is that the question argument regexp is incomplete.
1122 Fix this by making sure that the entire question is matched in the regexp:
1622 The procedure added the regexp ' +' after each completion, and then
1625 generated regexp would be: 'f1 +f2 + +'. This would match just fine,
2419 While there also extend the respective comment in the opcode table, to
2435 PPC64/ELF: adjust comment wrt ABI versions
3488 for specific comment contents here.
3553 The comment in s_bss() looks bogus (perhaps simply stale, or wrongly
3574 The comment looks bogus (perhaps simply stale, or wrongly copied from
3585 The comment looks bogus (perhaps simply stale), and there are also no
3612 The comment looks bogus (perhaps simply stale), and there are also no
3637 The comment looks bogus (perhaps simply stale, perhaps wrongly copied
3650 The comment looks bogus (perhaps simply stale), and there are also no
3800 4) Check out */po/*.pot which we don't update frequently.
4590 '/' starts a comment for some targets. Use .byte instead of .insn with
5644 As explained in the comment removed by the previous commit "gdb: pass
5958 This patch reverts the earlier change and then updates the comment to
6449 As the comment says, it's GDB's responsability to know whether the
6727 gdb: remove stale comment and ctor in gdbarch_info
6729 gdbarch when SVE vector length changes"). Remove the stale comment and
6760 Print instruction description as comment in disassembly with s390
6794 and optionally print the instruction description as comment in
6926 gdb: remove stale comment in value_assign
6927 This comment is no longer relevant, put_frame_register_bytes now accepts
7215 output configuration, only one regexp will match. With this change in
8776 [gdb/testsuite] Fix $eol regexp usage in some test-cases
8950 (Mips_relocate_functions::mips_reloc_unshuffle): Update comment.
9069 The focused window is highlighted by using active-border-kind instead of
9079 Likewise if highlighting is switched off by setting active-border-kind to the
9157 line regexp ... except that $eol was set to '[\r\n]*', which isn't
9159 line regexp.
10211 Remove incorrect "fall-through" comment
10212 I found a "fall-through" comment in gdb/remote.c that was incorrect --
10217 Update fall-through comment in gdbserver
10218 I noticed that gdbserver/win32-low.cc has a fall-through comment that
10431 those cases when there's an active checkpoint.
11024 This patch also adds a couple of tests to make sure all the comment
11057 gdbsupport/new-op.cc has a comment about relying on the C++-17 <new>
11065 index-write.c has a comment indicating that C++17's try_emplace could
11239 gdb/testsuite: improve test regexp in gdb_get_worker_threads
11273 gas: add NEWS entry for change of comment syntax in BPF assembler
11276 * NEWS: Add entry about change of comment syntax in the BPF
11333 * config/tc-bpf.c: Semicolon does not start a comment, but
13463 that the comment before this function was incorrect.
13500 compiler generated this stab is unknown. I left a comment in
13581 According to the function comment though, it should return -1 on error:
14440 the also eliminates a stale comment talking about a warning when an
14441 error is raised. While there, correct a similarly stale comment in
14755 * testsuite/gas/mips/call-nonpic-1.d: Adjust regexp to allow for mips-irix targets.
14934 [gdb/testsuite] Fix gdb.threads/stepi-over-clone.exp regexp
16435 Also tweak a comment in infrun.c:follow_exec referring to how
16504 The comment right above:
16688 Move new features above the 'Changes in 2.41' comment
17255 (cache_bclose): Add comment.
17266 * po/bfd.pot: Regenerate.
17281 * po/bfd.pot: Regenerate.
17295 * po/bfd.pot: Regenerate.
17992 * testsuite/ld-x86-64/property-3.r: Update regexp to allow for targets which support x86-64-v3.
18331 comment.
18429 gas: tc-bpf.c: fix formatting of comment
18431 opcodes: bpf-dis.c: fix typo in comment
18996 While there also add PROCESSOR_IAMCU to the respective comment.
19051 I noticed the regenerated BFD_RELOC_MICROBLAZE_32_NONE comment didn't
19055 comment:
19065 You'll notice how the second and third line of the original comment
19067 comment needs to be indented to match the code.
19449 - Introduce rocm_so, which is a name a unique_name (see comment in
20083 addr field cannot be used to determine if the buffer is active or not.
20089 to signal that a particular displaced-step buffer is active or not. If it is
20091 it is an active buffer in use by a particular thread.
20098 whether we're actively displaced-stepping (so we have an active buffer) or
20820 gdb_unique_ptr.h: Fix a typo in a comment
21084 - Updated comment on args_test,
21791 * testsuite/ld-elf/pr28158.rd: Adjust regexp to allow for section indicies larger than 9.
21963 This started with me running into this comment in symfile.c:
21969 In this particular case I think I disagree with the comment; I think
21976 comment, but that would mean loosing the filename styling in the
21977 output... so in the end I remove the comment and updated the code to
22583 if the register cache contains active (non-zero) SVE data.
24772 I noticed a comment by an include and remembered that I think these
25108 I stumbled across an ancient FIXME comment that was easy to fix --
25110 valprint.h, where (despite what the comment says) it belongs.
25705 - avoid using . in regexp to match $, {} and <>.
26882 This patch fixes the regexp in gdb.base/hook-stop.exp to allow such
27220 The test fails because this regexp is used:
27225 The regexp attempts to detect that the exec is somewhere in pause ():
27243 We could simply extend the regexp to also match __kernel_vsyscall, but the
27834 - adding a comment explaining why zero-initialization is not necessary.
27880 copy_fields, and there's already a comment for the third.
29098 comment ahead of the sole use site of CALC_ADDEND() may need to account
29143 Use the pattern rule in a comment from commit 77ac17b8453f.
29175 call to rela_dyn_section creates it, and as this comment in
29802 argument list and uses this to build the expected result regexp. This
30109 (insert_operand): Delete bogus comment and cast.
30152 presume the code is correct, but I've left the dead code and comment
30167 Indentation, whitespace and comment fixes.
30171 (elfNN_kvx_final_link_relocate): Correct GOT entry comment.
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.
30907 Commit f00b50d057 went the wrong way. As the comment says this
31155 per PR27981 comment 3:
31552 Mention process_stratum in inferior::priv comment
31994 Tidy comment formatting.
32153 noted in a comment in next-fork-exec-other-thread.exp, I had to remove
33026 spec_offset DIE (though that's not clear from the comment describing it).
33444 RISC-V: move comment describing rules for riscv_opcodes[]
33445 It makes little sense to have this comment meanwhile over a hundred
33446 lines ahead of the array. In fact until spotting the comment, I was
34433 The comment seems to be copied from debug_names::insert, which does indeed use
35551 bpf: remove spurious comment from tc-bpf.c
35620 has a confusing name and corresponding comment, because it doesn't contain the
36343 Fix typo in riscv-dis.c comment
36359 comment coming up again in the future, change make-target-delegates.py
36379 I've also added a comment to explain the fact that arguments to
36607 bpf: accept # as an inline comment char
36609 comment character, which clang -S seems to use.
36786 /* See comment in class declaration above. */
36847 The FAIL is due to a mismatch with regexp:
36853 Fix this by using instead the regexp:
37835 comment.
38195 The comment suggests these are to allow for output from a vforked
38317 handle_vfork_child_exec_or_exit for details). Further the comment
38458 Now, if we check the comment embedded within the condition it says:
38486 check, this makes it easier to write a longer comment explaining
38561 handle_vfork_child_exec_or_exit for details). Further the comment
38915 Remove obsolete comment from gdbthread.h
38916 A comment in gdbthread.h refers to a global that no longer exists.
38942 py-inferior.exp. One is an obviously incorrect comment, and the
38975 not an active inferior to query via ptrace. Instead, use the default
38991 not an active inferior to query via ptrace. Instead, use the default
39152 enum -- but the comment here refers to an enum that no longer exists.
39306 * coff-rs6000.c (add_range): Revise comment, noting possible fail.
40030 comment on type::length() we see this:
40349 Masking is not permitted in this case. See the code comment for how this
40358 Zeroing-masking is not permitted in this case. See the code comment for
41929 * sframe.h (SFRAME_FDE_TYPE_PCMASK): Update comment.
42174 archive names with a similar FIXME comment we already have in
42481 Add comment for intention to deprecate.
42768 removing the active gdb.log, so I reverted the commit.
42772 If the standard_output_file directory contains an active gdb.log, check that
42777 If the standard_output_file directory doesn't contain an active gdb.log, clean
42835 there was a FIXME comment to this effect. This patch fixes the
42965 The problem is that the regexp doesn't account for the ^C:
42974 For now, fix this by updating the regexp, and likewise in another place in the
43043 # a regexp matching the line to wait for. Return 0 on timeout, 1
43048 Note that besides the regexp, also a subsequent gdb prompt is matched.
43844 This exposes a problem in Term::command. The "prompt before command" regexp
43855 Futhermore, the "prompt after command" regexp in Term::wait_for has no
44254 Fix regexp in py-rbreak.exp").
44256 The fix I applied there was to use a regexp "^[^_]" to filter out
44260 - reverting the regexp to "", and
44271 [gdb/testsuite] Fix breakpoint regexp in gdb.ada/out_of_line_in_inlined.exp
44851 There was a comment in the code assuming that if the file was found on
44860 this comment.
44968 I noticed that the help texts for tui border-mode and tui active-border-mode
45215 Fix comment in address_class
45216 enum address_class has a stale comment referring to
45218 the comment.
46607 mi_interp::init avoided using mi_inferior_added, since, as the comment
46949 ARMMAGIC which has this comment: "I just made this up". Well, OK, I
46981 This file is unused and as the header comment says, obsolete.
48236 annotates a tuiterm line with the active attributes.
48347 documentation, and also fixes a somewhat related typo in a comment
49587 cause the command regexp to automatically be included in the expected
49606 In both cases the '^' will case gdb.exp to inject a regexp that
50107 evaluation of this expression requires the target program to be active
51166 with a FUNCTION comment.
51176 it the usual FUNCTION etc. comment so prototypes and docs are handled
51180 * opncls.c: ..here, add FUNCTION comment.
51224 _bfd_mips_elf_lo16_reloc vallo comment
51226 replacing the rather nebulous existing comment. I've also changed the
51232 comment. Hoist calculation out of loop.
51902 evaluation of this expression requires the target program to be active
52041 then also make more obvious that the comment there applies to both forms
52068 the comment added to _bfd_xcoff_openr_next_archived_file. While
52246 the command and include some regexp character, then I have to write:
52256 after the '^' is the command converted into a regexp, so lets do that
52262 inject the regexp version of the command after the '^', followed by a
52280 In this case my proposed new feature injects the command regexp, which
52282 injects the '\r\n' after the command regexp, thus we end up with this
52364 this commit I have extended the comment on gdb_test_no_output to
52795 against local_sym_name with a comment to that effect.
53866 the add_range function comment. I needed a place to stash the list,
54023 gas: sframe: fix comment
56234 under bfd/po/, i.e. in maintainer mode.
57080 array rather that using malloc. Clarify comment about
57109 syscall is active. But some active syscalls keep PC pointing to the SVC
57244 language_demangle is only called in two places, and has a comment
57448 Note that on targets where / starts a comment, --divide needs passing to
57470 similar comment and a similar check, relocations against STN_UNDEF have
58540 comment to say that we call unpack_pointer. I've also adjusted the
58541 header comment on value_as_address. The existing header refers to
58546 I've just trimmed the comment on value_as_address to be a brief
58782 comment. Always set sh_link to .dynsym for alloc reloc
59085 Fix test-case gdb.guile/scm-symbol.exp for remote host by making a regexp less
59563 Also fix the comment in gdb/linux-nat.h describing
59948 documents this in the fix_tag comment, makes is_sym a bitfield, and
59953 Sort and comment on union selectors.
59977 Add an option to the gold linker to put its version string into the .comment section.
59980 …::create_gold_note): If linker-version is enabled put the version string into the .comment section.
60147 libctf: fix a comment typo
60150 that couldn't actually happen. Update the comment to note what it
60155 * ctf-dedup.c (intern): Update comment.
60344 There is another crash scenario after we kill a previously active inferior, in
60352 At some points, like the one from the backtrace above, there is no active
60612 The comment on the gdbarch_displaced_step_fixup gdbarch method
60955 I noticed a weird comment in one of the .y files, and then ended up
61463 Regen ld/po/BLD-POTFILES.in
61880 [gdb/testsuite] Fix regexp in gdb.arch/ftrace-insn-reloc.exp
61900 Fix this by making the regexp less strict.
62170 in the .comment section.
62364 HAS_CONTENTS by default. This is wrong for .comment. Fix that by
62366 noalloc section types. That also allows the address of .comment to be
62373 * scripttempl/misc-sections.sc: Set .comment address to zero
62571 Add --enable-linker-version option to bfd linker to add an entry in the .comment section.
62573 …gs): Handle the new options. * scripttempl/arclinux.sc: Remove stabs and comment sections and repl…
62973 skipped due to the invalid field being False. This comment is inline
62974 with plenty of other getters that also have a similar comment. Plenty
62976 a comment noting that the validation has been skipped for a specific
62996 favour of a comment like:
63850 The problem is that the new thread message doesn't match the regexp, which
63927 Fix this by making the regexp less strict.
64291 missing LDFLAGS preservation, fix our builds and match the comment.
64539 std::underlying_type for that. It turns out that the comment just above
64767 exception_catchpoint::resources_needed has a FIXME comment that I
65096 I noticed a very stale comment in valarith.c. This patch fixes a few
65431 due to the regexp matching "Hardware watchpoint" but not "Watchpoint":
65436 Fix this by making the regexp less restrictive.
65543 There is a comment explaining why this is the case in the code; it's
65830 their expected output, but given there was no comment pointing out
65857 gdb: remove an out of date comment about disp_del_at_next_stop
65858 Delete an out of date comment about disp_del_at_next_stop, the comment
65864 I'm sure this was true when the comment was added, but today the
65869 And then this comment is located on one random place where
65872 Lets just delete the comment.
67493 gdb: fix parenthesis position in comment
67500 trigger failures in the regexp from dump tests, especially for those
68222 Hoist the SECTION comment in opncls.c
68233 That is, there's a stray C comment and declaration before any other
68237 before the SECTION comment. Hoisting it makes this a little nicer.
68241 * opncls.c: Hoist the SECTION comment.
68301 The regexp in "noinit sections (ld -r)" is skipping the file path before
68303 the regexp to allow such cases.
68416 while making sure that only one of the two is active. Likewise for i386. NFC.
68470 Also add a comment in the new function about the assumption that in absence of
68489 Fix this by recognizing above warning in the xfail regexp.
68728 This is kind of tricky and ugly, so I've tried to comment it
69031 progress.h. progress.h is unchanged apart from the copyright comment
69434 That comment quoted above says that gcc -Wall will reveal any types
69663 In a few cases I had to slightly reword the comment. There were also
69706 (bfd_symbol_info): Reorder documentation comment.
70026 Silence these warnings by casting to void. Add a comment to explain
70805 updates the test regexp to handle this optional 'ERROR: ' string.
71412 unwinder becomes active and gives the wrong answer, while I'm actually
71859 This commit fixes a comment describing each relaxation pass and reduces
71866 * elfnn-riscv.c (_bfd_riscv_relax_section): Fix a comment to
71893 "Local labels are never absolute" says the comment. Except when they
71899 struct definitions, so delete the comment and assertions.
71996 * I tightened the regexp in dwarf-insert-substructure. This prevents
72006 (dwarf-insert-substructure): Tighten regexp.
72013 Fix comment in gdb.rust/fnfield.exp
72014 gdb.rust/fnfield.exp has a comment that, I assume, I copied from some
72331 for nothing. I however, noted in its comment that it is an
72542 fixup_section has a long comment explaining that the call should only
72747 additional 'thread 1' is redundant. In fact, there's a comment to
72815 gdb: adjust comment on target_desc_info::from_user_p
72975 (_bfd_dwarf2_slurp_debug_info): Tidy. Correct outdated comment.
73617 [gas] Update .loc syntax comment in dwarf2dbg.c
73618 I noticed that a comment in gas/dwarf2dbg.c describing .loc syntax was missing
75144 There's a comment a few lines earlier saying that demand_copy_C_string
75146 I decided not to duplicate the comment.
75354 either x86, x86_64, or aarch64, mainly by changing the comment style.
75488 Fix this by dropping "rip" from the regexp.
75533 due to a mismatch between the regexp and the different output due to using
75536 Fix this by making the regexp less strict.
75542 gdb, i386: Update stale comment in i386-tdep.h.
75543 The comment seems no longer valid, the functions technically check for
77547 libctf: update regexp to allow makeinfo to build document
77567 missing in regexp that makes it impossible to match versions higher than
77584 * configure.ac: Update regexp to match versions higher than 7.0.
77613 COFF CALC_ADDEND comment
78193 max-page-size setting active at the time.
78402 [gdb/testsuite] Fix regexp in gdb.threads/dlopen-libpthread.exp
78403 Fix regexp in gdb.threads/dlopen-libpthread.exp:
79298 * po/SRC-POTFILES.in: Regenerate.
79531 * coffcode.h: Update coff long section name comment.
80868 The problem is that the regexp used here:
80875 Fix this by making the regexp less strict.
81058 This patch fixes a review comment by Tom de Vries. He pointed out
81059 that the new timestamp.exp should use the $decimal convenience regexp.
81663 Add a comment to make it clear where/how this file is used.
81790 regardless of the active arch backend (which can be 32 or 64-bit).
82044 sim: mips: always resolve active bfd mach dynamically
82046 that is always active when running a program. We already have access
82445 Regen opcodes/po/POTFILES.in
82623 * bfd.c (bfd_get_section_limit_octets): Add comment.
83537 I've also fixed a typo in the class comment.
83749 as gdb.rust/traits.exp was the only place an extra regexp was passed
83910 described in the comment that's being removed.
84087 to reference macro invocation sites. As mentioned in a comment this may
84787 Checking mips relocs is not without some difficulty. See the comment
85129 Expand comment.
85468 quit and left a perror "active". However, reading that variable would
85481 Prevent an illegal memory access when comparing the prefix of a section name regexp.
85849 explained by the comment, but basically this is a scenario that should
85930 * po/POTFILES.in: Likewise.
86032 As a comment near the top of match_template() already says: We really
86282 slightly, bringing a piece of code out of sync with its comment, and
86288 At the very least a comment in process_operands() is stale. Beyond that
86297 To be on the safe side assume 2: Update the comment and fold the
86301 For FMULP also add a comment paralleling a similar one FADDP has.
87266 - Better comment in target_kill
87302 to find active process targets. And after the kill, the inferior is
88685 Fix step-over-syscall.exp matching regexp for $bpnum.$locno matching
88687 The regexp matching breakpoint hit must take the added locno into account.
88716 gdb/arm: Update active msp/psp when switching stack
88718 of msp_s, msp_ns, psp_s or psp_ns. When switching active sp, the
88799 With the addition of $gdb_prompt in the regexp testing for breakpoint hit,
88802 Also fixed a typo in a comment.
88900 * testsuite/gas/riscv/csr.s: Add 'Ssstateen' extension to comment.
89166 described in the comment on the function_range proc in lib/dwarf.exp,
90370 (md_assemble): Expand comment before swap_operands() with rmpquery.
90409 The problem is the regexp in get_set_option_choices, it is possible that
91326 Since I was already touching the file, I also added a comment at the top
92300 with no core value, and the regexp in the test doesn't match (it
92375 A debugging session is active.
92407 A debugging session is active.
92445 A debugging session is active.
92539 This wrong comment was introduced by previous AVX-VNNI-INT8 commit.
92698 a PTRACE_EVENT_CLONE, and libthread_db.so isn't active.
92704 active PTRACE_O_TRACEFORK, PTRACE_O_TRACEVFORK, or PTRACE_O_TRACECLONE
92999 values to the instructions. The comment giving the name of the instruction
93363 ';' does not always indicate the start of a comment, and commit
93382 for cpu state, pass down the active cpu that's already available.
93767 here, everything after the '@' is a comment that is displayed at the
93866 opcodes/arm: use '@' consistently for the comment character
93867 Looking at the ARM disassembler output, every comment seems to start
93869 start an assembler comment.
93875 Turns out I was wrong, '@' is actually the ARM assembler comment
93878 nop ;@ comment
93881 second contains no instructions, just the '@ comment' comment text.
93885 nop @ comment
93887 is a single 'nop' instruction followed by a comment. And finally,
93890 nop ; comment
93893 second contains the instruction 'comment', which obviously isn't
93902 As '@' is the actual comment start character then clearly the '@' and
93903 anything after it can be styled as a comment. But what about ';' in
93904 the second example? Style as text? Style as a comment?
93906 And the third example is even harder, what about the 'comment' text?
93907 Style as an instruction mnemonic? Style as text? Style as a comment?
93910 '@' consistently as its comment character, and remove all the uses of
94504 description comment based on current spec. Limit instruction
95462 with a comment and an empty statement.
95887 * po/hu.po: Updated Hungarian translation.
96034 dependencies were explicitly documented in comment anywhere.
96071 dependencies were explicitly documented in a comment anywhere.
96180 is matched using regexp "Enable debuginfod?.*" with matches only the first two
96184 Fix this by included the interactive prompt in the regexp.
96306 Regen ld/po/BLD-POTFILES.in
96722 The regexp in the test-case expects the full $binfile pathname, but we have
96725 Fix this by making the regexp less strict.
97505 The problem is that styling is enabled, and that is causing a regexp mismatch.
97591 tests. Also the LSP test comment indicating there is something wrong
97892 * riscv-dis.c (xlen): Move before default_isa_spec. Add comment.
97893 (default_isa_spec, default_priv_spec): Add comment.
97898 (riscv_disassemble_insn): Fix comment about the Zfinx "extension".
97899 Add comment about the riscv_multi_subset_supports call.
98896 code to use gdb_iswprint, and removes a somewhat confusing comment
99211 and are due to the fact that the actual gdb output doesn't match the regexp:
99226 and because the regexp doesn't match, it triggers an implicit clause for
99231 - the regexp by making it less strict
99324 does not match the used regexp:
99327 && ![regexp "^No MPX support\r\n" $output]]
99335 Fix this by making the \r in the regexp optional.
99409 with FPCAR to identify if lazy FPU state preservation is active for
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.
100206 for its comment character, however, gas and libopcodes use '#' as the
100207 comment character, as gas uses ';' for an instruction separator.
100209 Unfortunately, Pygments expects ';' as the comment character, and
100211 'raiseonerror' filter, that any line containing a '#' comment, will
100218 a comment token. Every token after this (until the end of the line)
100219 is also converted into a comment.
100232 that will format '#' and all other text on the line, as a comment,
100326 instruction, call reset the in-comment flag. If the instruction
100327 being disassembler ends in a comment then the first disassembly pass
100328 will have set the in-comment flag to true. This shouldn't be a
100330 re-disassembly pass, if libopcodes is disabled, so the in-comment
100419 The asserts that validate the API as described in the comment I added
100507 gdb/gdbarch: add a comment to gdbarch_register_name
100515 The claims in the comment are I feel, best demonstrated with the
100533 this commit adds a comment to gdbarch_register_name, this comment is
100537 comment, and will even add the asserts shown above to
100654 As the TCL regexp matching is greedy, TCL will try to match as much as
101113 using regexp fun_re, which requires a line field:
102564 positive, the regexp for checking where gdb has stopped was relaxed a
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).
103292 See the comment at the beginning of bfd-errors.exp for details about
103664 The "@" char starts a comment on ARM.
103769 regexp, or until it steps too many times - defined as an optional
104054 terminate called without an active exception
104148 to cause problem with clang, as documented in the comment for proc
104170 - the comment about the return value was wrong,
104237 that's only active for ada:
104736 * dis-asm.h (disasm_option_arg_t): Update comment of values
105084 Remove obsolete filtering comment
105085 top.h has an obsolete comment about the use of _unfiltered.
105089 moment" comment. These comments aren't useful and I think the moment
106086 * reloc.c (bfd_reloc_other): Correct comment.
107001 gdb/riscv: improve a comment about fcsr, fflags, and frm registers
107002 There's a comment in riscv-tdep.c that explains some of the background
107006 This comment (and the functionality it describes) relates to how QEMU
107014 When I originally wrote the comment I thought it didn't matter which
107016 long as we just used one of them. The comment reflected this belief.
107024 copy of the register, so nothing is broken, but the comment is wrong.
107025 This commit updates the comment to better describe what is actually
108858 While there also amend the affected function's leading comment to also
109967 sparc targets. Expand comment.
109992 Fix this by updating the regexp.
110345 (1) Put an introductory comment to explain the purpose for some functions.
110351 (4) Remove "*" in the subsequent comment lines.
110504 I've also updated the comment on 'struct gdbarch_tdep_base' to fix a
110505 typo, and the comment on the 'gdbarch_tdep' function, to mention that
110606 breakpoint with a location, so the regexp returned by
112447 Note that there are 4 active threads, and scheduling elts_per_thread on each
112513 The regexp in the test-case expects "size 17".
112515 Fix this by updating the regexp.
112877 because the test's regexp has a ".*" after the part that matches
112878 thread 3. This commit tightens that regexp to catch such a bug. It
112880 regexp in the same way.
113058 We have in per_cu->set_lang this comment:
113596 set/show style disassembler comment
114795 related comment, which hasn't been applicable anymore since the
115193 Fix this instead by updating the regexp to allow the message.
115458 opcodes/aarch64: split off creation of comment text in disassembler
115463 In some cases, a comment is included in the operand representation,
115475 updated to pass an extra buffer, and print any resulting comment.
115480 while in other cases the comment was separated with two single spaces.
116265 Note that I didn't touch */po/*.po{,t} on the assumption that these
116456 gdb/arm: Update the value of active sp when base sp changes
116459 When plain "sp" is updated during unwinding of the stack, the active
117095 changing the active CU mappings when a link has already been done
117534 Fix this by matching using a regexp instead.
117680 identify the active one, compare the values of the different
118101 "Q" names are pseudo-registers. This patch fixes the comment.
118138 [gdb/testsuite] Fix regexp in gdb.ada/mi_var_access.exp
119112 (as can be read in a comment in compiler.c) compiler_info should be
119638 comment in the documentation. This patch removes the test and the doc
119639 comment.
119790 Remove obsolete Python 2 comment
119791 I found a comment that referred to Python 2, but that is now obsolete
119793 remove the comment.
119795 There's a similar comment elsewhere, but I plan to remove that one in
119849 The current implementation of parse_number contains a comment about PR16377,
119861 The current implementation of parse_number contains a comment about PR16377,
120418 overflow at BUG! comment.
120458 string buffer. If this happens for reasons explained in the comment,
121024 line issue mentioned above. A comment was added to maybe remove this
121336 whitespaces for the regexp.
123096 The comment about set_raw_breakpoint being used in gdbtk sources is
123436 object-regexp in some cases, but presents output as though no
123437 object-regexp was passed.
123440 filter based on object-regexp, and in the other, to remove the
123441 object-regexp from the command and leave all the output.
123811 conversion is further tied to # being a line comment character, anything
123813 is supposed to be treated as a comment, i.e. ignored. Therefore we
123816 O_constant as a comment as well.
123955 affected as well, so update the comment.
125421 wait_for can handle a multi-line regexp.
125531 The problem is that the regexp consuming the "Inferior exited normally"
126826 the '$gdb_prompt $' regexp, and this does not handle the case that '(gdb) ' is
126829 Fix this by using a gdb_test_multiple instead with a '$gdb_prompt ' regexp, so
127460 libctf: add a comment explaining how to use ctf_*open
127467 * ctf-api.h (ctf_*open): Improve comment.
127903 Additionally, the comment in the vsx expect file about the initialization
127981 does not check if a step over is active when restarting other threads:
128004 they all seem to check that there is no step over currently active
128109 To handle the problem described in the comment in handle_no_resumed, I
128111 but only the event target. That comment describes a kind of race
128903 obvious that only a single index can be active at a time, and also
129476 This patch slightly relaxes the regexp -- removing a space -- so that
129538 regexp:
129544 Fix this by adding the missing ^ at the regexp start.
129584 The existing comment:
130140 - Remove that weird "Useless if!!!" FIXME comment. It's been there
131140 As the comment says, hppa doesn't support use of BFD_RELOC_* in
131633 - rewrite the regexp such that each annotation is on a single line,
131635 - add a regexp variable optional_re, that matches all possible optional
131636 output, and use it as a separator in the first part of the regexp
132247 This was based on the comment on value::contents, which suggest that
132547 The problem is that the test expects the following regexp:
134564 Regen bfd po/SRC-POTFILES.in
135414 Minor comment updates in utils.h
135863 comment in patch context precedes (and explains) the setting
135875 original intention as well as the comment there. For constructs like
136003 call_site_find_chain_1 has a comment claiming that recursive calls
136156 sim: fix a comment typo in sim-load.c
136542 (indicating that part of the comment was wrong). Finally for there to be
136553 Delete that code as well as the corresponding part of the comment.
137393 (demand_empty_rest_of_line): Remove "know" check. Expand comment.
137396 buffer_limit plus one. Expand comment.
137688 strictly speaking an overlap in just one size (see the code comment) is
137920 * po/SRC-POTFILES.in: Regenerate.
138843 fallthrough comment instead of attribute.
138870 checking that the regexp was not output. But that's not what we are
138871 doing, we're checking either for the regexp, or for no output, hence
138993 match the regexp: "^[a-zA-Z][-_a-zA-Z0-9]*$" (without the quotes).
139092 The comment at the top of gdbarch-components.py tries to explain how
139093 the validation is done. I didn't understand this comment completely,
139176 deprecated_target_wait_hook usage: there's a commit comment telling
139262 Relax regexp in gdb.rust/unsized.exp
139270 unsized array looks right, this patch relaxes the regexp and changes
139404 Fixes a minor typo, in a comment, in the gdbarch-components.py script.
140499 comment typo fix
141765 "DO NOT EDIT!" says the comment at the top of bfd-in2.h. Move the new
142114 sim/common: Improve sim_dump_memory head comment
142117 * sim-memopt.c: Improve head comment.
142319 comment.
142446 similar tests. There's a comment that mentions this, though
142503 Neither the commit introducing progos, nor the top comment
144741 So, this commit adds a comment in location.c mentioning that the
144924 gdb: update the comment on string_to_event_location
144925 The comment on string_to_event_location is (I believe) out of date.
144936 be discussed in the header comment.
146112 reference, as explained in the comment. I think it would make sense to
147200 here, causing unnecessary divergence. While not an active issue, it is
147612 It might seem to work, but only if '/' is a start of comment char.
147614 * testsuite/ld-elf/dt-relr-1.s: Use # for comment.
147733 regexp that it uses is not tailored for the output printed by the
148301 gdb: testsuite: fix wrong comment in gdb.base/charset.c
148303 to fix the wrong comment.
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.
149747 Note that complete_command is not touched due to a comment there
150355 out */po/*.pot which we don't update frequently.
150366 gdb: copyright: fix a few comment typos
150680 pager will still be active. This is irritating, because the output
150941 * config/tc-riscv.c (abort_version): Updated comment.
151498 gdb/ada-exp.y: Reformat comment to follow GDB's coding standards
151499 This commit reformats a comment in gdb/ada-exp.y to avoid
151500 the leading '*' at the beginning of each line of the comment.
151502 gdb/ada-lang.h: Reformat comment to follow coding standards
151503 This commit reformats a comment in gdb/ada-lang.h to avoid
151504 the leading '*' at the beginning of each line of the comment.
151788 This adds a comment to document how to update gdbarch.
152033 Fix regexp for loads via debuglink section.
152510 string should be nullptr. Also removed a cryptic 'gdb_????' comment,
153022 The comment on top of gdb/testsuite/boards/remote-stdio-gdbserver.exp says
153250 The ## marker tells automake to not include the comment in its
153251 generated output, so use that in most places where the comment
156030 active connections.
156660 regexp.
156963 * po/BLD-POTFILES.in: Regenerate.
156964 * po/SRC-POTFILES.in: Regenerate.
156969 * po/fr.po; Updated French translation.
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.
157762 "switch -regexp -- $opt {
157865 bfd: remove wrong comment in xcofflink.c
157866 This comment was long time ago associated to the function
157870 * xcofflink.c: Remove wrong comment.
158260 I've also added a comment explaining the reason for needing to check
159187 mention in the comment above FUNCTION_NAME doesn't apply anymore.
159268 which makes the regexp matching more difficult (see commit 1f28b70def1
159269 "[gdb/testsuite] Fix regexp in gdb.base/foll-vfork.exp").
159924 [gdb/testsuite] Fix regexp in gdb.base/foll-vfork.exp
159976 * po/POTFILESin: Regenerate.
160501 comment and code near the start of the function:
160511 Also, as described by this comment prior to the 'async' field
160671 The comment referenced earlier regarding 'executing_breakpoint_commands'
161380 So, I've marked the 'return 0' with a comment, and now the test will
161383 I also removed an old comment from 1997 talking about how these tests
161384 will only pass with the HP compiler, followed by an additional comment
161648 Adjust the comment on top of `struct inf` to clarify the purpose of that
162721 gdb: or1k: fixup linux regcache comment
162722 The old comment was not properly updated from the RISC-V example used.
162733 Hence the comment about registers definitions being inline with glibc.
162883 Fix this by using the /* ... */ comment style instead:
163171 * Makefile.am: Remove obsolete comment.
163517 zero index entry. Remove outdated comment.
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.
163745 The problem is that the regexp used:
163752 Fix this by updating the regexp.
163779 The regexp expects a breakpoint-created event, but that's actually suppressed
163786 Fix this by updating the regexp.
163996 meant that the active union field was in fact
164007 the union matches what is supposed to be the active field.
164775 A debugging session is active.^M
164781 A debugging session is active.^M
165338 Fix this by likewise shortening the regexp to before the comma.
165393 Fix this by updating the regexp to expect libpthread or libc.
165635 which is not matched by the regexp.
165637 Fix this by updating the regexp.
165643 [gdb/testsuite] Refactor regexp in gdb.base/annota1.exp
165644 Refactor regexp in gdb.base/annota1.exp to reduce indentation and repetition.
165897 The regexp expect running messages for all threads, but we only get one for
165904 Fix this by updating the regexp.
166002 which is a known source of problems, as explained in the comment of proc
166235 read_call_site_scope" , I removed the comment:
166250 This could be fixed by simply reinstating the comment, but we're trying to
166254 - reverting commit b4c919f7525, apart from the comment removal, such that
166625 gdb: Fix comment in riscv_scan_prologue
166626 I found an inaccurate comment in riscv_scan_prologue. This commit fixes
167237 while the regexp expects "Symbol \"dl_main\" is a function at address $hex\\."
167468 The problem is that the regexp expects "hit Breakpoint $decimal". The "hit"
167482 Fix this by removing "hit" from the regexp, making the regexp more similar to
167686 So, loosen the regexp to accept "inf 1" and "inf 2" in any order.
168351 * libctf.ver: Give every symbol not in libctf-nobfd a comment on
168670 /* snip comment */
168732 Cache state: 3 active lines, 85 hits^M
168735 The regexp expects "Contains data for process $decimal".
168739 Fix this by updating the regexp.
168865 comment from the implementation, on the basis that it seems obsolete
169419 because it tries to do it in a regexp clause in a gdb_test_multiple, which
169712 The failure is caused by the regexp expecting variable r followed by
169739 Fix this by updating the regexp to expect "^done,stack-args=" instead of
170174 parameter. Update comment. Delete overload without addend.
170204 Comments are removed since it should be obvious without a comment, and
170220 Delete overload without addend later. Update comment.
170456 in the comment of proc function_range in gdb/testsuite/lib/dwarf.exp.
170525 Fix this by updating the regexp in gdb_load_no_complaints.
170908 which means that this regexp in proc test_with_self fails:
170923 Fix this by updating the regexp to not require "in" before " main".
170942 The mistake is that I passed an output regexp argument to a parameter
170946 Add support for checking output, to be able to handle the output regexp
171073 A regexp pattern with escapes like this is hard to read:
171093 regexp.
171191 Fix this by updating the regexp.
171229 by updating the regexp.
171231 Then I ran with clang and found another FAIL, fix by updating the regexp.
171729 existing comment doesn't seem to be referring to the structure, it
172013 I provide some details regarding the bug in a comment near the
172374 * po/BLD-POTFILES.in: Regenerate.
172960 proc arange { arange_start arange_length {comment ""} {seg_sel ""} } {
172978 { comment "" }
173173 arange $addr $len [<comment>] [$segment_selector]
173272 FAIL: objdump --source-comment
173440 The problem is that the regexp expects a gdb prompt immediately after the
173443 Fix this by updating the regexp.
173451 * lib/gdb.exp (gdb_load_no_complaints): Update regexp to allow
173501 * testsuite/gas/i386/bad-bcast.s: Add a comment.
174463 restore_original_signals_state prior to forking, so the comment on
174467 comment on SIGQUIT talks about problems with BSD4.3 and vfork,
174473 Finally, the header comment on the function now called
174585 PR28198, Support # as linker script comment marker
174588 comments. Extend # comment handling to all states.
175282 Make the expected output regexp for the kill command tighter (it
175293 regexp tighter, run inferior after killing it. Kfail when
176257 * config/tc-i386.c (struct Broadcast_Operation): Adjust comment.
177028 Fix this by updating the regexp.
177036 * gdb.dwarf2/dw2-using-debug-str.exp: Update regexp to match
177189 and the regexp doesn't match because it expects the "Number of read/unread
177192 Fix this by updating the regexp.
177257 at length in the gdbsupport/common-defs.h comment.
178511 From the comment in cmd_list_element, it sounds like at some point it
178659 independent test procedures. For example, it's possible to comment all
178679 makes it easier to comment out some parts of the test while working /
178968 Tag closing brace with comment.
179126 All branches in the "active" code are remove, and the target is
179673 of historical reasons plus a desire (mentioned in a comment somewhere)
180320 Note that the comment mentions __pthread_initialize_minimal, but in both cases
180321 it has already run before we hit the callback, so it's possible the comment is
180329 Fix this by updating the regexp patterns to agree with what libthread-db is
181512 Fix this by updating the regexp to make the "ERROR: " prefix optional.
181675 * po/gas.pot: Regenerate.
181682 * po/bfd.pot: Regenerate.
182057 * lib/gdb.exp (gdb_test_lines): Add handling or -re-not <regexp>.