Home
last modified time | relevance | path

Searched refs:breakpoints (Results 1 – 25 of 108) sorted by relevance

12345

/openbsd-src/gnu/usr.bin/binutils/gdb/gdbserver/
H A Dmem-break.c49 struct breakpoint *breakpoints; variable
70 bp->next = breakpoints; in set_breakpoint_at()
71 breakpoints = bp; in set_breakpoint_at()
79 if (breakpoints == bp) in delete_breakpoint()
81 breakpoints = bp->next; in delete_breakpoint()
87 cur = breakpoints; in delete_breakpoint()
105 struct breakpoint *bp = breakpoints; in find_breakpoint_at()
215 struct breakpoint *bp = breakpoints; in check_mem_read()
248 struct breakpoint *bp = breakpoints; in check_mem_write()
/openbsd-src/gnu/llvm/lldb/utils/lui/
H A Dsourcewin.py28 self.breakpoints = {}
131 bps = [] if not self.filename in self.breakpoints else self.breakpoints[self.filename]
147 def formatContent(self, content, pc_line, breakpoints): argument
158 if line_num in breakpoints:
178 if path in self.breakpoints:
179 self.breakpoints[path].update(lines)
181 self.breakpoints[path] = lines
186 if path in self.breakpoints:
187 self.breakpoints[path].difference_update(lines)
/openbsd-src/gnu/llvm/lldb/docs/use/
H A Dtroubleshooting.rst14 When setting breakpoints in implementation source files (.c, cpp, cxx, .m, .mm,
26 This will cause breakpoints in "bar.c" to be inlined into the compile unit for
28 files in some way such that breakpoints from one implementation file will be
39 Setting breakpoints in header files always searches all compile units because
41 breakpoints to have source line information that matches many header file
49 information, this can cause breakpoints to not be resolved. Try setting
50 breakpoints using the file basename only.
95 will set breakpoints by full paths where the path doesn't match the full path
96 in the debug info and this can cause LLDB to not resolve breakpoints. You can
98 for any source file and line breakpoints that the IDE set using:
H A Dondemand.rst50 users to reliably set breakpoints by file and line. As the user debugs their
58 Since most users set breakpoints by file and line, this is an easy way for
61 tables in debug information are cheap to parse and breakpoints will be able to
62 be set in any module that has debug info. Setting breakpoints by file and line
77 Setting breakpoints by function name can work, but we try to avoid using
84 mean that setting breakpoints on inline function names can fail for modules
88 allow users to set breakpoints on all concrete functions reliably. Stripped
109 - Setting breakpoints by function name for inlined functions
113 Setting breakpoints by function name can fail for inline function because this
118 breakpoints are a good way still use on demand symbol loading effectively
H A Dtutorial.rst84 Setting breakpoints by name is even more specialized in LLDB as you can specify
101 You can limit any breakpoints to a specific executable image by using the
225 We've discussed how to set breakpoints above. You can use help breakpoint set
233 You can find out about the breakpoints you've set with:
238 Current breakpoints:
253 Also, the logical breakpoints remain live so that if another shared library were
329 …breakpoints. For instance, you might want to check that self == nil and if it is, print a backtrac…
337 …is problem. The simple solution would be to use the name to gather the breakpoints you want to aff…
343 …en you've made all your breakpoints, you can set up or modify the options using the name to collec…
349 That is better, but suffers from the problem that when new breakpoints get
[all …]
/openbsd-src/gnu/usr.bin/binutils/gdb/testsuite/gdb.base/
H A Dgdb_history30 delete breakpoints
37 disable breakpoints
61 enable breakpoints delete
62 enable breakpoints once
63 enable breakpoints
87 info breakpoints
/openbsd-src/gnu/llvm/lldb/packages/Python/lldbsuite/test/
H A Dlldbinline.py33 self.breakpoints = []
68 self.breakpoints.append(current_breakpoint)
72 for bkpt in self.breakpoints:
76 for breakpoint in self.breakpoints:
81 for breakpoint in self.breakpoints:
/openbsd-src/gnu/llvm/lldb/source/Commands/
H A DCommandObjectBreakpointCommand.cpp340 const BreakpointList &breakpoints = target.GetBreakpointList(); in DoExecute() local
341 size_t num_breakpoints = breakpoints.GetSize(); in DoExecute()
512 const BreakpointList &breakpoints = target.GetBreakpointList(); in DoExecute() local
513 size_t num_breakpoints = breakpoints.GetSize(); in DoExecute()
592 const BreakpointList &breakpoints = target->GetBreakpointList(); in DoExecute() local
593 size_t num_breakpoints = breakpoints.GetSize(); in DoExecute()
H A DCommandObjectBreakpoint.cpp917 const BreakpointList &breakpoints = target.GetBreakpointList(); in DoExecute() local
919 size_t num_breakpoints = breakpoints.GetSize(); in DoExecute()
1031 const BreakpointList &breakpoints = target.GetBreakpointList(); in DoExecute() local
1032 size_t num_breakpoints = breakpoints.GetSize(); in DoExecute()
1177 const BreakpointList &breakpoints = in DoExecute() local
1182 size_t num_breakpoints = breakpoints.GetSize(); in DoExecute()
1196 Breakpoint *breakpoint = breakpoints.GetBreakpointAtIndex(i).get(); in DoExecute()
1310 BreakpointList &breakpoints = target.GetBreakpointList(); in DoExecute() local
1311 size_t num_breakpoints = breakpoints.GetSize(); in DoExecute()
1324 BreakIDs.push_back(breakpoints.GetBreakpointAtIndex(i)->GetID()); in DoExecute()
[all …]
H A DOptions.td53 Desc<"Show debugger internal breakpoints">;
61 def blist_dummy_bp : Option<"dummy-breakpoints", "D">,
62 Desc<"List Dummy breakpoints - i.e. breakpoints set before a file is "
103 Option<"dummy-breakpoints", "D">, Group<1>,
104 Desc<"Act on Dummy breakpoints - i.e. breakpoints set before a file is "
114 Desc<"Require the breakpoint to use hardware breakpoints.">;
119 "standard include file extensions. To set breakpoints on .c/.cpp/.m/.mm "
188 "expression (note: currently only implemented for setting breakpoints on "
204 Desc<"Move breakpoints to nearest code. If not set the "
208 Desc<"A specifier in the form filename:line[:column] for setting file & line breakpoints.">;
[all …]
/openbsd-src/gnu/llvm/lldb/examples/python/
H A Dperformance.py113 self.breakpoints = list()
116 self.breakpoints.append(breakpoint)
134 self.breakpoints.append(
138 self.breakpoints.append(
144 for bp in self.breakpoints:
H A Dprocess_events.py274 if launch_info and options.breakpoints:
275 for bp in options.breakpoints:
335 if options.breakpoints:
336 for bp in options.breakpoints:
/openbsd-src/gnu/llvm/lldb/source/Target/
H A DStatistics.cpp131 BreakpointList &breakpoints = target.GetBreakpointList(i == 1); in ToJSON() local
133 breakpoints.GetListMutex(lock); in ToJSON()
134 size_t num_breakpoints = breakpoints.GetSize(); in ToJSON()
136 Breakpoint *bp = breakpoints.GetBreakpointAtIndex(i).get(); in ToJSON()
H A DTargetProperties.td16 Desc<"Move breakpoints to nearest code.">;
36 Desc<"Skip function prologues when setting breakpoints by name.">;
91 def BreakpointUseAvoidList: Property<"breakpoints-use-platform-avoid-list", "Boolean">,
93 Desc<"Consult the platform module avoid list when setting non-module specific breakpoints.">;
136 …breakpoints by file and line. Breakpoint locations can end up being inlined by the compiler, so th…
178 Desc<"Require all breakpoints to be hardware breakpoints.">;
201 def IgnoreBreakpointsInExpressions: Property<"ignore-breakpoints-in-expressions", "Boolean">,
204 Desc<"If true, breakpoints will be ignored during expression evaluation.">;
/openbsd-src/gnu/llvm/lldb/packages/Python/lldbsuite/test/tools/lldb-vscode/
H A Dlldbvscode_testcase.py36 breakpoints = response['body']['breakpoints']
38 for breakpoint in breakpoints:
52 breakpoints = response['body']['breakpoints']
54 for breakpoint in breakpoints:
H A Dvscode.py780 breakpoints = []
793 breakpoints.append(bp)
794 args_dict['breakpoints'] = breakpoints
814 breakpoints = []
821 breakpoints.append(bp)
822 args_dict = {'breakpoints': breakpoints}
/openbsd-src/gnu/usr.bin/binutils/gdb/
H A DPROBLEMS74 gdb/1091: Constructor breakpoints ignored
75 gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
84 breakpoints reliably in constructors or destructors.
/openbsd-src/gnu/llvm/lldb/source/Breakpoint/
H A DBreakpointIDList.cpp249 const BreakpointList &breakpoints = target->GetBreakpointList(); in FindAndReplaceIDRanges() local
250 const size_t num_breakpoints = breakpoints.GetSize(); in FindAndReplaceIDRanges()
252 Breakpoint *breakpoint = breakpoints.GetBreakpointAtIndex(j).get(); in FindAndReplaceIDRanges()
/openbsd-src/gnu/llvm/clang/tools/clang-format-vs/
H A DREADME.txt42 - You can now set breakpoints if you like
50 entries in the Tool menu. You can test it out, and any breakpoints you set will be
/openbsd-src/gnu/llvm/lldb/docs/design/
H A Doverview.rst41 runs. Whether settings breakpoints by file and line, by symbol name, by symbol
42 regular expression, or by address, breakpoints will keep trying to resolve new
45 be scoped to be set only in a specific shared library. By default, breakpoints
50 locations. This allows flexibility when dealing with breakpoints and allows us
/openbsd-src/gnu/usr.bin/binutils/gdb/doc/
H A Drefcard.tex329 info break&show defined breakpoints\cr
332 clear&delete breakpoints at next instruction\cr
333 clear \opt{\it file\tt:}{\it fun}&delete breakpoints at entry to {\it fun}()\cr
334 clear \opt{\it file\tt:}{\it line}&delete breakpoints on source line \cr
335 delete \opt{{\it n}}&delete breakpoints
338 disable \opt{{\it n}}&disable breakpoints
341 enable \opt{{\it n}}&enable breakpoints
344 enable once \opt{{\it n}}&enable breakpoints \opt{or breakpoint {\it n}};
347 enable del \opt{{\it n}}&enable breakpoints \opt{or breakpoint {\it n}};
H A Dannotate.texinfo83 * Breakpoint Info:: Information on breakpoints.
653 @cindex annotations for breakpoints
654 The output from the @code{info breakpoints} command is annotated as follows:
656 @findex breakpoints-headers
657 @findex breakpoints-table
703 @findex breakpoints-table-end
722 @findex breakpoints-invalid
725 The breakpoints may have changed. For example, the user just added or
/openbsd-src/gnu/llvm/lldb/tools/lldb-vscode/
H A DJSONUtils.h213 lldb::SBBreakpoint &bp, llvm::json::Array &breakpoints,
/openbsd-src/gnu/llvm/lldb/docs/
H A Dlldb-for-gdb-users.txt148 b) Setting breakpoints:
151 We've discussed how to set breakpoints above. You can use "help break set"
157 You can find out about the breakpoints you've set with:
160 Current breakpoints:
169 Also the breakpoints remain "live" so that if another shared library
/openbsd-src/gnu/usr.bin/gcc/gcc/
H A Dgdbinit.in98 # Put breakpoints at exit and fancy_abort in case abort is mapped

12345