Lines Matching +refs:po +refs:mode +refs:menu +refs:layout
65 (note that most modern distros use this option), the layout of the
179 generally omitted (unless in suffix-always mode). All NDD insns have a
340 indexing offset quantity and offset mode is allowed - The value is
345 This indexing quantity/mode pair is selected by the setting of a
367 the data register addressing mode and whether the address register is
371 The use of a single bit to specify both the indexing mode and indexing
2731 register table entry is marked as implemented in the 128-bit mode via
2965 /* If currently in Ada mode, and the lookup name is wrapped in
2973 checks, or promoting the verbatim mode to not be a purely Ada feature
3799 3) Build with --enable-maintainer-mode --enable-cgen-maint=yes.
3800 4) Check out */po/*.pot which we don't update frequently.
5358 target apx, 64-bit mode and with rex_prefix.
5361 in 64-bit mode.
6438 * ::amd_dbgapi_wave_resume in single step mode. Since the wave terminated
7384 [gdb/tui] Show regs when switching to regs layout
7385 When starting gdb in CLI mode, running to main and switching into the TUI regs
7386 layout:
7388 $ gdb -q a.out -ex start -ex "layout regs"
9002 ~8000 entries (each different addressing mode is considered a different
9042 [gdb/tui] Handle shared border in fixed-sized layout
9136 gdb/testsuite: fix gdb.ada/complete.exp timeout in READ1 mode
9138 gdb.ada/complete.exp when testing in READ1 mode, e.g.:
9652 Fix hardware watchpoints in replay mode
9655 trigger in reverse execution or replay mode. This was documented in
11465 layout of the generated gdb-index.
12273 i386: Use a fallback XSAVE layout for remote targets
12275 XSAVE extended region, but does not provide an XSAVE layout, use a
12276 fallback XSAVE layout based on the included registers. This fallback
12277 layout matches GDB's behavior in earlier releases which assumes the
12278 layout from Intel CPUs.
12280 This fallback layout is currently only used for remote targets since
12281 native targets which support XSAVE provide an explicit layout derived
12507 Running gdb.tui/tui-layout-asm-short-prog.exp ...
12508 gdb compile failed, gdb.tui/tui-layout-asm-short-prog.S: Assembler messages:
12509 gdb.tui/tui-layout-asm-short-prog.S:23: Error: \
12605 Note that for LA the restriction is slightly too strict: In non-PIC mode
12607 libopcodes doesn't know what mode gas is presently assembling for, so we
12779 positive offsets. Linux on zSeries in ESA mode executes in 31-bit
12780 addressing mode. Therefore the ESA test cases are assembled with -m31.
12781 In 31-bit addressing mode the address computation using those large
12784 Linux on Z in z/Architecture mode executes in 64-bit addressing mode.
12786 In 64-bit addressing mode the address computation using those large
13303 - detecting the situation and dropping windows from the layout if
13324 /* This should always be made visible by a layout. */
14072 waiting for further input from the user (or in async mode, for an
14078 (b) When we resume the inferior. In synchronous mode, resuming the
14416 {disp16} is invalid to use in 64-bit mode, while {disp32} is invalid to
15609 In all-stop RSP mode, since events can only be forwarded to GDB one at
15617 event is never sent. This patch makes sure that in non-stop mode, the
15922 - called in sync mode, and,
15946 sync mode, which is unexpected by the core and fails an assertion.
15957 remote all-stop mode. There's no good reason for this, it just
15958 happened that THREAD_EXITED was only ever reported in non-stop mode so
16156 - all-stop mode, user issues 'continue', all threads are set running,
16159 - non-stop mode, user issues 'continue', other pre-existing threads
16168 - all-stop mode, user issues 'stepi', stepping will be done in place
16174 - non-stop mode, user issues 'stepi', stepping will be done in place
16190 + [non-stop mode only] GDB stops all threads. In all-stop mode all
16197 + [non-stop mode only] GDB resumes all threads that it previously
16219 + GDB single steps the thread of interest, [non-stop mode only] all
16225 + [non-stop mode only] GDB resumes the thread, now past its
16227 + [all-stop mode only] GDB resumes all threads.
16808 linking can fail if too many stubs are inserted and the section layout
16910 omit explicit "&x64" from any insn templates dealing with 64-bit-mode-
16923 possibly be supported by CPUs not supporting 64-bit mode.
17096 inferior. But for testing I've made use of non-stop mode and
17263 * doc/bfd.texi (BFD front end): Add Threading menu item.
17266 * po/bfd.pot: Regenerate.
17281 * po/bfd.pot: Regenerate.
17295 * po/bfd.pot: Regenerate.
17667 ==3389== by 0xA8C23C: tui_layout_split::apply(int, int, int, int, bool) (tui-layout.c:1030)
17668 ==3389== by 0xA8C2A2: tui_layout_split::apply(int, int, int, int, bool) (tui-layout.c:1033)
17669 ==3389== by 0xA8C23C: tui_layout_split::apply(int, int, int, int, bool) (tui-layout.c:1030)
17670 ==3389== by 0xA8B1F8: tui_apply_current_layout(bool) (tui-layout.c:81)
17678 ==3389== by 0xA8B1C6: tui_apply_current_layout(bool) (tui-layout.c:78)
17779 discrepancy here between how the DWARF reader works in "readnow" mode
18053 When running test-case gdb.tui/tui-layout-asm-short-prog.exp on AlmaLinux 9.2
18056 FAIL: gdb.tui/tui-layout-asm-short-prog.exp: check asm box contents
18073 filename = "tui-layout-asm-short-prog.S",
18074 filename_for_id = "$gdb/build/gdb/testsuite/tui-layout-asm-short-prog.S",
18085 <1a> DW_AT_name : tui-layout-asm-short-prog.S
18091 making the effective name $gdb/build/gdb/testsuite/tui-layout-asm-short-prog.S.
18096 $gdb/src/gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.S
18153 mode.
18174 (Nq): Change mode from q_mode to q_mm_mode.
18545 Consider the following situation, GDB is in non-stop mode, the main
18578 only happen in non-stop mode, the assert becomes:
18656 non-stop mode) for the stop notification to arrive after the detach is
19505 ensure (when building in dev mode) that we're casting to the right kind
20074 thumb mode.
20561 async mode then the async token should not be marked. */
21613 non-async mode, can't read the auxv data while an inferior is running
21624 remote is in async mode and the remote is currently waiting for a stop
21635 new_objfile observer is used in the special mode that actually means
22495 variable sizes. It also exposes a new mode called streaming mode.
22501 In streaming mode, the SVE registers have their sizes based on svl rather than
22771 n64 ABI and consequently produce a section layout that is different from
23008 running (and in non-async mode) then GDB will try to send a fileio
23290 TUI layout asm.
23326 -ex "layout asm" \
23732 to figure out the layout of the XSAVE area based on what features are
23747 layout.avx_offset = 576;
24066 gcc 13.2.1, I run into (layout adapted for readability):
24261 breakpoint to this instruction set correctly in both 32- and 64-bit mode.
24848 When gdb is compiled with ncurses mouse support, gdb's TUI mode
25176 stop event. Enabling this mode can make execution of waves significantly
25430 when in MI mode, and uses this new mechanism to skip the related section
28562 x86 nat: Add helper functions to save the XSAVE layout for the host.
28581 core: Support fetching x86 XSAVE layout from architectures.
28582 Add gdbarch_core_read_x86_xsave_layout to fetch the x86 XSAVE layout
28605 The standard layout of the XSAVE extended state area consists of three
28606 regions. The first 512 bytes (legacy region) match the layout of the
28609 with a fixed layout. The final region (extended region) contains zero
28617 component in the "standard" layout for a given CPU. (There is also a
28618 "compact" format which uses an alternate layout, but existing OS's
28619 currently export the "standard" layout when exporting XSAVE data via
28622 To date, GDB has assumed the layout used on current Intel processors
28625 fails on recent AMD processors which use a different layout.
29084 While doing so, in 64 bit mode the words were not zero extended and was coming like 32 bit mode.
29172 + = this->rela_dyn_section(layout)->current_data_size();
29405 moved memory layout around a bit I adjusted the test output. Some
30676 do with --enable-maintainer-mode, and added --enable-cgen-maint
30679 layout set up for opcodes rather than sim. Fix that by making both
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.
31256 unix board is that the test is only run in the default operating mode,
31259 If we adjust the test script so that it runs in the default mode and
31264 possible to turn on non-stop mode and have the test still work, so
32874 into the original i386_cpu_flags layout. This way the table in the final
33203 [gdb/testsuite] Improve failure mode in gdb.dwarf2/enqueued-cu-base-addr.exp
36140 ./ld-new: unrecognised emulation mode: elf32btsmipn32
36776 In gdb/tui/tui-layout.c, we have:
36793 - first gdb/tui/tui-layout.c,
37131 For extreme code mode, the instruction sequences is
37716 always mode.
37846 In the SingleKey mode, the prompt is not printed so that
37848 we temporarily leave the SingleKey mode. */
38234 where, when testing with non-stop mode, GDB stops in a different
38260 commit, GDB is in follow-fork-mode child. If you have not done so, it
38283 5. As GDB is running in all-stop on top of non-stop mode, in the
38390 gdb: fix an issue with vfork in non-stop mode
38396 … gdb: fix handling of vfork by multi-threaded program (follow-fork-mode=parent, detach-on-fork=on)
38492 non_stop mode.
38517 mode being on, target-non-stop being off, follow-fork-mode being set
38620 mode, then, if the user tries to detach there is a chance that thread
42668 relocations until the end of relaxation once the layout has
42689 * layout.cc (Layout::add_target_dynamic_tags): Add custom_relcount
42692 * layout.h(Layout::add_target_dynamic_tags): Update prototype.
42729 agent_expr::reg_mask") caused a regression in libstdc++ debug mode.
43078 (typically) in suffix-always mode.
44490 Say we're in TUI mode, and type "sun":
44495 After switching to SingleKey mode using C-x s, we have just:
44509 mode.
44521 I noticed that there's no test-case excercising SingleKey mode, so add a test-case.
44967 [gdb/tui] Factor out border-mode help text
44968 I noticed that the help texts for tui border-mode and tui active-border-mode
46198 tui new-layout command-layout cmd 1^M
46200 (gdb) ERROR: Undefined command "tui new-layout command-layout cmd 1".
46248 [gdb/tui] Fix fingerprint for cmd-only layout
46249 I added a cmd-only layout:
46251 (gdb) tui new-layout cmd cmd 1
46255 (gdb) layout cmd
46259 However, after going back to layout src:
46261 (gdb) layout src
46267 layout the fingerprint of the cmd window in the layout is taken. If the
46275 should be "C" for the cmd layout.
46753 Rework layout to be similar to that from 'objdump -p'.
47029 1. Start GDB in MI mode
47100 Consider the following scenario. We start gdb in TUI mode:
47110 In TUI mode, gdb uses a custom rl_getc_function tui_getc.
47415 ia64-linux-gnu: "Explicit stops are ignored in auto mode"
47859 "When a file is opened with update mode ('+' as the second or third
47860 character in the mode argument), both input and output may be
48238 For instance, the line representing the TUI status window with attribute mode
48408 printing the value using mi-mode, which was not covered by the fix.
48409 Porting the fix to the mi-mode code path resolved the issue.
48412 2fc3b8a4cb8, independently fixed the issue in both the cli- and mi-mode
48416 the mi-mode scenario to protect against any future divergence in this
48693 too relaxed: Any indication of a mode that's possible with BFD64 only
49612 is the only mode that aims to mimic gdb_test.
50819 add a KFAIL for that failure mode.
50830 KFAIL for that failure mode.
50902 If we start GDB in MI mode and continue to 'sum', the behaviour of
51533 building in C++ mode to avoid build errors.
51598 (gdb) PASS: gdb.tui/main.exp: set interactive-mode off
52899 Term::command "layout src"
52902 - "(gdb) layout src", and then
52905 Because the "layout src" command enables the TUI there's just a prompt.
52913 [gdb/testsuite] Fix timeout in gdb.tui/new-layout.exp
52914 In test-case gdb.tui/new-layout.exp we run into:
52917 PASS: gdb.tui/new-layout.exp: layout=cmd_only {cmd 1} {} {}: \
52923 Term::command "layout src"
52926 Before the "layout src" command we have:
52929 0 +-tui-layout.c-------------------------+(gdb) layout example3
52930 1 | 20 { |(gdb) layout src
52932 3 | 22 } |(gdb) layout example4
52933 4 | 23 |(gdb) layout src
52935 6 | 25 |(gdb) layout example5
52957 0 +-tui-layout.c-----------------------------------------------------------------+
52983 The Term::command "layout src" is waiting to match:
52984 - "(gdb) layout src", and then
52989 | 26 |(gdb) layout src
53045 22 #0 main () at tui-layout.c:21
53206 in C99 or C11 mode
53468 fact that we're in "auto language" mode is noted by the language_mode
53621 Likewise we can detect tui/30337 by doing a resize in TUI mode and doing
53640 all reported values are updated, except for curses when not in TUI mode.
53643 the curses lines unless in TUI mode, or annotate those lines such that it's
54544 same, depending on the `set follow-exec-mode` setting. But even if they
54978 This changes the layout of the disassembly window back to what it was before
56231 outside of maintainer mode dependencies will cause the subset of files
56234 under bfd/po/, i.e. in maintainer mode.
57367 outside of 64-bit mode unused (typically ignored) register encoding bits
57370 can't even be used outside of 64-bit mode). And then there are odd tests
57438 up cannot be used with .insn outside of 64-bit mode. Users would need to
57505 /* Get out of tfind mode, and kill or detach all inferiors. */
59698 Add truncation mode to gdb_mpz
59980 …* layout.cc (Layout::create_gold_note): If linker-version is enabled put the version string into t…
60567 The stub layout is kept fixed between sizing and building the stubs,
60569 introduce padding between stubs when those are relaxed. Stub layout
61463 Regen ld/po/BLD-POTFILES.in
62060 Intel Syntax mode otherwise bogus insn operands may be accepted.
63132 FAIL: gdb.tui/completion.exp: completion of layout names: \
63145 [gdb/testsuite] Fix gdb.tui/tui-layout.exp for remote host
63146 When running test-case gdb.tui/tui-layout.exp with host board
63149 FAIL: gdb.tui/tui-layout.exp: terminal=dumb: execution=false: layout=asm: \
63150 layout asm (timeout)
64913 difference is listed in the documentation for bash's POSIX-correct mode
65260 Changing mri mode between macro definition and use isn't good. This
65266 what should really happen is that macros be marked as being mri mode
65271 * macro.c (macro_expand): Don't segfault in mri mode if NARG
65477 inferior in non-stop mode. The worker thread then exits, but the main
65758 based on the current UI mode.
65762 this logic. If the separate UI mode should not be used then BODY will
66380 - you're in all-stop mode,
66387 parent/child, depending on "set follow-fork" mode.
66486 - in all-stop mode, "info program" displays info about the last stop.
66490 - in non-stop mode, because all threads are controlled individually,
66513 while in non-stop mode, we get:
66530 If the thread is running, we get, in non-stop mode:
66542 If the thread has exited, we get, in non-stop mode:
67909 In 64-bit mode BT can have REX.W or a data size prefix dropped in
67910 certain cases. Outside of 64-bit mode all 4 insns can have the data
68117 [aarch64] Enable pointer authentication support for aarch64 bare metal/kernel mode addresses
69792 * doc/webassembly.texi (File layout): Remove second argument from
70065 ("perf/x86/intel/pt: Opportunistically use single range output mode"),
70600 allocate the known_window_types map in tui-layout.c
70652 std::unordered_map (in tui/tui-layout.c) which is never deallocated,
70672 only called when trying to apply a new TUI layout - something that
70675 This commit does not update the std::unordered_map in tui-layout.c,
70708 This is because in tui_register_window (tui/tui-layout.c) we use
71037 strncmp_iw_with_mode with mode strncmp_iw_mode::MATCH_PARAMS and
71040 The strncmp_iw_mode::MATCH_PARAMS mode means that strncmp_iw_mode will
71062 mode, we stop the comparison as soon as we hit a '(' in the demangled
71078 I propose to fix this in strncmp_iw_with_mode. When the mode is
71098 To work around this issue, in strncmp_iw_with_mode, when mode is
71984 Add full display feature to dwarf-mode.el
71985 I've found that I often use dwarf-mode with relatively small test
71992 * I removed a stale FIXME from dwarf-mode. In practice I find I often
72000 * Finally, I've bumped the dwarf-mode version number so that this
72005 * dwarf-mode.el: Bump version to 1.8.
72008 (dwarf-mode-map): Bind "A" to dwarf-refresh-all.
72009 (dwarf-mode): Remove old FIXME.
72995 gdb/testsuite: don't try to set non-stop mode on a running target
72996 The test gdb.threads/thread-specific-bp.exp tries to set non-stop mode
73001 mode as part of the GDBFLAGS, so the mode will be set before GDB
73092 Regenerating BPF target using the maintainer mode emits:
74236 introduced a failure in libstdc++ debug mode. In particular, the new
74248 First, a new mode is introduced: a sorting mode for
74249 cooked_index_entry::compare. In this mode, strings are compared
74262 I regression tested this in libstdc++ debug mode on x86-64 Fedora 36.
74772 gdb/tui: disable tui mode when an assert triggers
74773 When an assert triggers in tui mode the output is not great, the
74777 and so, when the terminal is in raw mode, the cursor does not return
74795 raw mode, it is possible that the backtrace fills the screen. With
74796 the terminal in raw mode we don't have the ability to scroll back,
74799 In this commit I propose that we should disable tui mode whenever we
74830 the name matches multiple windows in the current layout.
74833 layout; if the partial name matches one window in the current layout,
74834 and one or more windows not in the current layout, then this is not
74836 layout.
74843 be present in the current layout, and non-focusable in order to
74848 current layout. Even if GDB does know about the window, but the
74849 window isn't in the current layout, then GDB will say it doesn't
74857 (b) No windows matching "NAME" in the current layout
74859 (c) Window "NAME" is not in the current layout
74863 not in the current layout then one of the other errors will trigger.
74866 are not in the current layout. If NAME identifies a single window in
74867 the current layout then that window will continue to be selected, just
74869 window in the current layout do we then check all the other known
74873 window that is not in the current layout.
74877 about a window, the mention of the current layout will hint to the
75707 window, when the window is part of the current layout. As a result,
75710 first action, which makes the current layout visible).
75746 tui mode, no longer do unless TERM is set to 'ansi'.
75755 now we are testing in tui mode.
75771 tui mode, no longer do unless TERM is set to 'ansi'.
75780 box does appear on the screen, which should indicate that tui mode has
75806 gdb/testsuite: extend gdb.tui/tui-layout.exp test script
75807 In passing I noticed that the gdb.tui/tui-layout.exp test script was a
75808 little strange, it tests the layout command multiple times, but never
75809 sets up our ANSI terminal emulator, so every layout command fails with
75822 After this, any tui test that didn't set the terminal mode back to
75823 'ansi' would fail to activate tui mode.
75825 For the tui-layout.exp test it just so happens that the test patterns
75829 In this commit I have updated the test so we now check the layout
75832 that GDB correctly entered tui mode.
75835 test suite that deliberately tries to enter tui mode in a dumb
78144 mode -- caused gdb to crash.
78157 ELF_MAXPAGESIZE matters much more, with regards to layout of
78190 With ELF_MAXPAGESIZE changed to 4 KiB, layout is sometimes
79298 * po/SRC-POTFILES.in: Regenerate.
79839 The multirun generation mode is a bit of a mess as generated run files
79841 In the multirun mode, be lazy and declare all of these generated source
79852 It also regenerates configuration files using the maintainer mode.
80087 sim: Regenerate using the maintainer mode
80088 Those files have changed by regenerating using the maintainer mode.
80385 To run GDB in this mode, use:
80593 derive from BaseException, port to python3, retain original file mode,
81133 sim: mips: rename "igen" generation mode to "single"
81139 this generation mode. So rename the set of rules from "igen" to
81155 rule & variable in the multi build mode, generalize that and switch
82283 for the old sim_cpu_base layout. There's a lot of noise here, so
82365 need custom state over to the new layout. This includes mn10300 that,
82385 build system) to maintainer/release mode (via spreg-gen.py that
82412 … /bin/sh ./libtool --mode=install STRIPPROG='strip' /bin/sh /src/gdb/gdb.git/install-sh -c -s \
82418 libtool: install: Try `libtool --help --mode=install' for more information.
82445 Regen opcodes/po/POTFILES.in
82496 The Emacs 28 compiler warns about dwarf-mode.el:
82498 Warning (comp): dwarf-mode.el:180:32: Warning: Unused lexical argument `ignore'
82505 * dwarf-mode.el (dwarf-do-refresh): Avoid compiler warning.
84388 supported in 64-bit mode" diagnostic as emitted for other 64-bit only
84389 insns. Also suppress deriving of the suffix in Intel mode except in the
84394 only supported in 64-bit mode" on the SIMD forms of MOVQ) we need to
84900 [gdb/testsuite] Require debug info for gdb.tui/tui-layout-asm-short-prog.exp
84901 When running test-case gdb.tui/tui-layout-asm-short-prog.exp on SLE-12-SP3
84904 FAIL: gdb.tui/tui-layout-asm-short-prog.exp: check asm box contents
84905 FAIL: gdb.tui/tui-layout-asm-short-prog.exp: check asm box contents again
84909 (gdb) file tui-layout-asm-short-prog^M
84910 Reading symbols from tui-layout-asm-short-prog...^M
84911 (No debugging symbols found in tui-layout-asm-short-prog)^M
85227 At first glance, the failure mode doesn't look too bad: we stop
85230 For contrast, if we do the same on powerpc64le, the failure mode is:
85261 Try to avoid this accident and make the failure mode on x86_64 the same as on
85930 * po/POTFILES.in: Likewise.
86765 Actually set m_is_async to current async mode
86766 Looks like this was missed in the async mode implementation.
87515 (background) mode. Each thread is continuously hitting a conditional
87885 -ex "set follow-fork-mode child" \
88261 suffix "derivation" in Intel Syntax mode.
88294 * m68k-opc.c (m68k_opcodes): Only accept 000 and 001 as mode
88817 In mi mode, bkpt_print_id also (optionally) prints a new table field "locno":
88927 mode:
88940 __x86_64__ guard, making it unavailable when building in 32 bits mode.
89440 This value is only stable in all-stop mode. In non-stop mode, where
90336 configure:28573: ./libtool --quiet --mode=link gcc -o conftest \
90684 follow fork mode in child or parent and set detach on fork on
91178 me that while the commits fix the root cause, the failure mode is not great.
91252 out if the new PC is thumb mode or not.
91254 With no copy_insn_closure data, the logic to determine the thumb mode
91275 in C++ mode, this behavior is deprecated [-Wdeprecated]
91701 If the output stream is not a tty, batch mode is enabled, the screen is
93175 fix '@menu reference to nonexistent node `Hash tables''
93414 insns being accepted in Intel syntax mode even when "tbyte ptr" was
93854 see, so I don't believe I've changed the output layout at all. There
95011 mode. */
95790 occasionally useful to print things in C mode when working in a non-C
95887 * po/hu.po: Updated Hungarian translation.
96306 Regen ld/po/BLD-POTFILES.in
96673 gdb.base/cond-eval-mode.exp
97279 I noticed recently that se_rfmci, a VLE mode instruction, was being
97593 instruction depends on whether the processor is in VLE mode (some
97604 that the LSP insns are enabled only in VLE mode, which means the LSP
98726 When maintainer mode is enabled, it tries to rebuild sim/moxie/moxie-gdb.dtb
98733 when maintainer mode is enabled).
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.
99743 * README-maintainer-mode: Add a minimum version of dejagnu
99899 When using AArch64 GDB with the QEMU debugging stub (in user mode), we get
100081 mode the exact order of lines may not be preserved, just different
100095 mode the exact order of lines may not be preserved, just different
100678 Currently the -data-disassemble command takes a single 'mode' value,
100689 the mode value altogether?
100699 Additionally, I will make the mode optional, and default to mode 0 if
100700 no mode value is given. Mode 0 is the simplest, no source code, no
100701 opcodes disassembly mode.
100703 The two new options are only valid for mode 0, if they are used with
100704 any other mode then an error is thrown.
100712 display, that is mode 1 and 3.
100714 My hope is that new users of the MI will not use the mode at all, and
100716 Existing MI users can continue to use the mode, and will not need to
100734 -- @var{mode}
100739 non-optional '-- mode'.
100751 -- @var{mode}
100852 equivalent, but for RISC-V, using /b gets the old layout back (except
100958 Add tests for instruction with rounding mode. Change march
101007 covering the differences between the default and that disassembly mode.
101058 operand, to avoid emitting an operand size prefix in 16-bit mode. (Since
101926 prompt" mode, to know when the command's execution is complete. As some
101966 `wait_for` proc go in its "looking for the prompt" mode. However,
102394 layout, e.g.:
102396 (gdb) tui new-layout foo my window 1 cmd 1
102398 (gdb) tui new-layout foo "my window" 1 cmd 1
102400 (gdb) tui new-layout foo my\ window 1 cmd 1
102423 character '{' which has special meaning within a new layout?
102731 being built. This patch came from trying to avoid a maintainer-mode
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).
103109 to previous errors from layout, and don't try to write them.
104332 Commit 171fba11ab27 ("Make GDBserver abort on internal error in development mode")
104346 It also regenerates corresponding files with the maintainer mode.
104356 Maintainer mode: wrong gettext version?
104357 * README-maintainer-mode: Update minimum version of gettext
105119 and the rounding-mode (bits 5 to 7).
105127 This means that a user can change the floating-point rounding mode
105129 the rounding mode into frm.
105232 parts, FFLAGS (the flags) and FRM (the rounding mode). Both of these
105296 text 'dynamic rounding mode' for value 0x7. However, this is not
105299 A RISC-V instruction can either encode the rounding mode within the
105301 dynamic rounding mode.
105303 So, for the rounding-mode field of an _instruction_ the value 0x7
105304 indicates "dynamic round mode", the instruction should defer to the
105305 rounding mode held in the FRM field of the $fcsr.
105308 0x7 (dynamic rounding mode), and indeed, section 11.2, "Floating-Point
105311 _its_ round-mode set to dynamic, and the FRM field is also set to 0x7,
105315 be "INVALID[7] (Dynamic rounding mode)". We already use the text
105317 however, I think adding the extra "Dynamic round mode" hint might be
105644 Tested by building with gcc 12 in -std=c++11 and -std=c++17 mode, and
105645 clang in -std=c++17 mode (I did not test fully with clang in -std=c++11
105646 mode because there are other unrelated issues).
105791 we need a better failure mode than asserting.
105796 This makes the failure mode to accept the incomplete CU table, but to ignore
106812 …FAIL: gdb.mi/mi-break.exp: mi-mode=main: test_breakpoint_commands: breakpoint commands: check that…
106813 …FAIL: gdb.mi/mi-break.exp: mi-mode=separate: test_breakpoint_commands: breakpoint commands: check …
106881 yielding the intended "ambiguous operand size" diagnostic in Intel mode.
107779 whether a Q suffix is okay outside of 64-bit mode).
108459 * layout.cc (Layout::create_notes): Call create_package_metadata().
108461 * layout.h (Layout::create_package_metadata): New function.
109055 Without it in 16-bit mode a pointless operand size prefix would be
109856 which mode should be used for each piece of text. Back in
109927 invent yet another expression evaluation mode, leaving everything
110220 Its definition, layout, methods and functions
110506 in maintainer mode a run-time type check is performed.
110827 want the regular GCC layout instead using attribute gcc_struct.
111322 that, when compiled in developer mode, GDB will validate that the cast
111358 developer mode, a run-time check will be made to ensure that `base`
111962 In all-stop mode, when the target is itself in non-stop mode (like
112030 mode, with the target in non-stop mode. When a step finishes,
112037 However, since the target is in non-stop mode, keep_going resumes
112041 If the target is in non-stop mode, we don't actually need to stop all
112616 Add 'summary' mode to Value.format_string
112617 This adds a 'summary' mode to Value.format_string and to
112619 using this mode. For the latter, it lets a printer potentially detect
112623 I considered adding a new mode here to let a pretty-printer see
112837 (ppc_parse_name): Add mode param. Search both cr_cond and
113088 - Tweak the "replay" mode's description to describe replay first
113089 instead of recording, and also mention how the mode behaves during
113092 - Say what is the default mode.
114131 automake-1.16.5 then --enable-maintainer-mode builds will hit errors:
115054 template at the same time as Disp32. Unlike for non-64-bit mode,
115064 i386_finalize_displacement() entirely dead for AT&T mode, since for
115075 when dealing with 32-bit addressing mode in 64-bit code.
115947 Make GDBserver abort on internal error in development mode
115961 development mode, while keeping the status quo when in release mode.
115963 Thus, after this patch, in development mode, you get:
115971 while in release mode, you'll continue to get:
116019 unwinding is enabled, previous SP is set w/r to the current mode
116265 Note that I didn't touch */po/*.po{,t} on the assumption that these
116287 sizes. When -z relro, the relro layout does this by laying out
116291 usual forward layout of section is done and .got is more aligned than
116639 I considered using the Tcl implementation in serial mode, and the
116642 end, I settled on the script approach for serial mode too, which
116648 testing in parallel mode, if you look at the terminal after "make -jN
116865 external data symbols in -fpie mode.
117612 in --enable-64-bit-bfd mode:
118105 Allow 'interrupt -a' in all-stop mode
118106 PR gdb/17160 points out that "interrupt -a" errors in all-stop mode,
121964 - set follow-fork-mode child
122064 detach-on-fork off, follow-fork-mode child, infrun.c sets
122913 menu, like so:
123852 and alike") I neglected the need to omit the leading . in M68K/MRI mode.
125394 PASS: gdb.tui/scroll.exp: check cmd window in flip layout
125407 FAIL: gdb.tui/scroll.exp: check cmd window in flip layout
125478 (gdb) UNRESOLVED: gdb.mi/user-selected-context-sync.exp: mode=non-stop: \
125566 gdb: handle bracketed-paste-mode and EOF correctly
125601 fix for setting RL_STATE_EOF in callback mode
126189 -ex "set follow-fork-mode child" \
126285 remote target is working in all-stop / sync mode and is currently
126592 not happening. Instead GDB is just started in MI mode and there is no
127101 …(gdb) PASS: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
127106 …(gdb) PASS: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
127111 …(gdb) PASS: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
127114 …(gdb) FAIL: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
127703 mode switching during unwinding. It is enabled by default.
127711 that the backtrace is correct: SecureFault_Callback (Non-secure mode),
127713 SecureFault_Handler (Secure mode).
128105 This target is working in "remote all-stop" mode, and it is currently
128183 gdb: handle bracketed-paste-mode and EOF correctly
128200 gdb: work around prompt corruption caused by bracketed-paste-mode
128220 leave bracketed paste mode. You might then think that in the
128223 rl_deprep_terminal only prints the '\n' when bracketed paste mode is
128226 "quit" when bracketed paste mode is on, and "quit\n" when bracketed
128227 paste mode is off.
128245 readline, and they have bracketed paste mode on, then they will see
128307 gdb: work around prompt corruption caused by bracketed-paste-mode
128310 consequence of this work around is that, when bracketed paste mode is
128317 The ideal output, which is what we get when bracketed paste mode is
128891 mode.
128951 insns to have the (ignored) rounding mode specified individually rather
129041 …mbols, once the allocations have been done. Thus, the .loader section cannot be layout before that.
129559 - The prepare_to_access_memory machinery was added for non-stop mode.
130545 gdb also needs a mode where ada_decode can be instructed not to decode
131876 (gdb) layout src
132817 gdb: fix handling of vfork by multi-threaded program (follow-fork-mode=parent, detach-on-fork=on)
132823 This patch only deals about the follow-fork-mode=parent,
132882 target-non-stop on/off, follow-fork-mode parent/child, detach-on-fork
132884 scope to follow-fork-mode=parent, detach-on-fork=on. That's the
133551 use of --visualize-jumps, a basic 8-color mode ("color"), and an
133552 extended 8bit color mode ("extended-color").
133964 (gdb) layout src
133965 (gdb) layout split
133986 layout now looks like:
134015 (gdb) tui new-layout hsrc {-horizontal src 1 cmd 1} 1
134017 When this layout is selected with current master, gdb will leave a 4
134024 complete terminal height, and the layout is done correctly.
134026 This 4 line restriction is also what prevents this layout from working
134029 (gdb) tui new-layout conly cmd 1
134031 Previously, this layout would present a cmd window only, but there
134034 was fixed), but with this commit, the above layout now correctly fills
134048 layout, which we check.
134050 My main motivation was adding the initial window layout check, the
134056 gdb/tui: support placing the cmd window into a horizontal layout
134061 (gdb) tui new-layout hsrc { -horizontal src 1 cmd 1 } 1 status 1
134062 (gdb) tui layout hsrc
134081 The problem is some code in tui_layout_split::apply, in tui-layout.c.
134087 size when a layout is re-applied, or a new layout is applied. This
134088 makes sense, consider moving from the 'src' layout to the 'asm'
134089 layout, this looks something like this (status window removed):
134109 Now retaining the cmd window width makes no sense; the new layout has
134115 To solve this problem, I propose we introduce the idea of a layout
134117 where the cmd window lives within the layout.
134122 The fingerprint for a layout is represented as a string, the string is
134130 # This layout is equivalent to the builtin 'src' layout.
134132 tui new-layout example1 src 2 status 0 cmd 1
134134 # This layout is equivalent to the builtin 'split' layout.
134136 tui new-layout example2 src 1 asm 1 status 0 cmd 1
134138 # This is the same layout that was given at the top.
134140 tui new-layout hsrc { -horizontal src 1 cmd 1 } 1 status 1
134144 layout, and will retain the cmd window size.
134146 In contrast, when switching to the hsrc layout, gdb understands that
134154 function to reapply the layout, and recalculate all the window sizes.
134167 (gdb) layout src
134169 (gdb) layout split
134171 You should see that the status window is missing from the new layout,
134209 (gdb) tui new-layout conly cmd 1
134210 (gdb) layout conly
134216 This layout only contains a cmd window, which we would expect to
134236 sub-layout has a size calculated. As the size is an integer, then,
134260 each sub-layout within a layout) using integer arithmetic. As this
134264 Currently, this space is just assigned to an arbitrary sub-layout.
134270 (gdb) layout regs
134279 layout specification has these windows given equal weight. The
134290 (gdb) layout regs
134311 (gdb) layout src
134312 (gdb) tui new-layout conly cmd 1
134313 (gdb) layout conly
134330 There is still a problem after this commit, when the conly layout is
134338 gdb/tui/testsuite: refactor new-layout.exp test
134339 This commit changes the gdb.tui/new-layout.exp test to make use of a
134356 && m_splits[i - 1].layout->bottom_boxed_p ()
134357 && m_splits[i].layout->top_boxed_p ())
134360 After all, the apply might be laying out a horizontal layout, right?
134383 tui-layout.c.
134385 To help produce more useful debug output in tui-layout.c, I've added
134430 work right. I setup a horizontal layout, then grow and shrink the
134460 of a tui window (when in a horizontal layout). As a result, some of
134463 in a vertical, or horizontal layout.
134491 command name space, e.g. layout, focus, refresh, winheight.
134497 into the tui namespace, so 'layout' becomes 'tui layout', etc. But I
134499 e.g. I'll make 'layout' an alias for 'tui layout'.
134506 (gdb) help layout
134507 tui layout, layout
134508 Change the layout of windows.
134509 Usage: tui layout prev | next | LAYOUT-NAME
134511 List of tui layout subcommands:
134513 tui layout asm -- Apply the "asm" layout.
134514 tui layout next -- Apply the next TUI layout.
134515 tui layout prev -- Apply the previous TUI layout.
134516 tui layout regs -- Apply the TUI register layout.
134517 tui layout split -- Apply the "split" layout.
134518 tui layout src -- Apply the "src" layout.
134564 Regen bfd po/SRC-POTFILES.in
134938 Remove dbx mode
134939 This patch removes gdb's dbx mode. Regression tested on x86-64 Fedora
135267 gdb: test vfork + follow-fork-mode=parent + detach-on-fork=off
135744 gdb: work around prompt corruption caused by bracketed-paste-mode
135748 mode changed, an additional '\r' character was added to the end. In
135885 rounding mode: "Note FCVT.D.W[U] always produces an exact result and is
135886 unaffected by rounding mode." Hence the chosen encodings also ought to
136517 To compensate, in Intel syntax mode check_register() needs calling;
136573 At least x86-64's x32 sub-mode and RISC-V's 32-bit mode calculate
137260 x86: don't suppress overflow diagnostics in x32 mode
137261 Unlike in 64-bit mode, where values wrap at the 64-bit boundary anyway,
137920 * po/SRC-POTFILES.in: Regenerate.
137991 gdb: work around prompt corruption caused by bracketed-paste-mode
138014 This problem is a result of readline 8.1 enabling bracketed paste mode
138016 version of readline bracketed paste mode is off by default, so a user
138019 Bracketed paste mode is available in readline 7.0 too, but the bug
138023 mode. Bracketed paste mode is a terminal feature that is enabled and
138025 for GDB is that the escape sequence to disable bracketed paste mode
138032 disable bracketed paste mode was introduced between readline 7.0 and
138038 So, the escape sequence to disable bracketed paste mode is emitted
138046 escape sequence to leave bracketed paste mode. The final '\r'
138051 escape sequence to leave bracketed paste mode is emitted on the same
138066 has disabled bracketed paste mode (by calling rl_deprep_terminal).
138068 And so, when bracketed paste mode is in use, rl_deprep_terminal leaves
138107 after the prompt, but only when bracketed paste mode is on. This
138454 human-readable form without knowledge of the specific layout of the
138847 Fix bug in dwarf-mode.el
138848 I noticed that, occasionally, dwarf-mode would think that the objdump
138854 I've bumped the version number of dwarf-mode.el to make it easier to
138861 * dwarf-mode.el: Now 1.7.
140002 Deprecate dbx mode
140003 GDB has a dbx emulation mode that adds a few aliases and helper
140004 commands. This mode is barely documented and is very superficial
141550 NEWS: Note that the FreeBSD async target supports async mode.
141554 inf-ptrace: Add an event_pipe to be used for async mode in subclasses.
141568 Enable async mode in the target in attach_cmd.
141569 If the attach target supports async mode, enable it after the
141599 Synchronous mode still uses blocking waitpid() calls in
141603 Asynchronous mode registers an event pipe with the core as a file
141613 - Handle a race in async mode where SIGCHLD might signal the event
141629 mode even if async mode wasn't currently enabled. This change only
141630 permits TARGET_WNOHANG if async mode is enabled.
141634 Don't enable async mode at the end of target ::resume methods.
141635 Now that target_resume always enables async mode after target::resume
141640 this case, async mode should already be enabled when supported by the
141643 In general, targets which support async mode run as async until
141646 When that occurs, the loop in wait_one disables async mode. Later
141647 if a stopped child is resumed, async mode is re-enabled in
141652 target supports async mode, then an earlier call to do_target_resume
141654 record_full_wait_1 would have already enabled async mode before
141656 the loop in record_full_wait_1 disables async mode. Async mode is
141660 It is also true that async mode can be disabled by an
141665 Note that there is an earlier call to enable async mode in
141667 to report an existing event after enabling async mode, so it needs to
141672 Enable async mode on supported targets in target_resume.
141673 Enabling async mode above the target layer removes duplicate code in
141675 ("Multi-target support") enabled async mode in do_target_resume after
141678 async mode. Rather than enabling async mode in each of the callers
141679 after target_resume returns, enable async mode at the end of
142754 There are constraints on layout of binaries to meet demand paging and
142758 The linker's MAXPAGESIZE variable gives the page size for these layout
142809 fact, because the linker was starting layout using its simple
144324 (check_fpu): Select IEEE 754-2008 mode for R6.
144433 * mips.igen (check_fpu): Select default quiet NaN mode
145230 register maps to describe the layout of the general purpose registers
145412 the actual layout (so that building the stubs, which behaves like
147208 with VMOV{H,L}PD and VMOVDDUP, and only in AT&T mode, but not checked
147312 vs the old section layout:
147829 DT_RELR section size and tell ldelf_map_segments to layout sections
148027 argument to indicate if section layout needs update.
148550 sections after section layout has been finalized.
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.
149498 mode.
149885 While file layout absolutely must take 64K page size into account, that
150247 debugredirect: The logging output mode is off.
150250 redirect: The logging output mode is off.
150253 debugredirect: The logging output mode is off.
150256 redirect: The logging output mode is off.
150269 show logging debugredirect -- Show the logging debug output mode.
150273 show logging redirect -- Show the logging output mode.
150318 'for' loop initial declarations are only allowed in C99 mode
150353 the files whose mode is changed by the script, plus a build with
150354 --enable-maintainer-mode --enable-cgen-maint=yes, then checking
150355 out */po/*.pot which we don't update frequently.
151065 test is run multiple times; we run in the original mode, as normal,
151436 x86: -mfence-as-lock-add=yes doesn't work for 16-bit mode
151537 async mode disabled (with 'maint set target-async off'), but the async
151566 non-async mode, and in all-stop mode. Here's my GDB session showing
151602 replies. However, this code is not what we use due to non-stop mode
151685 for async-mode, and so, in remote_target::push_stop_reply, where we
151690 mode has been temporarily disabled, but, when async mode is switched
153347 Suppose we continue past a fork with "follow-fork-mode == child" &&
153417 (gdb) show follow-fork-mode
153430 - We are using the all-stop user-visible mode as well as the
153882 0 +-/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.tui/tui-layout.c--+
153895 0 +-/home/tdevries/gdb/src/gdb/testsuite/gdb.tui/tui-layout.c--------------+
153911 Line 20 of "tui-layout.c" starts at address 0x4004a7 <main> \
153917 Line 21 of "tui-layout.c" starts at address 0x4005f4 <main> \
154326 indexer's parallel mode.
154747 However, in 32-bit mode, there are only 8 xmm/ymm/zmm registers.
154760 values in 64-bit and 32-bit mode.
155226 (init_insn_sequence): Update for new aarch64_instr_sequence layout.
155228 (verify_constraints): Update for new aarch64_instr_sequence layout.
156963 * po/BLD-POTFILES.in: Regenerate.
156964 * po/SRC-POTFILES.in: Regenerate.
156969 * po/fr.po; Updated French translation.
157001 async mode disabled (with 'maint set target-async off'), but the async
157025 never have async mode enabled. Given this, it should not be necessary
157036 target can act in async mode or not. In previous commits I have moved
157048 2. GDB should never try to enable async mode for a target that
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.
158638 aarch64: [SME] Add SME mode selection and state access instructions
158639 This patch is adding new SME mode selection and state access instructions:
159334 logic to stuff the stack for user-mode programs, but that's it.
159814 A couple of files changed on my latest --enable-maintainer-mode
159976 * po/POTFILESin: Regenerate.
160512 in 'struct ui' in top.h, the main UI starts off in sync mode
160515 /* True if the UI is in async mode, false if in sync mode. If in
160516 sync mode, a synchronous execution command (e.g, "next") does not
160517 return until the command is finished. If in async mode, then
160953 When doing "continue -a" in non-stop mode, each thread is individually
161149 sim: sh: rework register layout with anonymous unions & structs
161151 to fix a long standing issue with the SH register layout. The use
161785 fast-build mode settings, so mark it unused too.
163188 * layout.cc (Layout::create_note): Set order to ORDER_PROPERTY_NOTE
163190 * layout.h (Output_section_order): Add ORDER_PROPERTY_NOTE.
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.
163825 tweaks to layout and replacing NULL with nullptr, hence, I've left the
164821 layout, please refer to [1].
165316 gdb.base/bt-on-error-and-warning.exp: problem=internal-error, mode=on: \
165900 The test-case uses non-stop mode, and when the exec-continue --all command is
167581 - The protocol between gdb and gdbserver is in non-stop mode, but the
167587 mode
167590 - At this point, the remote target is in target_async(0) mode, which
167675 …(gdb) FAIL: gdb.base/foll-fork.exp: follow-fork-mode=parent: detach-on-fork=off: cmd=next 2: test_…
168073 gdb: don't share aspace/pspace on fork with "detach-on-fork on" and "follow-fork-mode child"
168078 2. "set follow-fork-mode child"
168134 off" and "follow-fork-mode child", because we create new spaces for the
170803 but instead the disassembler uses thumb mode and only consumes 2
171605 thread is stopped as a consequence of GDB being in all stop mode, and
172367 --enable-maintainer-mode showed a number of files needing to be
172374 * po/BLD-POTFILES.in: Regenerate.
173477 sim: nltvals: switch output mode to a directory
173997 in non-mri mode.
174004 MRI mode generally doesn't flip lexer states, so let's make MRI mode
174057 (section): Parse within braces of section in wild mode, and
174058 after brace back in script mode. Remove ldlex_backup call.
174066 Enable filename match in SCRIPT mode. Enable WILDCHAR match
174067 in WILD state, disable in SCRIPT mode.
174652 layout, a warning gets issued if any of the new flavors was attempted
176721 The main problem is: when follow-fork-mode is "parent",
177478 Fix for gdb.tui/tui-layout-asm.exp
177490 * gdb.tui/tui-layout-asm.exp: Replace window width of 80 with the
178461 ensure script mode parsing for section name in SEGMENT_START.
178463 on a lookahead NAME parsed in expression mode.
178842 x86: correct EVEX.V' handling outside of 64-bit mode
178844 outside of 64-bit mode. Oddly enough there already are tests for these
178868 x86: correct VCVT{,U}SI2SD rounding mode handling
178869 With EVEX.W clear the instruction doesn't ignore the rounding mode, but
179512 - eZ80 (Z80 mode only)
180522 <enum class mode>: New.
180756 And ultimately that's used if the user-visible mode is all-stop, so that
181675 * po/gas.pot: Regenerate.
181682 * po/bfd.pot: Regenerate.