New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/compile: Debug information missing : no stack info , no variables info using gdb #8357
Milestone
Comments
Note the beginning of http://golang.org/doc/gdb . Labels changed: added repo-main, release-none, gdb. |
Thanks very much on the fast reply . SO , just to see that I understand correctly : If GO 1.2.1 does show the debug info , and GO 1.3 does not is there no other way to see it , any alternative for the gdb ? is there any big differences between gc / gcc ? or to sum it up , are my alternatives using fmt.Print every other line , or using 1.2.1 ? Thanks . |
The report is unclear but there's definitely something funny going on. Given the snippet in the image I wrote this file: http://play.golang.org/p/islHo1hsMN package main import ( "fmt" ) func main() { a := 6 fmt.Println(a) sub(a) } func sub(a int) { a = 7 subsub(a) } func subsub(a int) { a = 8 fmt.Println(a) } I compiled it at tip (1.3+) and at 1.2, and then ran gdb and set a breakpoint at 'main.subsub'. With 1.3, bt prints #0 main.subsub (a=7) at /home/r/bug.go:18 #1 0x0000000000400cce in main.sub (a=7) at /home/r/bug.go:15 #2 0x0000000000400c8f in main.main () at /home/r/bug.go:10 while with 1.2, bt prints #0 main.subsub (a=7) at /home/r/bug.go:18 #1 0x0000000000400cc9 in main.sub (a=6) at /home/r/bug.go:15 #2 0x0000000000400c92 in main.main () at /home/r/bug.go:10 Note the argument to sub has changed value between the two prints. |
OK , at least your values make "some sense" , I'm getting a real awkward value (1 !!) what OS are you on / what GO build , what GBD build , GCC flags ? any suggestions on using something other than gdb ? I've been actually thinking about building some tool, but I don't see how I do that without altering the code (not enough support in runtime/debug to integrate to the runtime's variables , or am I missing something ?) Thanks . |
Hi, Same thing happened to me as well (windows 32/64) Version 1.2.1 showed vars and stack in a proper way, but after I've upgraded to the version 1.3, the debug info became unavailable. I hope that this issue will get more attention, because it is very unconvenient situation which holds me from upgrading my setup to the newest version (now 1.3.1) Simon |
I'm concerned that this issue is from July but still says 'New' despite that numerous people have reproduced it. How would that status be changed? Are there enough maintainers to read the tickets? I'm new so I'm trying to get a sense of how fast the project is moving/fixing things. Debugging is always on my hot list, so here I am. :) thank you! Anne ps Remark #9 might be a spam post. |
The project is moving fast and fixing things, but gdb support is a known problem area. See http://golang.org/doc/gdb . I don't know of anybody actively working on improving the debug info. Status changed to Accepted. |
Comment 15 by peter@dalinis.com: https://github.com/derekparker/delve/ I have been using this, and it works well enough for me. |
Comment 17 by peter@dalinis.com: The author of delve has an open ticket for osx support. No idea for Windows. |
Debugging somehow is very essential!!! Is is possible to use this debugger https://github.com/derekparker/delve/ in combination with liteide https://github.com/visualfc/liteide? |
rsc
changed the title
cmd/gc: Debug information missing : no stack info , no variables info using gdb
cmd/compile: Debug information missing : no stack info , no variables info using gdb
Jun 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
by guybrandw:
Attachments:
The text was updated successfully, but these errors were encountered: