Lines Matching +refs:autoconf +refs:current +refs:defun
420 to be the current function name.
773 Since the current use-case of ginsn is to synthesize CFI, the x86 target
811 GAS, apart from the current use-case of synthesizing CFI for
915 prompts revisiting the current representations a bit.
1361 current GDB attributes start with a lower case letter, and I suspect
1819 the current inferior and current thread which where originally representing
1924 The HAVE_DECL_xxx defines are always defined to 0 or 1. The current
2168 Fix this by sampling the pc value for the current process in
2462 The following patch fixes that by using what autoconf uses in AC_CHECK_DECL
2592 with the correct versions (automake 1.15.1 and autoconf 2.69).
3179 None of that is relevant for us with current automake, so drop it.
3410 This brings us in sync with current set of gdb warnings (for C).
4087 Now let's debug it with target record, using current gdb git master
4266 will it attempt heuristics based on the current instruction.
4363 current kernel & OS settings, but the library APIs should. So move
4646 current GDB.
5679 to obtain the value type. This prevents them from using the current
5766 The plds Dz,MACL insn stores the Dz bit into MACL. The current code
5959 reflect the current state.
6473 current thread) that was incorrectly added by infrun.c. Because it
7356 current and entry values of the function arguments:
7783 pseudo registers to non-current frames for that architecture.
7793 reading pseudo registers in non-current frames on that architecture.
7803 writing pseudo registers to non-current frames on this architecture.
7840 fixes writing to pseudo registers in non-current frames for those
7859 The objective is to fix writing pseudo registers to non-current
7891 the current frame (frame 0).
7951 current frame to gdbarch_pseudo_register_read_value. Passing the
7952 current frame will give the same behavior as before: for frame 0, raw
7953 registers will be read from the current thread's regcache.
8090 the current {get,put}_frame_register_bytes). If a caller mis-calculates
8377 will acquire the GIL based on the current thread. I think this should
8560 When using $_thread in info threads to showonly the current thread,
8915 For the current assembler, the final value of `riscv_opts.relax' is false, so
9029 current sub architecture are put at the end of the table. This shaves another
9317 - the source for the current frame,
9772 The following patch fixes that by using what autoconf uses in AC_CHECK_DECL
10014 determine whether the current source tree is a dev build (e.g.
10600 there is not enough buffer left for the current register,
12674 srllh cannot be implemented using the current design, as they require
13989 doesn't appear to trigger for our current test suite.
14018 the current on-disk file. But, if the bfd cache is still holding open
14048 I see two problems with the current approach:
14133 leaves the current frame, GDB decides to refresh the step information,
14264 The current get_thread_arch_regcache function gets an address_space for
14278 the current get_thread_arch_regcache, which gets removed. So, I think
14283 about, or in last resort using the current global context.
14382 While implementing this, I discovered that the current code does not
14740 …lit baseargs into {h,b}baseargs. (skip_barg): New flag. Skips appending current flag to bbaseargs…
15060 the handlers for the current program space first, and then all of the
15104 debug information for this objfile. This matches the current
15430 - the new QThreadOptions packet and its current defined options,
15524 …[infrun] resume_1: step=1, signal=GDB_SIGNAL_0, trap_expected=1, current thread [1163850.1163850.0…
15789 The current thread <Thread ID 2> has terminated. See `help thread'.
16165 software breakpoint at this address, then the current behaviour is
16807 did not need a BTI. The stub groups are fixed in the current logic so
16983 mapped to an invalid number by the current PowerPC DWARF mapper.
17000 .debug_frame on other operating systems. The current GDB support for
17145 No symbol "hello" in current context.
17147 No symbol "hello" in current context.
17170 'hello.c':: but I guess this is a limitation of the current
18112 current working directory."), because directory 0 is correct. With the
18359 current code does, which is try to read an empty section but then do
18421 [1] https://www.gnu.org/software/autoconf-archive/ax_cxx_compile_stdcxx.html
18478 be zero like other SUB relocations. But the current LD will still get the right
18547 second thread selected as the current thread and asks GDB to detach.
18623 However, in our case, the current process has already exited, and so
19611 the current program space (that's what the solib implementations that
20621 This function is just a wrapper around the current inferior's gdbarch.
20638 set_target_gdbarch is basically a setter for the current inferior's
20652 and that the callbacks should not assume it is the current inferior.
20867 the section of the current branch, now that it has been cut.
21472 current code clearer.
21511 relies on the current program space, so I didn't add a parameter to that
21653 for the current inferior.
21656 delete_inferior -> ~program_space path, we see that the current
21661 the case if the current inferior isn't within the program_space to
21666 can't rely on the current inferior having any relationship with the
21669 current program space. As a result of this mistake, after commit
21752 current inferior would, in theory, still be using the current
22363 the case that the current frame has a set of vector lengths (A) but the signal
22378 frame will always have the same gdbarch as the current frame.
22531 otherwise they may have a size bigger than 16 bytes (depending on the current
22559 Where the current code makes use of unique_ptr, allocating a new buffer by
23581 actually corresponds to a change in the current executable.
23614 requires my to think about the current users of this observable.
23616 One current user of executable_changed is in symtab.c. We add an
24902 Make the current situation explicit by emitting a dwarf error:
24980 A user pointed out that the current DAP variable code does not let the
25310 The current code returns different TLS_TBSS values for .tdata and
26469 No definition of "red" in current context.^M
26625 cleanup, since the current token is a fundamentally per-interp thing.
26628 mi_cmd_gdb_exit: when invoked from Python's gdb.execute_mi, the current
26745 No definition of "rgb_color" in current context.^M
26949 rather than the current language.
27645 current patch is mostly his work, though I did make some adjustments
27735 from current trunk, but the pathname to the build dir changed and I forgot to
27742 No symbol "ZERO" in current context.^M
28517 gdb: Support XSAVE layouts for the current host in the Linux x86 targets.
28540 gdb: Support XSAVE layouts for the current host in the FreeBSD x86 targets.
28596 This structure is fetched from the current target in i386_gdbarch_init
28622 To date, GDB has assumed the layout used on current Intel processors
28787 most of current LE ELF files are using EM_MIPS.
29076 This matches the current set of system calls at the start of the
29268 by reversing from the current location and checking all registers for
29342 be slightly changed to work with empty "current locations", so that we
29808 Instead of the current equivalent:
30885 of files and regen with our standard automake/autoconf.
31268 an exec as well as the current exit. Exec and exit are the two ways
31394 proceed_resume_thread_checked just once, for the current thread,
31447 the current selected thread, this is not a vfork-parent, and so
31529 Solution is to limit the search to the current program space.
31535 current thread's location -- if a user is asking the current thread to
31537 current thread is located.
31540 decode_line_1 is updated to pass through the current program_space,
31541 which will limit the returned locations to those in the current
31772 current inferior's process for a wildcard ptid. If a resumed process
31935 Print dump of current symbol definitions.
31947 Print dump of current partial symbol definitions.
32041 AFAIU the current code in symtab_index_entry::minimize makes the assumption
32048 In other words, the current approach breaks feature parity between cooked
32528 since the buggy toolchain cannot bootstrap current GCC sources
32655 is not given in the configure line. To cater for this we pass the current
33375 When testing current gdb trunk on Solaris/amd64, the whole session was
35337 make sure that amd_dbgapi_target::wait only pulls events for the current
36936 group name matches current group for section.
37070 objcopy embeds the current time and ignores SOURCE_DATE_EPOCH making the output unreproducible.
37527 @defun. This patch removes all such uses from python.texi, plus a
37745 No symbol "aaa" in current context.
37783 No symbol "aaa" in current context.^M
37900 In the current code, when a register is fetched, the entire regset
39026 the current line or that a list command was used at all, making GDB's
39043 stopped. The current best options require either using a separate
40082 enable direct addressing of current and future large memories, as well
40206 /* Resume execution (or prepare for execution) of the current thread
40208 current process or all processes run free.
40499 The current thread has terminated
40504 The current thread <Thread ID 1> has terminated. See `help thread'.
40542 The current thread has terminated
40546 which should be the current thread. The above message is reported
40547 because GDB has deleted what we think is the current thread!
40687 This change was rejected by the kernel team, the current
40769 The current thread has terminated
40775 second, the "The current thread has terminated" message. This is
40776 because the first thread in the core file is the current thread, but
40779 current (first) thread has terminated.
40803 current thread (which there will not be if no ".reg/NN" section was
40804 found), then we look for a thread in the current inferior. If there
40806 then we once again setup the current inferior.
40808 What I think this means, is that, in all cases, the current inferior
41622 decimal or hexadecimal notation), but at least let's stop the current
41802 In other words, like the rest of the binutils, only the current SFrame
42502 In libtool-version, set the current to 1 to prepare for the upcoming
43933 `sizeof(int)` evaluates to for the current target.
44725 string value will be represented just as it would be in the current
44824 In the current implementation, core_target::build_file_mappings will try
45385 Consider this example using current GDB:
45841 Print the current targets section list. This is a sub-set of all
46415 I chose this approach because the current implementation doesn't place
46702 need to deal with the current interpreter (the "this" pointer).
46711 understand than the current solution that uses observers. We are sure
46948 current arm-wince-pe. arm-pe has different relocations and uses
47819 solution in this commit is to select the location in the current symtab.
47989 clear_current_line overwrites the current line with chars_per_line
48207 taken into account, but not when comparing to the current value of
48781 In the current code, when execute the following test on LoongArch:
49321 The current API relies on returning a DisassemblerResult object to
49495 the number to go over the current maximum. This bumps the number.
50188 much space as is needed for the line numbers in the current file, and
50285 possibly deleting the current breakpoint as well as related breakpoints.
50804 much simpler than the current approach.
50920 consider the current behaviour to be a bug.
50922 1. If the current behaviour is a bug, then we can update the behaviour
50931 2. If the current behaviour is not a bug, then we can add a new option
50941 This patch implements solution (1) as I think the current behaviour of
51665 breakpoints for non-existent threads. This would preserve the current
51734 current inferior from a set callback, move to the API that allows for
51735 getters and setters, and store the value directly within the current
51749 current inferior from a set callback, move to the API that allows for
51750 getters and setters, and store the value directly within the current
51770 responsible for copying the scratch area into the current inferior.
51774 straight into the current inferior.
51776 There is a second problem, when the current inferior changes the
51784 value returned will now always reflect the current inferior.
51958 Remove @var from @defun in Python documentation
51959 Eli pointed out that @var isn't needed in @defun in Texinfo. This
52316 then we should be checking for it, the current gdb_test doesn't do
52317 that. But also, with the current gdb_test, if a blank line suddenly
52767 input_radix. Note that the current code may fail to restore it on
53466 language automatically". But "auto" is never the current language. The
53467 `current_language` points to the current effective language, and the
54167 of the current mapping symbol.
54228 The current implementation of the interposed functions is:
54232 In the test from PR 30360, pthread_create@GLIBC_2.0 is not in the current libC.
54367 This will try to get the thread's register by calling into the current target
54402 sequence of events would happen, if it was not for the current patch.
54404 - we start with inferior 1 as current
54405 - do_target_wait_1 makes inferior 2 current, does a target_wait, which
54408 current
54411 target of inferior 2. This makes inferior 1 the current inferior, as
54420 regcache_read_pc executes while inferior 1 is still the current one
54492 inferior is the current one. Return an instantiated
54509 as well just get it from the current target stack. This simplifies a
54547 With the current observable signature, the observers only receive the
54690 Maybe the real answer is to use a better editor, or fix my current
54747 In the current code, when execute the following test on LoongArch:
55901 This commit aims to address a problem that exists with the current
55906 with the current approach which will impact amd64 and ARM, and can
55917 called, which has the job of fixing up the state of the current
56065 seems to run into "debug_name_type: no current file" or similar
56350 thread-specific for the current inferior_thread().
56357 the current inferior_thread(), so we know that the thread being passed
56512 current location. The second time is a little odd, why do we print
56764 the frame-pointer, as such GDB's (current) preference for using the
56774 instructions at the current $pc looking for this pattern:
56849 really does go from the start of the function right up to the current
57310 symbol when the language of the current frame is Fortran.
58620 for the current location within the pending frame, or None.
58622 - gdb.PendingFrame.block: Return a gdb.Block for the current
58625 - gdb.PendingFrame.function: Return a gdb.Symbol for the current
58865 But anyway, I just sync the current behavior as aarch64 ld, in case
59333 There is some notion of current gdb, tracked in both gdb_spawn_id and fileid
59336 host, and consequently the current gdb.
59746 host, because the current implementation of gdb_ensure_index doesn't support it.
60142 member of the current struct as necessary.
60303 current thread. This means a call to inferior_thread () will assert, and
60346 will also have no current thread (inferior_thread () will assert etc).
60353 thread/current regcache because gdb is in the middle of doing event handling
60357 opposed to relying on the current register cache. Though we need to make sure
60630 I believe I've manually checked all the current places where
61379 for recreating the current breakpoints. The CLI does not use global
62203 frame-id was being built (using the current stack point and program
64162 properly after rebasing and before pushing, we get this with the current
64594 Since the current code does what we want, and I don't see any way of doing it
65194 The setting is off by default, preserving current behaviour.
65200 the most detailed info is found. This explains the current reading order of
65581 …x7ffff7c5eb80 (LWP 987035)",name="thread-bp-delet",state="running",core="4"}],current-thread-id="1"
65758 based on the current UI mode.
66121 current behavior in which GDB exits upon receipt of a SIGTERM.
66322 current thread, GDB aborts the execution command, presenting the stop
66337 1 is not the current thread, GDB aborts the execution command,
66365 …[infrun] resume_1: step=0, signal=GDB_SIGNAL_0, trap_expected=0, current thread [1722839.1722839.0…
66386 a) if the current thread is the one that forked, gdb follows the
66389 b) if the current thread is some other thread (because you switched
66484 the thread that last reported a stop, not the current thread:
66494 The current code already behaves this way, though in a poor way. This
66569 the current target, which was incorrect. Two different targets may
66883 the new version is ASCII sorted, while the current version was
67251 You can see the current master's table for Linux x86-64 here:
67765 but it shows the information of all registers in the current code,
68104 ".file Line.s" are identical and thus gas won't change the current
68385 For amd64 the current frame-unwinders are:
68739 attempt lazily computing the current language. Perhaps this approach
68780 the tdesc_info of the current inferior, the above commit stopped this
68825 So we replaced the call by only switching inferior_ptid, the current
68826 inferior, and the current address space (like proc-service.c).
68842 processes. Now we only use he GDB threads of the current
68847 true for the current inferior.
69208 Here is the current default quit_handler, a function that ends up
69611 the frame stash. That is when we create the frame_info for the current
70968 When the current language is C++, and the user places a breakpoint on
71233 updated the patch to current testsuite standards.
71354 user's current directory when debugging GDB.
71544 Consider this GDB session with the current GDB:
71603 current debuggee memory contents outside the original data accessed,
71766 No line 63 in the current file.
71776 "current source file".
71779 of debug info, the "current source file" becomes glibc's ./setjmp/longjmp.c.
71786 glibc-32bit-debuginfo package. This allowed me to confirm the "current source
71867 reflect current roles of each relaxation pass.
72007 (dwarf-refresh-all): New defun.
72695 of the current output:
73023 The current PRU default linker script may output a segment size not
74338 will configure the current target (if available). If no target is
74340 adapted. The show command will display the current remote target's
74349 for the current inferior. To fix this, the clean_restart command is
74404 warning: Range stepping is not supported by the current target
74408 warning: Range stepping is not supported by the current target
74425 warning: Range stepping is not supported by the current target
74444 command line configuration affected current targets and future remote
74450 current connection. All other existing remote targets are not
74456 The show command displays the current remote target's configuration. If no
74680 is larger than the current window size - which seems a reasonable
74830 the name matches multiple windows in the current layout.
74832 It is worth noting that the ambiguity must be within the current
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
74835 ambiguous, and focus will shift to the matching window in the current
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).
75790 ncurses pad in order to hold the current page of disassembler output.
76099 Currently, that happens to be not the case due to the current implementation
76231 current target frame (for frame 0) or frame_find_by_id (for other
76273 frames are not the fruit of unwinding from the target's current frame.
76324 This second "frame" command shows the current target frame instead of
76370 -1), lookup_selected_frame just reselects the target's current frame,
76378 target's current frame. User-created frames also have level 0, so add a
76875 the current setting of the `set/show print characters' option.
77720 We aren't affected by that bug with the current code, but as we move
78375 So change gdbarch.py to generate the current version of gdbarch.c.
79738 No line 1 in the current file.^M
80135 Don't let property evaluation affect the current language
80137 change the current language, because gdb would select the call dummy
80140 This patch changes gdb so that the current language is never affected
80185 instead, this patch adds a new method that falls back to the current
80304 to track whether to enable the sim. While the current code works
81021 displays the DWARF5 entry 0 for the program current directory rather
81198 for DWARF5 where index zero is allowed and is the current directory of
81201 of putting the current dir in .debug_line was so the section could
81743 multi-keyword will possible be a single extension for the current parser.
82120 * Regenerated using unmodified autoconf-2.69
82158 gdb/c++: validate 'using' directives based on the current line
82180 current scope, we assume it is valid.
82645 the section of the current branch, now that it has been cut.
82921 No symbol "some_label" in current context.
82923 No symbol "some_label" in current context.
82925 No symbol "some_label" in current context.
82929 In all cases, some_label is a goto label within the current frame.
83339 Right now, closing a target, in some cases, depends on the current
83679 not just the current language (C in this case), so, when GDB
83770 The current AS accepts invalid operands due to miss of operands length check.
84675 3-bits are unused). So the current implementation works without this patch.
86412 and we could use the fact that the current pc is in the 1000067c-10000680
86765 Actually set m_is_async to current async mode
87150 can only change due to the current thread’s activity (and if you are also
87151 confident that no other thread can become current), then you can use software
87152 watchpoints as usual. However, GDB may not notice when a non-current thread’s
87404 The reason is a wrong current process when find_one_thread is called.
87405 The current process is the 2nd one, which was just attached. It does
87411 `current_process ()->priv->thread_db`, assuming the current process
87415 Fix this by making find_one_thread not assume what the current process /
87416 current thread is. If it needs to call into libthread_db, which we know
87417 will try to read memory from the current process, then temporarily set
87418 the current process.
88632 The test py-objfile.exp unloads the current file while debugging the process.
88950 with a current process but no current thread. This tripped on ps_getpid
88952 `current_process ()` instead, which removes the need to have a current
88954 gdb_ps_prochandle_t structure, to avoid the need for a current process
89367 The current output from the test:
89374 …Run till exit from #0 return_large_struct () at binutils-gdb-current/gdb/testsuite/gdb.base/retva…
89375 …main (argc=1, argv=0x7fffffffcd58) at binutils-gdb-current/gdb/testsuite/gdb.base/retval-large-str…
89379 testcase binutils-gdb-current/gdb/testsuite/gdb.base/retval-large-struct.exp completed in 1 seconds
89436 the number of live (non-exited) threads in the current inferior. This
89785 gdb: add "set style tui-current-position on|off", default to off
89791 text highlighted by the TUI's current position indicator, and adds a
90281 backtracing. The current version supports AMD64 and AARCH64.
90321 AC_LINK_IFELSE autoconf macro in order to link a simple program to
90326 for them with an autoconf macro resulting in an addition to LIBS.
91136 the current language. If this was meant to be permanent, I would
91749 that frame to reinflate it. We should instead just re-fetch the current
91764 get_current_frame to get the target's current frame. Otherwise, use
91961 if the function was printed using a C++ style mangled name. The current
91962 patch fixes this by allowing for mangled names along with the current
92198 PR exp/28359 points out that 'ptype/o' does not work when the current
92739 file, using vanilla autoconf-2.69 and automake-1.15.1. I noticed
93082 an uninitialized variable usage, based on the current usage of the
93225 assuming that the current bfd cannot load it (since a basic cris
93297 Clang up to version 15 (current) adds macros that were defined in the
93307 for all current versions of Clang. The workaround detects when
93376 add more host flags to CPPFLAGS, and that conflicts with our current
94504 description comment based on current spec. Limit instruction
94599 (riscv_remove_mapping_symbol): If current and previous mapping symbol have
94600 same value, then remove the current $x only if the previous is $x+arch;
94613 * config/tc-riscv.h (riscv_segment_info_type): Record current $x+arch mapping
95134 The current logic limits itself to a maxdepth of 4 when looking for
95853 current frame-id to the breakpoint.
95872 ideally have the current function's frame_id to avoid other problems
96493 files in GDB's current directory, specifically, the two source files:
96517 tests within the block. After running the tests the previous current
97340 Setting SP of the next frame to the same address as the current frame
97742 current approach is to do the compilation hoping for the best, and if we find
97808 privileged architecture requires the 'Zicsr' extension. However, current
98393 reads from the current inferior's target stack (it looks just like a
98420 current inferior. The latter is for convenience, to avoid making
98433 target_auxv_search overload that works in the current inferior.
99410 the current frame. See "Lazy context save of FP state", in B1.5.7,
100127 than the current 'Illegal Argument' error message.
100277 The intention of the current code is that, should the Pygments package
100345 not available on the current architecture then these new tests will be
100562 available on the current target. Indeed, there are plenty of places
100601 registers that are not supported on the current target, and that
100641 There is one slight oddity with the current implementation, which I
100645 The current implementation uses this pattern:
101034 destination register) it is easy to see that current behavior is far
101472 it with the autoconf $EGREP or with grep.
101648 build, the command takes just a bit more than the current timeout of 10
101731 that contain non-trivial autoconf macros, because autoconf will emit
101732 any AC_REQUIREd autoconf macro expansions outside of the conditional.
104283 accessible for every vector subsets), current minimum vector subset 'Zve32x'
106727 ___lc_codepage_func was introduced to determine the current encoding.
107667 The current implementation of the fcc register is referenced to the
107729 therefore the current thread is null.
107732 be in the correct current thread that has caused an event of new
108353 current simple checks. Fix that, and use the same check in other
109043 - replacing the current implementation of the warning with an
109293 will be tested no matter what the current target compiler is for a given
109395 No symbol "ZERO" in current context.
109692 current source file as "/dir/d/dw2-compdir-oldgcc42.S". If you compile
109728 about an invalid index to the sole current caller of file_file_name,
110697 "python dont-write-bytecode". The current doc was just a copy
111391 current inferior is updated based on the architecture of the
111409 The problem here is that the ARCH in this line comes from the current
111463 The problem is that performing these actions requires that the current
111520 be current. As a result, all of the checks in arm_pc_is_thumb would
111521 fail (they rely on reading symbols from the current program space),
111523 arm_frame_is_thumb. However, remember, at this point the current
111524 inferior is the AArch64 inferior, so the current frame is an AArch64
111538 arm_frame_is_thumb, as the current inferior should now be the ARM
111539 inferior, the current frame should be an ARM frame, so we still should
111565 example above, on an x86-64 native target, the current target
111571 I also think the current output is a little confusing, we appear to
111591 Zeroing of upper 32 bits of 64-bit addresses is "auto" (current architecture is not MIPS).
111593 The 'current architecture is not MIPS' text is only displayed when the
111594 current architecture is not MIPS. If the architecture is mips then we
111617 The problem with the current code is that the functions in question
111619 parameters are available no matter the current architecture, but are
111634 the current architecture is ARM, otherwise the result will actually be
112038 _only_ the current thread. All the other threads remain stopped,
112294 Make GDB change its current directory to the output dir just before
112505 Since commit c4a3dbaf113 ("Expose current 'print' settings to Python") we
112629 Expose current 'print' settings to Python
112630 PR python/17291 asks for access to the current print options. While I
112638 Second, there is no good way to examine the current settings (in
112871 The current thread <Thread ID 1> has terminated. See `help thread'.
112889 …/../binutils-gdb-current/gdb/testsuite/gdb.base/stap-probe.c:107:1: error: expected '=', ',', ';',…
112935 /.../binutils-gdb-current/gdb/testsuite/gdb.base/step-indirect-call-thunk.c
114126 Until we update the recommended versions of autoconf/automake, files
114127 should be regenerated with automake-1.15.1 and autoconf-2.69. That's
114524 I've noticed this because current llvm-dwarfdump crashed on an
115657 current thread codepage.
116019 unwinding is enabled, previous SP is set w/r to the current mode
116395 cooked_indexer::index_dies incorrect computes the end of the current
116512 such that core files are dumped in the current directory instead of
116777 Let's show the current stub as well as the previous one. Of interest
116778 is the current offset and a new field, id. Check that the build
116787 Show current stub as well as previous.
116907 According to the picture 28.1 in the current ISA spec, h is no larger the
116950 This commit adds 'H' to canonical extension ordering based on current
116957 canonical extension ordering based on current consensus.
118249 testcase with current git Clang. This testcase is also updated to
118315 * dwarf2dbg.c (dirs, dirs_in_use, dirs_allocated, current): Don't
118675 The current PowerPC values for TCGETS, TCSETS, TCSETSW and TCSETSF are
118728 But given the current true/false definitions have been in place since
119574 then fall back to the current approach if it fails.
119849 The current implementation of parse_number contains a comment about PR16377,
119861 The current implementation of parse_number contains a comment about PR16377,
120134 complicates things by trying to set the current osabi.
120360 Implement the software_single_step gdbarch method to decode the current
120525 the current language without (1) ever having the value "auto" or (2)
120850 No symbol "mod_1" in current context.
120896 No symbol "typeinfo" in current context.
120913 No symbol "bad_key_err" in current context.
121174 figure out the current compiler version via the 'getting_compiler_info'
121343 The current "Specify Location" section of the GDB manual starts with:
122143 current machine, "maint space 1" reports no change due to the patch.
122361 Thus, this patch preserves the current behavior, and, instead, adds a
123404 The current assembler accepts system registers FPCXTNS and FPCXTS for Armv8.1-M
124008 "No symbol \"scope0.c\" in current context.*" \
124059 current code does not try to prevent it, causing UBSan to complain.
124113 While at it, make use_poll be a bool. The current code is using
124302 from gcc. Remove current uses in gdb.
124710 Fix "b f(std::string)" when current language is C
124712 f(std::string)", and the current language is C, the breakpoint fails
124765 print a type in a given language, avoiding a dependency on the current
124770 does not. The one that does not uses the current language, defeating
124783 current language, just like today. Can always be improved later.
125325 The current glibc on Tumbleweed is 2.35, which contains commit
125361 The current glibc on Tumbleweed is 2.35, which contains commit
125894 errors out if the current inferior has a process_stratum_target pushed.
125897 current inferior (the current one upon entering the function).
126070 current thread's register cache, and the current thread pointer
126073 In #3, the current thread is nullptr because gdb_read_memory clears it
126075 the current thread when it shouldn't. It was always possible to end
126076 up in this situation (when the current thread exits), but it was
126079 This commit fixes it by tweaking is_64bit_tdesc to look at the current
126080 process's tdesc instead of the current thread's tdesc.
126240 …[infrun] resume_1: step=0, signal=GDB_SIGNAL_0, trap_expected=0, current thread [965604.965604.0] …
126261 …[infrun] resume_1: step=0, signal=GDB_SIGNAL_0, trap_expected=0, current thread [965604.965604.0] …
126296 space is the current program space). Inferior 2 isn't bound to any
126304 but our current inferior is not running, we should not invite the
126306 (unrelated) current process. */
126310 The problem here is that while inferior 2's program space is the current
126311 program space, inferior 1 is the current inferior. So the check above
126319 consider the current inferior at all, but instead all inferiors bound to
126320 the affected program space. Especially since the current inferior can
126321 be unrelated to the current program space at that point.
126324 the current program space, but there is no more inferior having that
126330 ensure that the current inferior has execution before calling it.
126425 gdbserver: track current process as well as current thread
126452 Fix this by making GDBserver track the current process separately,
126454 similar to set_desired_thread, but just sets the current process,
126455 leaving the current thread as NULL. Use it in the GDB-facing memory
127151 …[infrun] resume_1: step=0, signal=GDB_SIGNAL_0, trap_expected=0, current thread [637627.637627.0] …
127191 stayed the current inferior, which should have prevented it from getting
127193 prune_inferiors call, the current inferior is inferior 1. Further
127195 clean_up_just_stopped_threads_fsms, the current inferior is inferior 2,
127204 this, "info threads" says "The current thread <Thread
127212 So in the end, inferior 1 stays current, and inferior 2 gets wrongfully
127216 actually attempts to restore the event_thread to be current at the end,
127217 after the loop (I presume the current thread on entry is always supposed
127219 and ecs->event_thread is not set, so the current inferior isn't
127222 Fix that by using scoped_restore_current_thread. If there is no current
127223 thread, scoped_restore_current_thread will still restore the current
127241 The current target_resume interface is a bit odd & non-intuitive.
127253 Because GDB always switches the current thread to "leader" thread
127930 user that the current ehaviour of creating an executable stack
128421 current inferior.
129324 regardless of what is the current source file.
129449 The current nightly Rust compiler (aka 1.61) added better DWARF
129453 this. I tested this against various Rust compilers: 1.48, current
129454 stable, current beta, and current nightly.
129581 ... teach GDBserver to access memory even when the current thread is
130136 then assign the result to the current subfile, obtained with
130137 get_current_subfile. I assume that the current subfile is also the
130467 different way. The current reader reads and stores all the DIEs that
131891 displayed, it's current register group is nullptr. As a consequence
131897 current register group is nullptr.
131911 be unique. The current command logic goes:
132558 current PC is at the beginning of a line. So depending on where thread
132575 When testing this, Tom de Vries pointed out that the current test code
132626 …[infrun] resume_1: step=1, signal=GDB_SIGNAL_0, trap_expected=0, current thread [4154304.4154304.0…
132642 …[infrun] resume_1: step=0, signal=GDB_SIGNAL_0, trap_expected=0, current thread [4154304.4154310.0…
133052 current skip_prologue_using_sal works, this commit modifies it to accept
133134 parameter to record_line for each possible flag, transform the current
133255 The clients still have a global for the current process. That is,
133561 must provide two functions, the current non-styled print function, and
134017 When this layout is selected with current master, gdb will leave a 4
134059 by 24 lines terminal, using current master gdb:
134086 This special case is trying to have the cmd window retain its current
134267 steps with current master:
134315 After this, with current master, gdb crashes with a floating-point
134780 name current-thread.c
134784 … { symtab /home/simark/src/babeltrace/src/lib/current-thread.c ((struct symtab *) 0x6210002955e0)
134857 the current uses. Something seems odd with this use of
134963 is the current inferior. The vfork-done event we receive could be for
134964 any inferior. If the vfork-done event is for a non-current inferior, we
135025 …[infrun] resume_1: step=0, signal=GDB_SIGNAL_0, trap_expected=0, current thread [713933.713933.0] …
135322 characters, shifting all the rest of the line right. The current
136550 directory table contains the current... ") added a "dwarf_level < 5"
136840 The gdb.format_address by default selects SYMBOL from the current
136842 architecture for the current inferior. However, a user can also
136976 watchpoint_triggered is only current called in the handle_signal_stop
137029 I notice this happening on a current Fedora Rawhide install with the
137284 mechanisms to trigger this crash in the current test, using the commands
137291 mentioned functions save a pointer to the current frame's information,
137294 call_function_by_hand needs to reset the obstack to get the current
137402 the section of the current branch, now that it has been cut.
138192 Cannot find bounds of current function
138229 Cannot find bounds of current function
138851 is not guaranteed to be run with the current buffer set to the process
139427 In summary, the current zombie leader detection code in linux-low.cc
139449 The current zombie leader detection code in linux-nat.c has a race --
139559 Fix gdb.threads/current-lwp-dead.exp race
139562 gdb.threads/current-lwp-dead.exp starts failing:
139565 …edro/rocm/gdb/build/gdb/testsuite/../../../src/gdb/testsuite/gdb.threads/current-lwp-dead.c, line …
139570 …(gdb) FAIL: gdb.threads/current-lwp-dead.exp: continue to breakpoint: fn_return (the program exite…
139586 current thread as pointed by inferior_ptid was gone when infrun got
139606 gdb.threads/current-lwp-dead.exp starts failing:
139956 now uses the same connection as the current inferior, this commit adds
139991 inherit a copy of the target stack from the current inferior.
139998 inherit a copy of the target stack from the current inferior.
140330 current hashmap based substitution mechanism always compares the target
140679 In the current code, there is no test result when execute the following
141424 Currently we report errors as "invalid CSR 'fscr' for the current ISA"
141429 'fscr' for the current ISA, CSR 'fscr' needs 'f' extension".
141715 output to AC_LINK_IFELSE. However, as the current language is C++,
141956 current version of Darwin (Big Sur) demonstrate that gdb runs just fine
142370 New defun.
142912 No symbol "nml" in current context.
142930 loop if the current instruction is the last one related to that loop.
142961 current line table entry, that is 0x10c in our example. GDB then
143938 method of compunit_symtab. The name filetabs conflicts with the current
143945 Adjust the COMPUNIT_FILETABS macro to keep its current behavior of
144418 This patch replaces the macro with a variable to track the current
144746 This test passes on current gdb, but with my modified (and broken)
144819 This will place a breakpoint at the current location with the
145176 on offset used in the current iteration, and if we're fudging the
145656 So, based on this, the current use of data_section_offset /
145938 Set the current value of 'param-none'.
145944 Set the current value of 'param-doc'.
145979 set print param-none -- Set the current value of 'print param-none'.
145991 show_doc string to create a sentence that would display the current
145996 by displaying the show_doc string with the current value appended, see
146009 The current value of 'param-none' is "off".
146128 current language is no longer captured by the Python layer, it seems
146181 Currently, gdb's Python layer captures the current architecture and
146195 Python code cannot affect the current language for its own purposes.
146199 ... stuff using the current language
146205 This patch changes gdb to try to avoid capturing the current values.
146206 The Python concept of the current gdbarch is only set in those few
146209 required, the current language is temporarily changed.
146316 by Simon in d0ac1c44885daf68f631befa37e ("Bump to autoconf 2.69 and
146322 ("Bump to autoconf 2.69 and automake 1.15.1"). So delete it here.
146453 Regenerate configure files with autoconf 2.69
146454 Regenerate configure files with the unmodified autoconf 2.69 to remove
146662 if the skipped element is the last one in the current dimension we need
146684 Amend existing test cases accordingly that rely on the current incorrect
146921 In the current code, if decimal floating point is not supported for
147732 2. The test attempts to find the PID of the current thread, but the
147736 3. The test uses "info threads" to find the current thread PID.
148106 So, given the current code does the work of reloading the offset data
148910 The current approach is that in such situation, the input and expected
149287 Finally, our current style for keyword arguments, appears to be:
149395 the streaming vector length instead of the current vector length.
149853 This scenario isn't covered by the current test suite, so this patch
150248 file: The current logfile is "gdb.txt".
150254 file: The current logfile is "gdb.txt".
150270 show logging file -- Show the current logfile.
150283 logging file: The current logfile is "gdb.txt".
151829 Note that some info (like "staticdefault") in the current code is
152548 We use the two linker scripts, to test the current medlow and medany behaviors
152550 Besides, these testcases also show the limits of the current medlow and medany
152556 behaviors of the current medlow and medany code models.
152725 Introduce a class for restoring the current thread and a function to
153332 it should be fixed, but I would like to handle that later. The current
153563 immutable when other types defined in GDB are not. This current
155567 To avoid this, and to leave things as close to the current behaviour
155604 the istarget. The current if / else statement does not check for
156124 For the current dis-assembler, we get the result,
156339 tests can be run rather the current configure target. This allows
157125 The current logfile is "gdb.txt".
157128 The current logfile is "gdb.txt".
159673 entry 0 of the directory table in DWARF 5, which represents the "current
159677 file table, which represents the "current compilation file". But the latter
159685 .file 0 "/current/directory" "/full/path/test.c"
159691 0 (indirect line string, offset: 0x25): /current/directory
159778 The current linker heuristic of only generating power10 instructions
159826 Fix build with current GCC: EL_EXPLICIT(location) always non-NULL
159827 Compiling GDB with current GCC (1b4a63593b) runs into this:
160159 For the current objdump, we dump data to .byte/.short/.word/.dword, and
160648 This relatively short backtrace is due to the current UI's async field
160901 Then with the current interface nothinng prevents this usage of
161047 complete insofar as it goes: it documents format v3 (the current
161350 would want to support current kernels until such a fix is more wide
161515 I get some diffs when running autoconf in gdbserver, probably leftovers
161702 The current register set selection mechanism for AArch64 is static, based
162190 current gdb as well.
162245 The current system maintains a list of target errno constants in the
162430 argument. 'on' enables debuginfod for the current session. 'off'
162431 disables debuginfod for the current session. 'ask' will prompt
162774 …[infrun] resume_1: step=1, signal=GDB_SIGNAL_0, trap_expected=0, current thread [Thread 0x7ffff7d9…
162778 …[infrun] resume_1: step=1, signal=GDB_SIGNAL_0, trap_expected=1, current thread [894072.894077.0] …
162952 No symbol "p_union" in current context.
163146 has led to the current arrangement it is to prevent libtool from picking
163148 not at least with our current libtool incarnation, as directly referring
163838 names within the current build of GDB.
164219 with zero sym on the call might be a solution, but current linkers
164356 The current system root is "target:".
166092 If gdb would use the default AX_CXX_COMPILE_STDCXX from autoconf-archive, then
166141 AX_CXX_COMPILE_STDCXX from autoconf-archive.
166318 list all the targets that the current build supports. This aligns with
166369 Instead of comparing the user provided value against the current value
166759 "table" in the current namespace ("Dwarf" in this case).
168905 gdb.error: No symbol "ada_evaluate_subexp" in current context.
169559 (gdb) FAIL: gdb.python/py-events.exp: get current thread
169954 Also had to update the text capitalization to match current manual.
170010 With current master and gcc 7.5.0/8.5.0, we have this timeout:
170102 (current): Update initialisation.
170615 With current trunk and target board cc-with-debug-names we have:
171242 No symbol "clear_complaints" in current context.^M
171617 again, in proceed() we compare the current pc with the cached stop_pc.
172114 No symbol "clear_complaints" in current context.^M
172539 No symbol "outstring_func" in current context.^M
172792 With current gdb we run into:
172958 The current syntax of proc arange is:
173182 We can use current dwarf assembly infrastructure to declare a label that marks
173310 breakpoint stop sets the current language to the language that was
173314 sets the current language to C++ at startup, causing this test to
173378 there's no current commitment/incentive to support/workaround gas-generated
173896 In this case, an additional check is needed. With the current code,
174132 In the current implementation of the prologue scanner, GDB stops when
174509 spot is pretty hit and miss. I did try changing the current HEAD GDB
174873 to make sure registered smobs get exported from the current
174888 smob type from the current module.
174906 …GAS: DWARF-5: Ensure that the 0'th entry in the directory table contains the current working direc…
174908 contains current working directory.
175332 the current code, there were some attempts at doing this, just using the
176099 explain a couple more details behind the current design:
176189 operands predated our current conventions; those instructions moved to map 3.
176242 operands predated our current conventions; those instructions moved to map 3.
176378 be set running with its current $pc value. This means that the new
176449 The current state is problematic when testing with CC_FOR_TARGET=clang,
176722 target_follow_fork is called with the parent as the current inferior.
176724 current inferior. This means that target_follow_fork is sometimes
176746 parent as the current inferior. That lets all targets present on the
176766 the current inferior between parent and child. Nothing in
176767 exec_on_vfork depends on the current inferior, after this change.
177256 The current conclusion is that it's best to disable this. This is explained
178400 The current implementation of the -break-condition command's argument
178469 Update the NetBSD system call table to match NetBSD-current.
178579 With the current code, both a NULL pointer and an empty string can mean
178769 No definition of "s" in current context.^M
179276 gdb: set current thread in btrace_compute_ftrace_{bts,pt}
179365 new thread isn't the current thread, inferior_ptid is null_ptid. I
179382 make TP the current thread. Since btrace_compute_ftrace_bts takes the
179384 doesn't require its caller to also set the global current context
179385 (current thread) when calling. If it needs to call other functions
179386 that do require the global current thread to be set, then it needs to
179387 temporarily change the current thread while calling these other
179388 functions. Therefore, switch and restore the current thread in
179569 actually iterating on inferiors. The current implementation:
179706 to throw an exception. I think this is preferable -- the current
179767 call site: at this point we have switched the current program space
179768 to the child's, but not the current inferior nor the current thread.
179771 current inferior and inferior 2's program space as the current
179773 setting up inferior 2, and all that code relies on the current
179775 make inferior 2 the current one, but there are other problems (see
179810 thread_db_load are called, the current inferior is (erroneously)
179814 current inferior is the correct one and the child's LWP exists, so
180669 introducing a dependency on the current inferior (the current inferior
180670 is used to get the current target stack). For debug messages, I find it
180792 currently using the current thread's wait status. And the current
180864 list to find the current tail. It would be nice to get rid of that
180959 It's not possible with current master, but with this patch [1] that I
181910 requirements. Looking at the current description of those functions,
181927 system and user CPU time of the current process. It does not
182404 particular, assumes that there is a current thread, as it tries to get
182405 the current thread's regcache.
182432 Rename the section of the current branch, now that it has