CDT Based Debugger Produces GDB Errors During Debugging Sessions

[goclipse]

CDT Based Debugger Produces GDB Errors During Debugging Sessions

[bruno-medeiros]

This issue seems to be caused when the Go debug info in the executable has variables with odd names, such as ~anon1. I even got a variable named r·2 when running this. I think this is indicative primarily of a Go bug, since variables should not have these invalid names. GDB in the command line also is unable to handle them. (for example print ~anon1 will fail)

[sesteel]

If memory serves, the gopath is created dynamically and differently based
on the operation being performed. In the case of a 'go get'; it is $GOPATH
while for 'go build' it is $PROJECT:$GOPATH. So, I think all 'go get's go
to GOPATH and the only way to change that is to modify code.

On Thu, Sep 25, 2014 at 11:10 AM, Bruno Medeiros [email protected]
wrote:

Closed #41 #41.

—
Reply to this email directly or view it on GitHub
#41 (comment).

[bruno-medeiros]

@sesteel was that meant to be an answer to #81 (comment) ?

[sesteel]

I was just giving some insight... not really for the issue, but for you.

On Thu, Sep 25, 2014 at 1:40 PM, Bruno Medeiros [email protected]
wrote:

@sesteel https://github.com/sesteel was that meant to be an answer to #81
(comment)
#81 (comment) ?

—
Reply to this email directly or view it on GitHub
#41 (comment).

[bruno-medeiros]

Right, I got a bit confused because your comment has nothing to do with
issue #41 (which is just about GDB and debugging). Yet on issue #81 I did
recently ask about 'go get'. Perhaps you replied to the wrong Github
notification email? (Your comment showed up as a comment in issue #41 , the
GDB one)

On Thu, Sep 25, 2014 at 9:30 PM, Stanley Steel [email protected]
wrote:

I was just giving some insight... not really for the issue, but for you.

On Thu, Sep 25, 2014 at 1:40 PM, Bruno Medeiros [email protected]

wrote:

@sesteel https://github.com/sesteel was that meant to be an answer to
#81
(comment)
#81 (comment)
?

—
Reply to this email directly or view it on GitHub
#41 (comment).

—
Reply to this email directly or view it on GitHub
#41 (comment).

Bruno Medeiros
https://twitter.com/brunodomedeiros