- 18 3月, 2016 2 次提交
-
-
由 Derek Parker 提交于
-
由 Hubert Krauze 提交于
-
- 15 3月, 2016 4 次提交
-
-
由 Alex Brainman 提交于
-
由 Derek Parker 提交于
-
由 Derek Parker 提交于
-
由 Joe Grasse 提交于
On linux kernel 2.6.x, the Trace/Stop status is 'T' Fixes #209
-
- 14 3月, 2016 1 次提交
-
-
由 vancouverwill 提交于
It was unclear that to install, first clone Delve before `CERT=mycert make install` Added link to helpful walkthrough installation video
-
- 09 3月, 2016 1 次提交
-
-
由 aarzilli 提交于
Automatically sets a breakpoint on runtime.startpanic, the function that gets called by runtime.dopanic when a panic is not recovered. Implements #317
-
- 05 3月, 2016 1 次提交
-
-
由 aarzilli 提交于
Caches the mapping of type names to offset in debug_info to speed up variable evaluation. BEFORE: BenchmarkArray-4 100 13'238'441 ns/op 0.62 MB/s BenchmarkArrayPointer-4 200 10'044'093 ns/op 0.87 MB/s BenchmarkMap-4 1000 1'332'530 ns/op 0.77 MB/s BenchmarkGoroutinesInfo-4 10 114'677'462 ns/op BenchmarkLocalVariables-4 2000 1'223'975 ns/op AFTER: BenchmarkArray-4 200 9'925'686 ns/op 0.83 MB/s BenchmarkArrayPointer-4 100 11'143'930 ns/op 0.78 MB/s BenchmarkMap-4 2000 1'302'520 ns/op 0.79 MB/s BenchmarkGoroutinesInfo-4 30 35'079'549 ns/op BenchmarkLocalVariables-4 1000 1'137'299 ns/op Note in particular the speedup of BenchmarkGoroutinesInfo, since proc.(*Variable).parseG is a function we call a lot.
-
- 04 3月, 2016 1 次提交
-
-
由 Derek Parker 提交于
-
- 29 2月, 2016 3 次提交
-
-
由 John Aylward 提交于
-
由 aarzilli 提交于
The go compiler changed and break statements no longer get compiled to nothing when -N is passed: https://go-review.googlesource.com/#/c/19848/ https://go-review.googlesource.com/#/c/19854/
-
由 Derek Parker 提交于
-
- 28 2月, 2016 7 次提交
-
-
由 aarzilli 提交于
BreakpointInfo variables were always evaluated on CurrentThread instead of the thread that triggered the breakpoint.
-
由 aarzilli 提交于
Implements extensible mechanism to specify which commands accept prefixes (goroutine, frame, on) instead of hardcoding them in a switch. Implements #240
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
Lists all the types defined in the debugged program.
-
由 aarzilli 提交于
-
由 aarzilli 提交于
Fixes #414
-
由 Derek Parker 提交于
-
- 25 2月, 2016 4 次提交
-
-
由 aarzilli 提交于
Fixes #411
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
proc.(*Process) methods are not thread safe, multiple clients connecting simultaneously to a delve server (Issue #383) or a even a single over-eager client (Issue #408) can easily crash it. Additionally (Issue #419) calls to client.(*RPCClient).Halt can crash the server because they can result in calling the function debug/dwarf.(*Data).Type simultaneously in multiple threads which will cause it to return incompletely parsed dwarf.Type values. Fixes #408, #419 (partial)
-
由 aarzilli 提交于
Fixes #419 (partial)
-
- 20 2月, 2016 2 次提交
-
-
由 Derek Parker 提交于
Going forward, all documentation should be placed in the Documentation directory in the root of the project. This switch allows maintainers to approve updates to documentation before they are committed, as opposed to the pre-existing wiki which anybody could modify. Currently the Documentation directory includes docs on building, usage, and minimal docs around the API. This is just the initial commit, and documentation will continue to improve over time. Some changes have been made (and will continue to be made) to `cmd/dlv` to ensure we can auto-generate documentation for all commands from the newly provided script `scripts/gen-usage-docs.go`, which can be invoked via `go run scripts/gen-usage-docs.go`. Additionally, version has been split into its own package. This was a bit of housekeeping related to the changes made the `cmd/dlv`.
-
由 Derek Parker 提交于
-
- 19 2月, 2016 5 次提交
-
-
由 Alex Brainman 提交于
Unrelated to conversion, I have also changed (*Thread).readMemory to return only first count bytes of memory just as advised by ReadProcessMemory. Fixes #409 Fixes #412 Fixes #416
-
由 aarzilli 提交于
Moved the code in testvariables2 and testvariables4 into testvariables3, renamed testvariables3 into testvariables2
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
Step disassembles the current instruction, if it is a CALL sets a temp breakpoint inside the called function, after the prologue and calls Continue. Fixes #332
-
由 aarzilli 提交于
- Unlike FunctionEntryToFirstLine can skip the prologue on functions that are defined on a single line, either because they weren't formatted or because they were autogenerated - Can skip the prologue on most functions when setting a breakpoint with the filename:line syntax Fixes #396
-
- 18 2月, 2016 1 次提交
-
-
由 aarzilli 提交于
-
- 17 2月, 2016 2 次提交
-
-
由 aarzilli 提交于
Implements #109 and #120
-
由 Derek Parker 提交于
This patch allows certain commands (`debug`, `test`, and `trace`) to take an argument specifying a package name. This allows a user to specify a package other than that of the current package in the working directory. If a package name is not specified, the behavior remains the same, as in Delve will look in the current working directory for a `main` package to compile. Fixes #423
-
- 12 2月, 2016 2 次提交
-
-
由 Derek Parker 提交于
-
由 aarzilli 提交于
Implements #368
-
- 11 2月, 2016 2 次提交
-
-
由 aarzilli 提交于
1. A running goroutine is by definition not parked waiting for a chan recv 2. The FDE end address is intended to be exclusive, the code interpreted as inclusive and sometimes ended up setting a breakpoint on a function other than the current one.
-
由 aarzilli 提交于
Past the maximum recursion depth maps shouldn't be loaded at all, adding map children and not loading them breaks assumptions in the prettyprinter. Fixes #406
-
- 10 2月, 2016 1 次提交
-
-
由 Alex Brainman 提交于
-
- 09 2月, 2016 1 次提交
-
-
由 Alex Brainman 提交于
I was hoping this will fix the issue below. But there is more code that break new cgo rules. Fixes #409 (partial)
-