debugging go application doesn't stop at breakpoints












7














I have latest IntelliJ Ultimate EAP and latest Gogland and the problem occurs on both under MacOS Sierra.



I'm trying to debug a go application by creating a debug profile for Go Application and the Run Kind is configured to Package, which contains the package name of the current project.



under Go tool arguments I have -ldflags="-linkmode internal" configured.



When I start a debug session while having some breakpoints, it would run but not stop at these breakpoints.



what am I missing?



thanks



update



ok I was able to reproduce the issue with the following project:



test1.go contains:



package main

const Numb uint64 = 5


test2.go contains:



package main

import "fmt"

func main() {
fmt.Println(Numb);
}


I Created a Go Application run/debug configuration with the following parameters:



Run kind: package
Package: github.com/kfirufk/test
Working Directory: /usr/local/Cellar/go/1.8.1/src/github.com/kfirufk/test/


when I choose a breakpoint on test2.go line 6 (the first and only line of code in the main function) and I start a debug session, I see the following output:



"/Users/ufk/Library/Application Support/IntelliJIdea2017.1/Go/lib/dlv/mac/dlv" --listen=localhost:53111 --headless=true exec /private/var/folders/cn/n7rwdd_95_l54s3zdnbxvw040000gn/T/Unnamedgo --
GOROOT=/usr/local/Cellar/go/1.8.1/libexec
GOPATH=/usr/local/opt/go
/usr/local/Cellar/go/1.8.1/libexec/bin/go build -o /private/var/folders/cn/n7rwdd_95_l54s3zdnbxvw040000gn/T/Unnamedgo -gcflags "-N -l" github.com/kfirufk/test
API server listening at: 127.0.0.1:53111
5


I get the program's output properly but Intellij did not stop in the required breakpoint.



the problem is reproduced on Intellij 2017.1.3 with Go Lang Plugin 0.171.1928 on MacOS Sierra 10.12.4.



update



trying to play with intellij's delve to try to understand better what's going on:



/Users/ufk/Library/Application Support/IntelliJIdea2017.1/intellij-go/lib/dlv/mac/dlv exec ./test


then I executed:



(dlv) step


and received:



Command failed: could not find FDE for PC 0x78bc000


did I fail to understand how to use delve or is something doesn't work properly here ?



update



yeap.. with continue the debugger works properly with both versions of delve (installed from homebrew and the intellij's version). but still intellij works the same, doesn't stop at breakpoints. i create a breakpoint at test2.go at the line when I print the variable.



any ideas ?










share|improve this question
























  • Disable the ldflags from the run configuration and try again please.
    – dlsniper
    May 18 '17 at 13:29






  • 1




    What version of the IDE/ Go plugin do you have? Can you please provide more details about the app you are trying to debug? Does it have any CGO? Are you using symlinks? Is the app open source to be able to replicate this? Thanks
    – dlsniper
    May 18 '17 at 18:29






  • 1




    @eduncan911 there are plenty that use IntelliJ for debugging (or Go for that matter). ufk where are you setting the breakpoint and it doesn't work? I cannot recreate the issue from the IDE using the same setup you mentioned. However you need to run "continue" not "step" if you intend to use delve from command line.
    – dlsniper
    May 21 '17 at 9:53








  • 1




    I had this problem, really nasty, with gogland #GO-171.4424.55 (May 12, 2017). Go plugin 171.4424.55.1932 Based on the suggestion here I upgraded delve with brew and selected "Use native" and now I have debugging again. Thanks!
    – rfay
    May 25 '17 at 23:32






  • 1




    @ufk there shouldn't be any correlation between the directories via glide and debugging. If you still have the problem even using the nightly, please open up an issue on Youtrack youtrack.jetbrains.com/issues/Go and attach the logs, you can find them via Help | Show logs in... Also, before adding the logs, go to Help | Debug Log Settings and add the following line: #com.goide.dlv.DlvVm
    – dlsniper
    May 26 '17 at 5:47
















7














I have latest IntelliJ Ultimate EAP and latest Gogland and the problem occurs on both under MacOS Sierra.



I'm trying to debug a go application by creating a debug profile for Go Application and the Run Kind is configured to Package, which contains the package name of the current project.



under Go tool arguments I have -ldflags="-linkmode internal" configured.



When I start a debug session while having some breakpoints, it would run but not stop at these breakpoints.



what am I missing?



thanks



update



ok I was able to reproduce the issue with the following project:



test1.go contains:



package main

const Numb uint64 = 5


test2.go contains:



package main

import "fmt"

func main() {
fmt.Println(Numb);
}


I Created a Go Application run/debug configuration with the following parameters:



Run kind: package
Package: github.com/kfirufk/test
Working Directory: /usr/local/Cellar/go/1.8.1/src/github.com/kfirufk/test/


when I choose a breakpoint on test2.go line 6 (the first and only line of code in the main function) and I start a debug session, I see the following output:



"/Users/ufk/Library/Application Support/IntelliJIdea2017.1/Go/lib/dlv/mac/dlv" --listen=localhost:53111 --headless=true exec /private/var/folders/cn/n7rwdd_95_l54s3zdnbxvw040000gn/T/Unnamedgo --
GOROOT=/usr/local/Cellar/go/1.8.1/libexec
GOPATH=/usr/local/opt/go
/usr/local/Cellar/go/1.8.1/libexec/bin/go build -o /private/var/folders/cn/n7rwdd_95_l54s3zdnbxvw040000gn/T/Unnamedgo -gcflags "-N -l" github.com/kfirufk/test
API server listening at: 127.0.0.1:53111
5


I get the program's output properly but Intellij did not stop in the required breakpoint.



the problem is reproduced on Intellij 2017.1.3 with Go Lang Plugin 0.171.1928 on MacOS Sierra 10.12.4.



update



trying to play with intellij's delve to try to understand better what's going on:



/Users/ufk/Library/Application Support/IntelliJIdea2017.1/intellij-go/lib/dlv/mac/dlv exec ./test


then I executed:



(dlv) step


and received:



Command failed: could not find FDE for PC 0x78bc000


did I fail to understand how to use delve or is something doesn't work properly here ?



update



yeap.. with continue the debugger works properly with both versions of delve (installed from homebrew and the intellij's version). but still intellij works the same, doesn't stop at breakpoints. i create a breakpoint at test2.go at the line when I print the variable.



any ideas ?










share|improve this question
























  • Disable the ldflags from the run configuration and try again please.
    – dlsniper
    May 18 '17 at 13:29






  • 1




    What version of the IDE/ Go plugin do you have? Can you please provide more details about the app you are trying to debug? Does it have any CGO? Are you using symlinks? Is the app open source to be able to replicate this? Thanks
    – dlsniper
    May 18 '17 at 18:29






  • 1




    @eduncan911 there are plenty that use IntelliJ for debugging (or Go for that matter). ufk where are you setting the breakpoint and it doesn't work? I cannot recreate the issue from the IDE using the same setup you mentioned. However you need to run "continue" not "step" if you intend to use delve from command line.
    – dlsniper
    May 21 '17 at 9:53








  • 1




    I had this problem, really nasty, with gogland #GO-171.4424.55 (May 12, 2017). Go plugin 171.4424.55.1932 Based on the suggestion here I upgraded delve with brew and selected "Use native" and now I have debugging again. Thanks!
    – rfay
    May 25 '17 at 23:32






  • 1




    @ufk there shouldn't be any correlation between the directories via glide and debugging. If you still have the problem even using the nightly, please open up an issue on Youtrack youtrack.jetbrains.com/issues/Go and attach the logs, you can find them via Help | Show logs in... Also, before adding the logs, go to Help | Debug Log Settings and add the following line: #com.goide.dlv.DlvVm
    – dlsniper
    May 26 '17 at 5:47














7












7








7


1





I have latest IntelliJ Ultimate EAP and latest Gogland and the problem occurs on both under MacOS Sierra.



I'm trying to debug a go application by creating a debug profile for Go Application and the Run Kind is configured to Package, which contains the package name of the current project.



under Go tool arguments I have -ldflags="-linkmode internal" configured.



When I start a debug session while having some breakpoints, it would run but not stop at these breakpoints.



what am I missing?



thanks



update



ok I was able to reproduce the issue with the following project:



test1.go contains:



package main

const Numb uint64 = 5


test2.go contains:



package main

import "fmt"

func main() {
fmt.Println(Numb);
}


I Created a Go Application run/debug configuration with the following parameters:



Run kind: package
Package: github.com/kfirufk/test
Working Directory: /usr/local/Cellar/go/1.8.1/src/github.com/kfirufk/test/


when I choose a breakpoint on test2.go line 6 (the first and only line of code in the main function) and I start a debug session, I see the following output:



"/Users/ufk/Library/Application Support/IntelliJIdea2017.1/Go/lib/dlv/mac/dlv" --listen=localhost:53111 --headless=true exec /private/var/folders/cn/n7rwdd_95_l54s3zdnbxvw040000gn/T/Unnamedgo --
GOROOT=/usr/local/Cellar/go/1.8.1/libexec
GOPATH=/usr/local/opt/go
/usr/local/Cellar/go/1.8.1/libexec/bin/go build -o /private/var/folders/cn/n7rwdd_95_l54s3zdnbxvw040000gn/T/Unnamedgo -gcflags "-N -l" github.com/kfirufk/test
API server listening at: 127.0.0.1:53111
5


I get the program's output properly but Intellij did not stop in the required breakpoint.



the problem is reproduced on Intellij 2017.1.3 with Go Lang Plugin 0.171.1928 on MacOS Sierra 10.12.4.



update



trying to play with intellij's delve to try to understand better what's going on:



/Users/ufk/Library/Application Support/IntelliJIdea2017.1/intellij-go/lib/dlv/mac/dlv exec ./test


then I executed:



(dlv) step


and received:



Command failed: could not find FDE for PC 0x78bc000


did I fail to understand how to use delve or is something doesn't work properly here ?



update



yeap.. with continue the debugger works properly with both versions of delve (installed from homebrew and the intellij's version). but still intellij works the same, doesn't stop at breakpoints. i create a breakpoint at test2.go at the line when I print the variable.



any ideas ?










share|improve this question















I have latest IntelliJ Ultimate EAP and latest Gogland and the problem occurs on both under MacOS Sierra.



I'm trying to debug a go application by creating a debug profile for Go Application and the Run Kind is configured to Package, which contains the package name of the current project.



under Go tool arguments I have -ldflags="-linkmode internal" configured.



When I start a debug session while having some breakpoints, it would run but not stop at these breakpoints.



what am I missing?



thanks



update



ok I was able to reproduce the issue with the following project:



test1.go contains:



package main

const Numb uint64 = 5


test2.go contains:



package main

import "fmt"

func main() {
fmt.Println(Numb);
}


I Created a Go Application run/debug configuration with the following parameters:



Run kind: package
Package: github.com/kfirufk/test
Working Directory: /usr/local/Cellar/go/1.8.1/src/github.com/kfirufk/test/


when I choose a breakpoint on test2.go line 6 (the first and only line of code in the main function) and I start a debug session, I see the following output:



"/Users/ufk/Library/Application Support/IntelliJIdea2017.1/Go/lib/dlv/mac/dlv" --listen=localhost:53111 --headless=true exec /private/var/folders/cn/n7rwdd_95_l54s3zdnbxvw040000gn/T/Unnamedgo --
GOROOT=/usr/local/Cellar/go/1.8.1/libexec
GOPATH=/usr/local/opt/go
/usr/local/Cellar/go/1.8.1/libexec/bin/go build -o /private/var/folders/cn/n7rwdd_95_l54s3zdnbxvw040000gn/T/Unnamedgo -gcflags "-N -l" github.com/kfirufk/test
API server listening at: 127.0.0.1:53111
5


I get the program's output properly but Intellij did not stop in the required breakpoint.



the problem is reproduced on Intellij 2017.1.3 with Go Lang Plugin 0.171.1928 on MacOS Sierra 10.12.4.



update



trying to play with intellij's delve to try to understand better what's going on:



/Users/ufk/Library/Application Support/IntelliJIdea2017.1/intellij-go/lib/dlv/mac/dlv exec ./test


then I executed:



(dlv) step


and received:



Command failed: could not find FDE for PC 0x78bc000


did I fail to understand how to use delve or is something doesn't work properly here ?



update



yeap.. with continue the debugger works properly with both versions of delve (installed from homebrew and the intellij's version). but still intellij works the same, doesn't stop at breakpoints. i create a breakpoint at test2.go at the line when I print the variable.



any ideas ?







debugging go intellij-idea gogland






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 22 '17 at 12:30

























asked May 18 '17 at 5:01









ufk

10.6k49167293




10.6k49167293












  • Disable the ldflags from the run configuration and try again please.
    – dlsniper
    May 18 '17 at 13:29






  • 1




    What version of the IDE/ Go plugin do you have? Can you please provide more details about the app you are trying to debug? Does it have any CGO? Are you using symlinks? Is the app open source to be able to replicate this? Thanks
    – dlsniper
    May 18 '17 at 18:29






  • 1




    @eduncan911 there are plenty that use IntelliJ for debugging (or Go for that matter). ufk where are you setting the breakpoint and it doesn't work? I cannot recreate the issue from the IDE using the same setup you mentioned. However you need to run "continue" not "step" if you intend to use delve from command line.
    – dlsniper
    May 21 '17 at 9:53








  • 1




    I had this problem, really nasty, with gogland #GO-171.4424.55 (May 12, 2017). Go plugin 171.4424.55.1932 Based on the suggestion here I upgraded delve with brew and selected "Use native" and now I have debugging again. Thanks!
    – rfay
    May 25 '17 at 23:32






  • 1




    @ufk there shouldn't be any correlation between the directories via glide and debugging. If you still have the problem even using the nightly, please open up an issue on Youtrack youtrack.jetbrains.com/issues/Go and attach the logs, you can find them via Help | Show logs in... Also, before adding the logs, go to Help | Debug Log Settings and add the following line: #com.goide.dlv.DlvVm
    – dlsniper
    May 26 '17 at 5:47


















  • Disable the ldflags from the run configuration and try again please.
    – dlsniper
    May 18 '17 at 13:29






  • 1




    What version of the IDE/ Go plugin do you have? Can you please provide more details about the app you are trying to debug? Does it have any CGO? Are you using symlinks? Is the app open source to be able to replicate this? Thanks
    – dlsniper
    May 18 '17 at 18:29






  • 1




    @eduncan911 there are plenty that use IntelliJ for debugging (or Go for that matter). ufk where are you setting the breakpoint and it doesn't work? I cannot recreate the issue from the IDE using the same setup you mentioned. However you need to run "continue" not "step" if you intend to use delve from command line.
    – dlsniper
    May 21 '17 at 9:53








  • 1




    I had this problem, really nasty, with gogland #GO-171.4424.55 (May 12, 2017). Go plugin 171.4424.55.1932 Based on the suggestion here I upgraded delve with brew and selected "Use native" and now I have debugging again. Thanks!
    – rfay
    May 25 '17 at 23:32






  • 1




    @ufk there shouldn't be any correlation between the directories via glide and debugging. If you still have the problem even using the nightly, please open up an issue on Youtrack youtrack.jetbrains.com/issues/Go and attach the logs, you can find them via Help | Show logs in... Also, before adding the logs, go to Help | Debug Log Settings and add the following line: #com.goide.dlv.DlvVm
    – dlsniper
    May 26 '17 at 5:47
















Disable the ldflags from the run configuration and try again please.
– dlsniper
May 18 '17 at 13:29




Disable the ldflags from the run configuration and try again please.
– dlsniper
May 18 '17 at 13:29




1




1




What version of the IDE/ Go plugin do you have? Can you please provide more details about the app you are trying to debug? Does it have any CGO? Are you using symlinks? Is the app open source to be able to replicate this? Thanks
– dlsniper
May 18 '17 at 18:29




What version of the IDE/ Go plugin do you have? Can you please provide more details about the app you are trying to debug? Does it have any CGO? Are you using symlinks? Is the app open source to be able to replicate this? Thanks
– dlsniper
May 18 '17 at 18:29




1




1




@eduncan911 there are plenty that use IntelliJ for debugging (or Go for that matter). ufk where are you setting the breakpoint and it doesn't work? I cannot recreate the issue from the IDE using the same setup you mentioned. However you need to run "continue" not "step" if you intend to use delve from command line.
– dlsniper
May 21 '17 at 9:53






@eduncan911 there are plenty that use IntelliJ for debugging (or Go for that matter). ufk where are you setting the breakpoint and it doesn't work? I cannot recreate the issue from the IDE using the same setup you mentioned. However you need to run "continue" not "step" if you intend to use delve from command line.
– dlsniper
May 21 '17 at 9:53






1




1




I had this problem, really nasty, with gogland #GO-171.4424.55 (May 12, 2017). Go plugin 171.4424.55.1932 Based on the suggestion here I upgraded delve with brew and selected "Use native" and now I have debugging again. Thanks!
– rfay
May 25 '17 at 23:32




I had this problem, really nasty, with gogland #GO-171.4424.55 (May 12, 2017). Go plugin 171.4424.55.1932 Based on the suggestion here I upgraded delve with brew and selected "Use native" and now I have debugging again. Thanks!
– rfay
May 25 '17 at 23:32




1




1




@ufk there shouldn't be any correlation between the directories via glide and debugging. If you still have the problem even using the nightly, please open up an issue on Youtrack youtrack.jetbrains.com/issues/Go and attach the logs, you can find them via Help | Show logs in... Also, before adding the logs, go to Help | Debug Log Settings and add the following line: #com.goide.dlv.DlvVm
– dlsniper
May 26 '17 at 5:47




@ufk there shouldn't be any correlation between the directories via glide and debugging. If you still have the problem even using the nightly, please open up an issue on Youtrack youtrack.jetbrains.com/issues/Go and attach the logs, you can find them via Help | Show logs in... Also, before adding the logs, go to Help | Debug Log Settings and add the following line: #com.goide.dlv.DlvVm
– dlsniper
May 26 '17 at 5:47












3 Answers
3






active

oldest

votes


















0














Ok.. I finally got it. I got mixed up with the GOROOT structure and GOPATH structure and I placed my project in GOROOT instead of GOPATH.



this is what I did to resolve the issue



I completely deleted go with brew uninstall --force go, then reinstalled go with the following environment variables:



export GOPATH=$HOME/golang
export GOROOT=/usr/local/opt/go/libexec
export PATH=$PATH:$GOPATH/bin
export PATH=$PATH:$GOROOT/bin


then I placed my project at ~/golang/src/github.com/kfirufk/windy-server



and I was finally able to properly debug go applications.



thank you all for assisting me! :)






share|improve this answer





























    0














    For me, issue resolved adding:



    export GOROOT="/usr/local/go"


    to $HOME/.profile.



    EDIT:
    I'm using LiteIde X35.2, with Delve Debugger
    Version: 1.1.0
    Build: $Id: 1990ba12450cab9425a2ae62e6ab988725023d5c $



    under:




    DISTRIB=LinuxMint VERSION=18.3 CODENAME=sylvia



    RELEASE=#41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 2018
    UBUNTU_CODENAME=xenial KERNEL=4.15.0-38-generic HDWPLATFORM=x86_64



    DESKTOP_SESSION=XFCE WINDOWS_MANAGER=XFWM4
    DESKTOP_COMPONENTS=kdevtmpfs gnome-keyring-d xfce4-session xfce4-panel
    xfce4-volumed polkit-gnome-au xfce4-power-man xfce4-terminal
    gnome-pty-helpe



    GTK=libgtk-3-0:amd64 3.18.9-1ubuntu3.3 GStreamer=gst-launch-1.0
    version 1.8.3 GStreamer 1.8.3
    https://launchpad.net/distros/ubuntu/+source/gstreamer1.0







    share|improve this answer































      0














      In my case, the process was already running at that port and didn't close. So I had to manually stop the process and run again from IntelliJ.






      share|improve this answer





















        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
        });


        }
        });














        draft saved

        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44038930%2fdebugging-go-application-doesnt-stop-at-breakpoints%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        0














        Ok.. I finally got it. I got mixed up with the GOROOT structure and GOPATH structure and I placed my project in GOROOT instead of GOPATH.



        this is what I did to resolve the issue



        I completely deleted go with brew uninstall --force go, then reinstalled go with the following environment variables:



        export GOPATH=$HOME/golang
        export GOROOT=/usr/local/opt/go/libexec
        export PATH=$PATH:$GOPATH/bin
        export PATH=$PATH:$GOROOT/bin


        then I placed my project at ~/golang/src/github.com/kfirufk/windy-server



        and I was finally able to properly debug go applications.



        thank you all for assisting me! :)






        share|improve this answer


























          0














          Ok.. I finally got it. I got mixed up with the GOROOT structure and GOPATH structure and I placed my project in GOROOT instead of GOPATH.



          this is what I did to resolve the issue



          I completely deleted go with brew uninstall --force go, then reinstalled go with the following environment variables:



          export GOPATH=$HOME/golang
          export GOROOT=/usr/local/opt/go/libexec
          export PATH=$PATH:$GOPATH/bin
          export PATH=$PATH:$GOROOT/bin


          then I placed my project at ~/golang/src/github.com/kfirufk/windy-server



          and I was finally able to properly debug go applications.



          thank you all for assisting me! :)






          share|improve this answer
























            0












            0








            0






            Ok.. I finally got it. I got mixed up with the GOROOT structure and GOPATH structure and I placed my project in GOROOT instead of GOPATH.



            this is what I did to resolve the issue



            I completely deleted go with brew uninstall --force go, then reinstalled go with the following environment variables:



            export GOPATH=$HOME/golang
            export GOROOT=/usr/local/opt/go/libexec
            export PATH=$PATH:$GOPATH/bin
            export PATH=$PATH:$GOROOT/bin


            then I placed my project at ~/golang/src/github.com/kfirufk/windy-server



            and I was finally able to properly debug go applications.



            thank you all for assisting me! :)






            share|improve this answer












            Ok.. I finally got it. I got mixed up with the GOROOT structure and GOPATH structure and I placed my project in GOROOT instead of GOPATH.



            this is what I did to resolve the issue



            I completely deleted go with brew uninstall --force go, then reinstalled go with the following environment variables:



            export GOPATH=$HOME/golang
            export GOROOT=/usr/local/opt/go/libexec
            export PATH=$PATH:$GOPATH/bin
            export PATH=$PATH:$GOROOT/bin


            then I placed my project at ~/golang/src/github.com/kfirufk/windy-server



            and I was finally able to properly debug go applications.



            thank you all for assisting me! :)







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered May 28 '17 at 22:56









            ufk

            10.6k49167293




            10.6k49167293

























                0














                For me, issue resolved adding:



                export GOROOT="/usr/local/go"


                to $HOME/.profile.



                EDIT:
                I'm using LiteIde X35.2, with Delve Debugger
                Version: 1.1.0
                Build: $Id: 1990ba12450cab9425a2ae62e6ab988725023d5c $



                under:




                DISTRIB=LinuxMint VERSION=18.3 CODENAME=sylvia



                RELEASE=#41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 2018
                UBUNTU_CODENAME=xenial KERNEL=4.15.0-38-generic HDWPLATFORM=x86_64



                DESKTOP_SESSION=XFCE WINDOWS_MANAGER=XFWM4
                DESKTOP_COMPONENTS=kdevtmpfs gnome-keyring-d xfce4-session xfce4-panel
                xfce4-volumed polkit-gnome-au xfce4-power-man xfce4-terminal
                gnome-pty-helpe



                GTK=libgtk-3-0:amd64 3.18.9-1ubuntu3.3 GStreamer=gst-launch-1.0
                version 1.8.3 GStreamer 1.8.3
                https://launchpad.net/distros/ubuntu/+source/gstreamer1.0







                share|improve this answer




























                  0














                  For me, issue resolved adding:



                  export GOROOT="/usr/local/go"


                  to $HOME/.profile.



                  EDIT:
                  I'm using LiteIde X35.2, with Delve Debugger
                  Version: 1.1.0
                  Build: $Id: 1990ba12450cab9425a2ae62e6ab988725023d5c $



                  under:




                  DISTRIB=LinuxMint VERSION=18.3 CODENAME=sylvia



                  RELEASE=#41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 2018
                  UBUNTU_CODENAME=xenial KERNEL=4.15.0-38-generic HDWPLATFORM=x86_64



                  DESKTOP_SESSION=XFCE WINDOWS_MANAGER=XFWM4
                  DESKTOP_COMPONENTS=kdevtmpfs gnome-keyring-d xfce4-session xfce4-panel
                  xfce4-volumed polkit-gnome-au xfce4-power-man xfce4-terminal
                  gnome-pty-helpe



                  GTK=libgtk-3-0:amd64 3.18.9-1ubuntu3.3 GStreamer=gst-launch-1.0
                  version 1.8.3 GStreamer 1.8.3
                  https://launchpad.net/distros/ubuntu/+source/gstreamer1.0







                  share|improve this answer


























                    0












                    0








                    0






                    For me, issue resolved adding:



                    export GOROOT="/usr/local/go"


                    to $HOME/.profile.



                    EDIT:
                    I'm using LiteIde X35.2, with Delve Debugger
                    Version: 1.1.0
                    Build: $Id: 1990ba12450cab9425a2ae62e6ab988725023d5c $



                    under:




                    DISTRIB=LinuxMint VERSION=18.3 CODENAME=sylvia



                    RELEASE=#41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 2018
                    UBUNTU_CODENAME=xenial KERNEL=4.15.0-38-generic HDWPLATFORM=x86_64



                    DESKTOP_SESSION=XFCE WINDOWS_MANAGER=XFWM4
                    DESKTOP_COMPONENTS=kdevtmpfs gnome-keyring-d xfce4-session xfce4-panel
                    xfce4-volumed polkit-gnome-au xfce4-power-man xfce4-terminal
                    gnome-pty-helpe



                    GTK=libgtk-3-0:amd64 3.18.9-1ubuntu3.3 GStreamer=gst-launch-1.0
                    version 1.8.3 GStreamer 1.8.3
                    https://launchpad.net/distros/ubuntu/+source/gstreamer1.0







                    share|improve this answer














                    For me, issue resolved adding:



                    export GOROOT="/usr/local/go"


                    to $HOME/.profile.



                    EDIT:
                    I'm using LiteIde X35.2, with Delve Debugger
                    Version: 1.1.0
                    Build: $Id: 1990ba12450cab9425a2ae62e6ab988725023d5c $



                    under:




                    DISTRIB=LinuxMint VERSION=18.3 CODENAME=sylvia



                    RELEASE=#41~16.04.1-Ubuntu SMP Wed Oct 10 20:16:04 UTC 2018
                    UBUNTU_CODENAME=xenial KERNEL=4.15.0-38-generic HDWPLATFORM=x86_64



                    DESKTOP_SESSION=XFCE WINDOWS_MANAGER=XFWM4
                    DESKTOP_COMPONENTS=kdevtmpfs gnome-keyring-d xfce4-session xfce4-panel
                    xfce4-volumed polkit-gnome-au xfce4-power-man xfce4-terminal
                    gnome-pty-helpe



                    GTK=libgtk-3-0:amd64 3.18.9-1ubuntu3.3 GStreamer=gst-launch-1.0
                    version 1.8.3 GStreamer 1.8.3
                    https://launchpad.net/distros/ubuntu/+source/gstreamer1.0








                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Nov 13 '18 at 0:13









                    Stephen Rauch

                    27.8k153256




                    27.8k153256










                    answered Nov 12 '18 at 23:51









                    cittaul

                    11




                    11























                        0














                        In my case, the process was already running at that port and didn't close. So I had to manually stop the process and run again from IntelliJ.






                        share|improve this answer


























                          0














                          In my case, the process was already running at that port and didn't close. So I had to manually stop the process and run again from IntelliJ.






                          share|improve this answer
























                            0












                            0








                            0






                            In my case, the process was already running at that port and didn't close. So I had to manually stop the process and run again from IntelliJ.






                            share|improve this answer












                            In my case, the process was already running at that port and didn't close. So I had to manually stop the process and run again from IntelliJ.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Dec 26 '18 at 7:22









                            Vishal

                            7319




                            7319






























                                draft saved

                                draft discarded




















































                                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.





                                Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                                Please pay close attention to the following guidance:


                                • 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.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44038930%2fdebugging-go-application-doesnt-stop-at-breakpoints%23new-answer', 'question_page');
                                }
                                );

                                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







                                Popular posts from this blog

                                Xamarin.iOS Cant Deploy on Iphone

                                Glorious Revolution

                                Dulmage-Mendelsohn matrix decomposition in Python