Set breakpoint by sourcefile in Delve
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
How can I set a breakpoint by sourcefile?
I have the following code in a tmp.go file.
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
This works
$ dlv debug ./tmp.go
(dlv) b main.main:1
Breakpoint 1 set at 0x105395d for main.main() ./tmp.go:4
But this fails
$ dlv debug ./tmp.go
(dlv) b ./tmp.go:4
Command failed: Location "./tmp.go:4" not found
Edit:
This works
$ dlv debug ./tmp.go
(dlv) b tmp.go:4
Breakpoint 1 set at 0x105395d for main.main() ./tmp.go:4
Any ideas what might be wrong with my environment?
go delve
asked Nov 23 '18 at 23:29
BenBen
1,95421318
add a comment |
How can I set a breakpoint by sourcefile?
I have the following code in a tmp.go file.
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
This works
$ dlv debug ./tmp.go
(dlv) b main.main:1
Breakpoint 1 set at 0x105395d for main.main() ./tmp.go:4
But this fails
$ dlv debug ./tmp.go
(dlv) b ./tmp.go:4
Command failed: Location "./tmp.go:4" not found
Edit:
This works
$ dlv debug ./tmp.go
(dlv) b tmp.go:4
Breakpoint 1 set at 0x105395d for main.main() ./tmp.go:4
Any ideas what might be wrong with my environment?
go delve
asked Nov 23 '18 at 23:29
BenBen
1,95421318
add a comment |
How can I set a breakpoint by sourcefile?
I have the following code in a tmp.go file.
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
This works
$ dlv debug ./tmp.go
(dlv) b main.main:1
Breakpoint 1 set at 0x105395d for main.main() ./tmp.go:4
But this fails
$ dlv debug ./tmp.go
(dlv) b ./tmp.go:4
Command failed: Location "./tmp.go:4" not found
Edit:
This works
$ dlv debug ./tmp.go
(dlv) b tmp.go:4
Breakpoint 1 set at 0x105395d for main.main() ./tmp.go:4
Any ideas what might be wrong with my environment?
go delve
asked Nov 23 '18 at 23:29
BenBen
1,95421318
How can I set a breakpoint by sourcefile?
I have the following code in a tmp.go file.
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
This works
$ dlv debug ./tmp.go
(dlv) b main.main:1
Breakpoint 1 set at 0x105395d for main.main() ./tmp.go:4
But this fails
$ dlv debug ./tmp.go
(dlv) b ./tmp.go:4
Command failed: Location "./tmp.go:4" not found
Edit:
This works
$ dlv debug ./tmp.go
(dlv) b tmp.go:4
Breakpoint 1 set at 0x105395d for main.main() ./tmp.go:4
Any ideas what might be wrong with my environment?
go delve
go delve
asked Nov 23 '18 at 23:29
BenBen
1,95421318
asked Nov 23 '18 at 23:29
BenBen
1,95421318
edited Nov 24 '18 at 17:27
Ben
asked Nov 23 '18 at 23:29
BenBen
1,95421318
asked Nov 23 '18 at 23:29
BenBen
1,95421318
asked Nov 23 '18 at 23:29
BenBen
1,95421318
1,95421318
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Any ideas what might be wrong with my environment?
Why should this question be closed?
off-topic because...
Questions seeking debugging help ("why isn't this code working?") must
include the desired behavior, a specific problem or error and the
shortest code necessary to reproduce it in the question itself.
Questions without a clear problem statement are not useful to other
readers. See: How to create a Minimal, Complete, and Verifiable
example.
You didn't provide an MCVE, so we can only guess.
We have no idea what is in your main.go, so how do you expect us to know what your problem is?
For example, just a guess, with an MCVE,
main.go:
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
Playground: https://play.golang.org/p/i2D9uZnFlXn
Output:
$ go run main.go
3
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.main:4
Breakpoint 1 set at 0x454bda for main.main() ./main.go:7
(dlv) quit
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.go:4
Breakpoint 1 set at 0x454b9d for main.main() ./main.go:4
(dlv) quit
$
break main.main:4 and break main.go:4 are not the same thing, at ./main.go:7 and at ./main.go:4 respectively. Line numbers are relative to files, functions, etc.
answered Nov 24 '18 at 3:45
peterSOpeterSO
99.2k16169184
Thank you for the comment. I update the question to use your example.
– Ben
Nov 24 '18 at 17:23
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53453860%2fset-breakpoint-by-sourcefile-in-delve%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Any ideas what might be wrong with my environment?
Why should this question be closed?
off-topic because...
Questions seeking debugging help ("why isn't this code working?") must
include the desired behavior, a specific problem or error and the
shortest code necessary to reproduce it in the question itself.
Questions without a clear problem statement are not useful to other
readers. See: How to create a Minimal, Complete, and Verifiable
example.
You didn't provide an MCVE, so we can only guess.
We have no idea what is in your main.go, so how do you expect us to know what your problem is?
For example, just a guess, with an MCVE,
main.go:
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
Playground: https://play.golang.org/p/i2D9uZnFlXn
Output:
$ go run main.go
3
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.main:4
Breakpoint 1 set at 0x454bda for main.main() ./main.go:7
(dlv) quit
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.go:4
Breakpoint 1 set at 0x454b9d for main.main() ./main.go:4
(dlv) quit
$
break main.main:4 and break main.go:4 are not the same thing, at ./main.go:7 and at ./main.go:4 respectively. Line numbers are relative to files, functions, etc.
answered Nov 24 '18 at 3:45
peterSOpeterSO
99.2k16169184
Thank you for the comment. I update the question to use your example.
– Ben
Nov 24 '18 at 17:23
add a comment |
Any ideas what might be wrong with my environment?
Why should this question be closed?
off-topic because...
Questions seeking debugging help ("why isn't this code working?") must
include the desired behavior, a specific problem or error and the
shortest code necessary to reproduce it in the question itself.
Questions without a clear problem statement are not useful to other
readers. See: How to create a Minimal, Complete, and Verifiable
example.
You didn't provide an MCVE, so we can only guess.
We have no idea what is in your main.go, so how do you expect us to know what your problem is?
For example, just a guess, with an MCVE,
main.go:
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
Playground: https://play.golang.org/p/i2D9uZnFlXn
Output:
$ go run main.go
3
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.main:4
Breakpoint 1 set at 0x454bda for main.main() ./main.go:7
(dlv) quit
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.go:4
Breakpoint 1 set at 0x454b9d for main.main() ./main.go:4
(dlv) quit
$
break main.main:4 and break main.go:4 are not the same thing, at ./main.go:7 and at ./main.go:4 respectively. Line numbers are relative to files, functions, etc.
answered Nov 24 '18 at 3:45
peterSOpeterSO
99.2k16169184
Thank you for the comment. I update the question to use your example.
– Ben
Nov 24 '18 at 17:23
add a comment |
Any ideas what might be wrong with my environment?
Why should this question be closed?
off-topic because...
Questions seeking debugging help ("why isn't this code working?") must
include the desired behavior, a specific problem or error and the
shortest code necessary to reproduce it in the question itself.
Questions without a clear problem statement are not useful to other
readers. See: How to create a Minimal, Complete, and Verifiable
example.
You didn't provide an MCVE, so we can only guess.
We have no idea what is in your main.go, so how do you expect us to know what your problem is?
For example, just a guess, with an MCVE,
main.go:
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
Playground: https://play.golang.org/p/i2D9uZnFlXn
Output:
$ go run main.go
3
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.main:4
Breakpoint 1 set at 0x454bda for main.main() ./main.go:7
(dlv) quit
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.go:4
Breakpoint 1 set at 0x454b9d for main.main() ./main.go:4
(dlv) quit
$
break main.main:4 and break main.go:4 are not the same thing, at ./main.go:7 and at ./main.go:4 respectively. Line numbers are relative to files, functions, etc.
answered Nov 24 '18 at 3:45
peterSOpeterSO
99.2k16169184
Any ideas what might be wrong with my environment?
Why should this question be closed?
off-topic because...
Questions seeking debugging help ("why isn't this code working?") must
include the desired behavior, a specific problem or error and the
shortest code necessary to reproduce it in the question itself.
Questions without a clear problem statement are not useful to other
readers. See: How to create a Minimal, Complete, and Verifiable
example.
You didn't provide an MCVE, so we can only guess.
We have no idea what is in your main.go, so how do you expect us to know what your problem is?
For example, just a guess, with an MCVE,
main.go:
package main
func main() {
a, b := 1, 2
c := a + b
println(c)
}
Playground: https://play.golang.org/p/i2D9uZnFlXn
Output:
$ go run main.go
3
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.main:4
Breakpoint 1 set at 0x454bda for main.main() ./main.go:7
(dlv) quit
$ dlv debug ./main.go
Type 'help' for list of commands.
(dlv) break main.go:4
Breakpoint 1 set at 0x454b9d for main.main() ./main.go:4
(dlv) quit
$
break main.main:4 and break main.go:4 are not the same thing, at ./main.go:7 and at ./main.go:4 respectively. Line numbers are relative to files, functions, etc.
answered Nov 24 '18 at 3:45
peterSOpeterSO
99.2k16169184
edited Nov 24 '18 at 14:07
answered Nov 24 '18 at 3:45
peterSOpeterSO
99.2k16169184
answered Nov 24 '18 at 3:45
peterSOpeterSO
99.2k16169184
answered Nov 24 '18 at 3:45
peterSOpeterSO
99.2k16169184
99.2k16169184
Thank you for the comment. I update the question to use your example.
– Ben
Nov 24 '18 at 17:23
add a comment |
Thank you for the comment. I update the question to use your example.
– Ben
Nov 24 '18 at 17:23
Thank you for the comment. I update the question to use your example.
– Ben
Nov 24 '18 at 17:23
Thank you for the comment. I update the question to use your example.
– Ben
Nov 24 '18 at 17:23
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53453860%2fset-breakpoint-by-sourcefile-in-delve%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
