- 19 9月, 2018 2 次提交
-
-
由 Seth Bromberger 提交于
Explicit build instructions to avoid #1342.
-
由 chainhelen 提交于
-
- 01 9月, 2018 1 次提交
-
-
由 aarzilli 提交于
Refactors edit and list so that they use the same code to get the current location and also both accept a locspec as an argument.
-
- 31 8月, 2018 4 次提交
-
-
由 aarzilli 提交于
Add a flag to Stackframe that indicates where the stack frame is the bottom-most frame of the stack. This allows clients to know whether the stack trace terminated normally or if it was truncated because the maximum depth was reached. Add a truncation message to the 'stack' command.
-
由 aarzilli 提交于
-
由 aarzilli 提交于
Fncall.go was written with the assumption that the object returned by proc.Thread.Registers does not change after we call proc.Thread.SetPC/etc. This is true for the native backend but not for gdbserial. I had anticipated this problem and introduced the Save/SavedRegisters mechanism during the first implementation of fncall.go but that's insufficient. Instead: 1. clarify that the object returned by proc.Thread.Registers could change when the CPU registers are modified. 2. add a Copy method to Registers that returns a copy of the registers that are guaranteed not to change when the CPU registers change. 3. remove the Save/SavedRegisters mechanism. This solution leaves us the option, in the future, to cache the output of proc.(Thread).Registers, avoiding a system call every time it's called.
-
由 Derek Parker 提交于
Implements missing functionality in gdbserial to enable function calls on OSX.
-
- 30 8月, 2018 2 次提交
-
-
由 aarzilli 提交于
Normally variables that have a named struct as a type will get a typedef entry as their type, sometimes however the Go linker will decide to use the DW_TAG_structure_type entry instead. For consistency always wrap a struct type into a typedef when we are creating a new variables (see comment in newVariable for exceptions). This fixes a bug where it would be impossible to call methods on a global variable.
-
由 aarzilli 提交于
Next should work even if one or more instructions in the current function can not be disassembled.
-
- 21 8月, 2018 1 次提交
-
-
由 aarzilli 提交于
Explain why we are asking the user to write to a /proc file.
-
- 17 8月, 2018 5 次提交
-
-
由 aarzilli 提交于
Add new version to CHANGELOG and update internal version. Thank you @jaym, @slp, @yasushi-saito, @acshekhara1, @benc153, @yuval-k, @functionary, @psanford @giuscri, @jsoref, @Carpetsmoker, @PatrickSchuster, @aarzilli, @derekparker, @ramya-rao-a and @dlsniper.
-
由 aarzilli 提交于
Updated call description to reflect current limitations.
-
由 aarzilli 提交于
-
由 aarzilli 提交于
-
由 aarzilli 提交于
Evaluates var.method expressions into a variable holding the corresponding method with the receiver variable as a child, in preparation for extending CallFunction so that it can call methods.
-
- 16 8月, 2018 2 次提交
-
-
由 aarzilli 提交于
-
由 aarzilli 提交于
Changes (*Variable).setValue so that it can be used in CallFunction to set up the argument frame for the function call, adding the ability to: - nil nillable types - set strings to the empty string - copy from one structure to another (including strings and slices) - convert any interface type to interface{} - convert pointer shaped types (map, chan, pointers, and structs consisting of a single pointer field) to interface{} This covers all cases where an assignment statement can be evaluated without allocating memory or calling functions in the target process.
-
- 15 8月, 2018 1 次提交
-
-
由 aarzilli 提交于
Use the same connect code path whether we started the server (with debug/exec/test) or we didn't (i.e. the 'connect' subcommand). This fixes a bug where the init file was ignored with the 'connect' subcommand and hopefully prevents future divergence between the behavior of 'connect' and the other subcommands. Fixes #1301
-
- 08 8月, 2018 3 次提交
-
-
由 Derek Parker 提交于
This patch makes it so inlined functions are returned in the function list, and also allows users to set breakpoints on the call site of inlined functions. Fixes #1261
-
由 aarzilli 提交于
Something changed on Travis side that broke TestIssue877. Disable that test when $TRAVIS is set to true.
-
由 Florin Pățan 提交于
-
- 01 8月, 2018 4 次提交
-
-
由 Ben Cotterell 提交于
Which I miss from gdb-- it's nice to be able to open where you are in your editor where you're already working on the project you're debugging.
-
由 aarzilli 提交于
If we send a process to foreground while the headless instance may get a SIGTTOU/SIGTTIN, if not ignored this signal will stop the headless. It's not clear why this only happens the second time we do this but that's how it is. Also removes the direct syscall to TIOCSPGRP and lets the go runtime do it instead. Fixes #1279
-
由 aarzilli 提交于
Fixes #1278
-
由 aarzilli 提交于
Adds a test that compares the output of our state machine with the output of the debug_line reader in the standard library and checks that they produce the same output for the debug_line section of grafana as compiled on macOS (which is the most interesting case since it uses cgo and therefore goes through dsymutil). A few bugs were uncovered and fixed: 1. is_stmt was reset improperly after a DW_LNS_end_sequence instruction 2. basic_block, prologue_end and epilogue_begin were not reset after a DW_LNS_copy instruction 3. some opcodes were not decoded properly if the debug_line section declares fewer standard opcodes than we know about. Fixes #1282
-
- 25 7月, 2018 1 次提交
-
-
由 aarzilli 提交于
Adds -defer flag to the stack command that decorates the stack traces by associating each stack frame with its deferred calls. Reworks proc.next to use this feature instead of using proc.DeferPC, laying the groundwork to implement #1240.
-
- 24 7月, 2018 4 次提交
-
-
由 aarzilli 提交于
next/step/stepout should work even if the current frame isn't the topmost stack frame, but their behavior should be different in that case (they should continue inside the function of the selected frame). Most of the logic of next/step/stepout would work correctly if we simply replaced the call to proc.topframe with something that took a frame index. However the breakpoint they set on the first deferred function is wrong, and fixing it requires scanning the defer stack and matching it to the call stack, something we can't do yet. Given that enhancing next/step/stepout will take time and the current behavior confuses users (see issue #1240) return an error if next/step/stepout are called while the currently selected frame isn't frame 0. Updates #1240
-
由 Ramya Achutha Rao 提交于
-
由 Ramya Achutha Rao 提交于
-
由 aarzilli 提交于
There is no guarantee that files will end up stored contiguously in the debug_line section which makes this optimization wrong in the general case. In particular with recent versions of go1.11 and a go.mod file present the go compiler seems to sometimes produce executables that actually violate this assumption.
-
- 20 7月, 2018 1 次提交
-
-
由 aarzilli 提交于
On newer kernels when /proc/sys/kernel/perf_event_paranoid is > 1 rr will crash with SIGABRT. Return an error instead of letting this happen.
-
- 14 7月, 2018 1 次提交
-
-
由 aarzilli 提交于
Implements the function call injection protocol introduced in go 1.11 by https://go-review.googlesource.com/c/go/+/109699. This is only the basic support, see TODO comments in pkg/proc/fncall.go for a list of missing features. Updates #119
-
- 11 7月, 2018 1 次提交
-
-
由 aarzilli 提交于
Output a better error message when users try to debug a Go 1.11 executable but delve was not built with Go 1.11.
-
- 10 7月, 2018 2 次提交
-
-
由 aarzilli 提交于
Fixes a bug where breakpoint condition evaluation would never load the value if the breakpoint condition consisted of just a single variable. Fix #1264
-
由 aarzilli 提交于
Adds StartPC to proc.G, StartLoc to api.Goroutine and show the start location in the command line client when appropriate. Updates #1104
-
- 03 7月, 2018 4 次提交
-
-
由 aarzilli 提交于
The JSON-RPC layer doesn't like non-nil error that return an empty string when the Error method is called and when this happens it shuts down the connection to the server. Since we can return a ThreadBlockedError to the client it can't have an empty string as return value. Fixes #1251
-
由 Peter Sanford 提交于
Core files created by gdb can have sections missing that would be present in OS created core files. We work around this by first reading PT_LOAD entries from the exe and then reading them from the core. Fixes #1121
-
由 aarzilli 提交于
* Adds some links to the more relevant documentation pages on the main README.md * Adds a document informally describing how to write a client of delve * Adds link to slides describing the architecture of delve
-
由 aarzilli 提交于
Setting the Level field of a logrus logger doesn't actually do anything since the Level field simply reports the log level of the last log message emitted on the logger. The right way to do that is to set logger.Logger.Level. Also cleans up newline characters from log messages emitted through logrus and fixes the direction of the arrows in the messages emitted by rpccommon, which was inconsistent with the arrows of gdbserial.
-
- 29 6月, 2018 1 次提交
-
-
由 aarzilli 提交于
Adds a field, DeclLine, to Variable containing the declaration line number of the variable.
-