- 05 11月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Changes CreateBreakpoint to create a logical breakpoint when multiple addresses are specified, FindLocation and the api.Location type to return logical locations and the cli to support logical breakpoints.
-
- 02 11月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Modifies FindFileLocation, FindFunctionLocation and LineToPC as well as service/debugger to support inlining and introduces the concept of logical breakpoints. For inlined functions FindFileLocation, FindFunctionLocation and LineToPC will now return one PC address for each inlining and one PC for the concrete implementation of the function (if present). A proc.Breakpoint will continue to represent a physical breakpoint, at a single memory location. Breakpoints returned by service/debugger, however, will represent logical breakpoints and may be associated with multiple memory locations and, therefore, multiple proc.Breakpoints. The necessary logic is introduced in service/debugger so that a change to a logical breakpoint will be mirrored to all its physical breakpoints and physical breakpoints are aggregated into a single logical breakpoint when returned.
-
- 30 10月, 2019 1 次提交
-
-
由 Alan Yee 提交于
Maintain naming convention
-
- 29 10月, 2019 2 次提交
-
-
由 aarzilli 提交于
program When evaluating type casts always resolve array types. Instead of resolving them by looking up the string in debug_info construct a fake array type so that a type cast to an array type always works as long as the element type exists. We already did this for byte arrays, this commit extends this to any array type. The reason is that we return a fake array type (that doesn't exist in the target program) for the array of a channel type. Fixes #1736
-
由 Alessandro Arzilli 提交于
Fixes a case of breakpoint confusion on resume caused by having two breakpoints one byte apart. This bug can cause the target program to resume execution a single byte inside an instruction and crash either with SIGILL or a SIGSEGV, or misbehave (depending on how the truncated instruction is decoded). native.(*Thread).StepInstruction should call FindBreakpoint using adjustPC==false because at that point the PC of the thread should already have been adjusted (and it has been).
-
- 26 10月, 2019 2 次提交
-
-
由 Alessandro Arzilli 提交于
This script re-runs a program until it fails or hits a breakpoint, it is useful for debugging non-deterministic problems when used in conjunction with rr.
-
由 Alessandro Arzilli 提交于
Make the 'list' command succeed for file:line expressions that don't map to any instruction. Adds an argument to the FindLocations API call that makes FindLocations return if the expression can be parsed, even if it doesn't end up matching any instruction in debug_line.
-
- 23 10月, 2019 2 次提交
-
-
由 Alessandro Arzilli 提交于
Fixes #1713
-
由 Derek Parker 提交于
Thanks to everyone who contributed!
-
- 22 10月, 2019 5 次提交
-
-
由 Alessandro Arzilli 提交于
Adds a '-r' option to the 'restart' command (and to the Restart API) that re-records the target when using rr. Also moves the code to delete the trace directory inside the gdbserial package.
-
由 Alessandro Arzilli 提交于
Updates #1711
-
由 Alessandro Arzilli 提交于
-
由 Alessandro Arzilli 提交于
Avoid crashing with nil pointer dereference, signal error instead. Fixes #1720
-
由 TerrySolar 提交于
-
- 08 10月, 2019 7 次提交
-
-
由 Alessandro Arzilli 提交于
A compile unit can produce a debug_line program consisting of multiple sequences according to the DWARF standard. The standard guarantees that addresses monotonically increment within a single sequence but different sequences may not follow this rule. This commit changes dwarf/line (in particular PCToLine and AllPCsBetween) to support debug_line sections containing units with multiple sequences. TestPCToLine needs to be changed so that it picks valid addresses (i.e. addresses covered by a sequence) as values for basePC, instead of just rounding. Fixes #1694
-
由 Alessandro Arzilli 提交于
Splits the code that loads function information from debug_info into multiple functions. This makes the changes needed to implement logical breakpoints easier to make.
-
由 Alun Evans 提交于
* Fix starlark map iteration for maps > 64 entries * Fix TestMapEvaluation
-
由 chainhelen 提交于
The origin error message is confusing, so add some details. Fixes #1700
-
由 Alessandro Arzilli 提交于
The Disassemble API call should work when there is no selected goroutine (for example because the program was just started). Fixes #1703
-
由 Cody Kaup 提交于
-
由 Alessandro Arzilli 提交于
It was failing silently.
-
- 26 9月, 2019 3 次提交
-
-
由 chainhelen 提交于
`func (v *Variable) findMethod` should support for searching methods of an embedded filed. Fixes #1688
-
由 Alessandro Arzilli 提交于
Trust argument order to determine argument frame layout when calling functions, this allows calling optimized functions and removes the special cases for runtime.mallocgc. Fixes #1589
-
由 Alessandro Arzilli 提交于
Add options to start a stacktrace from the values saved in the runtime.g struct as well as a way to disable the stackSwitch logic and just get a normal stacktrace.
-
- 16 9月, 2019 2 次提交
-
-
由 Alessandro Arzilli 提交于
If a closure captures a variable but also defines a variable of the same name in its root scope the shadowed flag would, sometimes, not be appropriately applied to the captured variable. This change: 1. sorts the variable list by depth *and* declaration line, so that closure captured variables always appear before other root-scope variables, regardless of the order used by the compiler 2. marks variable with the same name as shadowed even if there is only one scope at play. This fixes the problem but as a side effect: 1. programs compiled with Go prior to version 1.9 will have the shadowed flag applied arbitrarily (previously the shadowed flag was not applied at all) 2. programs compiled with Go prior to versoin 1.11 will still exhibit the bug, as they do not have DeclLine information. Fixes #1672
-
由 Alessandro Arzilli 提交于
Bump continuous integration to include Go 1.13, drop 1.10 from compatiblity file.
-
- 13 9月, 2019 1 次提交
-
-
由 chainhelen 提交于
This change adds the `make uninstall` command which will uninstall delve.
-
- 05 9月, 2019 2 次提交
-
-
由 chainhelen 提交于
According to the description of "CIE: length, CIE_id, version, augmentation" in Page 122 of http://dwarfstd.org/doc/Dwarf3.pdf , `augmentation` should exclude `version`
-
由 Heschi Kreinick 提交于
The fix for #1428 was buggy, partly because I communicated poorly. Sorry about that. The size of the TLS segment should be padded such that TLS addresses are congruent in the file to where they will end up memory, i.e. (tlsoffset%align) == (vaddr%align). In most cases, vaddr will be aligned and it won't matter, but if not then simply aligning the end of the segment is incorrect. This should be right. (For the record, the current rounding logic is working in bits, but PtrSize is in bytes, so it wasn't working as originally intended either.)
-
- 28 8月, 2019 2 次提交
-
-
由 Derek Parker 提交于
* all: Bump to v1.3.0 Add new version to CHANGELOG and update internal version. Thank you @Ladicle, @qaisjp, @justinclift, @tschundler, @two, @dpapastamos, @qingyunha, @rayrapetyan, @briandealwis and @msaf1980, @jeremyfaller, @stmuk, @dr2chase, @pjot726. * all: Add date to changelog
-
由 Alessandro Arzilli 提交于
-
- 14 8月, 2019 5 次提交
-
-
由 Alessandro Arzilli 提交于
They are irrelevant and confusing.
-
由 Alessandro Arzilli 提交于
-
由 Alessandro Arzilli 提交于
threadUpdater needs to be reset before every possible use. Fixes #1659
-
由 pjot726 提交于
-
由 David Chase 提交于
Intent here is to bring optargorder up to date with delve and keep it in sync (and to use optargorder to help monitor compiler output for debugging quality regressions).
-
- 13 8月, 2019 2 次提交
-
-
由 Alessandro Arzilli 提交于
proc.Next and proc.Step will call, after setting their temp breakpoints, curthread.SetCurrentBreakpoint. This is intended to find if one of the newly created breakpoints happens to be at the same instruction that curthread is stopped at. However SetCurrentBreakpoint is intended to be called after a Continue and StepInstruction operation so it will also detect if curthread is stopped one byte after a breakpoint. If the instruction immediately preceeding the current instruction of curthread happens to: 1. have one of the newly created temp breakpoints 2. be one byte long SetCurrentBreakpoint will believe that we just hit that breakpoint and therefore the instruction should be repeated, and thus rewind the PC of curthread by 1. We should distinguish between the two uses of SetCurrentBreakpoint and disable the check for "just hit" breakpoints when inappropriate. Fixes #1656
-
由 David Chase 提交于
-
- 12 8月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
-
- 10 8月, 2019 1 次提交
-
-
由 Derek Parker 提交于
Moves EvalScope methods to the proper file and organizes everything together. Also makes some EvalScope methods no longer methods and just pure functions.
-