- 08 10月, 2019 6 次提交
-
-
由 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 8 次提交
-
-
由 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.
-
由 Derek Parker 提交于
Remove `initialized` member in favor of just deriving the information it represented.
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
The methods for the BinaryInfo and Image structs were spread around in multiple files. This patch just brings them all under one file.
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
More untangling. Arch doesn't actually need to know anything about a Goroutine.
-
由 Derek Parker 提交于
This is going towards untangling proc in order to clean it up.
-
由 Derek Parker 提交于
Cleanup some unused members.
-
- 02 8月, 2019 2 次提交
-
-
由 Alessandro Arzilli 提交于
* proc: fix stacktraces when a SIGSEGV happens during a cgo call When a SIGSEGV happens in a cgo call (for example as a result of dereferencing a NULL pointer) the stack layout will look like this: (system stack) runtime.fatalthrow (system stack) runtime.throw (system stack) runtime.sigpanic (system stack) offending C function ... other C functions... (system stack) runtime.asmcgocall (goroutine stack) call inside cgo The code in switchStack would switch directly from the runtime.fatalthrow frame to the first frame in the goroutine stack, hiding important information. Disable this switch for runtime.fatalthrow and reintroduce the check for runtime.mstart that existed before this version of the code was implemented in commit 7bec20. This problem was reported in comment: https://github.com/go-delve/delve/issues/935#issuecomment-512182533 * cmd/dlv: actually disable C compiler optimizations when building
-
由 Alessandro Arzilli 提交于
* scripts: use relative path in gen-cli-docs.go Makes gen-cli-docs.go work outside GOPATH. * Documentation,cmd/dlv: tidy up --help output The description of --log-dest, --log-output and --backend is very verbose and messes up the output of --help, move it to two "additional help" subcommands.
-
- 01 8月, 2019 2 次提交
-
-
由 Steve Mynott 提交于
* alias stepout to so * run gen-cli-docs.go to update cli/README.md
-
由 Alessandro Arzilli 提交于
For some reason the version of dwz in Travis-CI now fails to run on Go binaries. Ignore the particular error.
-
- 30 7月, 2019 2 次提交
-
-
由 Derek Parker 提交于
* *: Add .cirrus.yml for FreeBSD testing * *: run go mod tidy * service/test: prefer 127.0.0.1 over localhost * dwarf/line: fix TestDebugLinePrologueParser * vendor: rerun go mod vendor
-
由 Jeremy Faller 提交于
* terminal/command: add support for next [count] * disallow negative counts. * handle github comments, and regen docs. * Fix the fact that we don't print the file info in the last step of the next count. * Fix a typo, cleanup a few other observations.
-
- 28 7月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
Implements #1640
-
- 27 7月, 2019 1 次提交
-
-
由 Alessandro Arzilli 提交于
-