How to get the Stack-trace of golang in the Crashlytics












0















Our's app is a Android app, which has a JNI writed by golang. And we use the Fabric Crashlytics to track carshes.



But, we can not get the Stack-trace information in the Crashlytics, after a crash happened in the JNI. In the Java, We can get it.



In the Object-C for iOS app, we can upload the dSYM file to map the functions. But where can I do it with Golang?



Does the Fabric support it?



Now, in the Crashlytics, we can see below only:



Crashed: Thread
0 libc.so 0xf6f4c778 (Missing)
1 libc.so 0xf6f26791 (Missing)
2 libc.so 0xf6f23933 (Missing)
3 (Missing) 0x15c791e6 (Missing)
4 libgojni.so 0xdddd910e (Missing)
5 libc.so 0xf6f214ee (Missing)
6 (Missing) 0x15c791e6 (Missing)
7 libgojni.so 0xde00a8de (Missing)
8 libgojni.so 0xde00a93e (Missing)
9 libgojni.so 0xdddd8ed6 (Missing)









share|improve this question



























    0















    Our's app is a Android app, which has a JNI writed by golang. And we use the Fabric Crashlytics to track carshes.



    But, we can not get the Stack-trace information in the Crashlytics, after a crash happened in the JNI. In the Java, We can get it.



    In the Object-C for iOS app, we can upload the dSYM file to map the functions. But where can I do it with Golang?



    Does the Fabric support it?



    Now, in the Crashlytics, we can see below only:



    Crashed: Thread
    0 libc.so 0xf6f4c778 (Missing)
    1 libc.so 0xf6f26791 (Missing)
    2 libc.so 0xf6f23933 (Missing)
    3 (Missing) 0x15c791e6 (Missing)
    4 libgojni.so 0xdddd910e (Missing)
    5 libc.so 0xf6f214ee (Missing)
    6 (Missing) 0x15c791e6 (Missing)
    7 libgojni.so 0xde00a8de (Missing)
    8 libgojni.so 0xde00a93e (Missing)
    9 libgojni.so 0xdddd8ed6 (Missing)









    share|improve this question

























      0












      0








      0








      Our's app is a Android app, which has a JNI writed by golang. And we use the Fabric Crashlytics to track carshes.



      But, we can not get the Stack-trace information in the Crashlytics, after a crash happened in the JNI. In the Java, We can get it.



      In the Object-C for iOS app, we can upload the dSYM file to map the functions. But where can I do it with Golang?



      Does the Fabric support it?



      Now, in the Crashlytics, we can see below only:



      Crashed: Thread
      0 libc.so 0xf6f4c778 (Missing)
      1 libc.so 0xf6f26791 (Missing)
      2 libc.so 0xf6f23933 (Missing)
      3 (Missing) 0x15c791e6 (Missing)
      4 libgojni.so 0xdddd910e (Missing)
      5 libc.so 0xf6f214ee (Missing)
      6 (Missing) 0x15c791e6 (Missing)
      7 libgojni.so 0xde00a8de (Missing)
      8 libgojni.so 0xde00a93e (Missing)
      9 libgojni.so 0xdddd8ed6 (Missing)









      share|improve this question














      Our's app is a Android app, which has a JNI writed by golang. And we use the Fabric Crashlytics to track carshes.



      But, we can not get the Stack-trace information in the Crashlytics, after a crash happened in the JNI. In the Java, We can get it.



      In the Object-C for iOS app, we can upload the dSYM file to map the functions. But where can I do it with Golang?



      Does the Fabric support it?



      Now, in the Crashlytics, we can see below only:



      Crashed: Thread
      0 libc.so 0xf6f4c778 (Missing)
      1 libc.so 0xf6f26791 (Missing)
      2 libc.so 0xf6f23933 (Missing)
      3 (Missing) 0x15c791e6 (Missing)
      4 libgojni.so 0xdddd910e (Missing)
      5 libc.so 0xf6f214ee (Missing)
      6 (Missing) 0x15c791e6 (Missing)
      7 libgojni.so 0xde00a8de (Missing)
      8 libgojni.so 0xde00a93e (Missing)
      9 libgojni.so 0xdddd8ed6 (Missing)






      android go stack-trace crashlytics google-fabric






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 '18 at 7:48









      Romain XieRomain Xie

      567




      567
























          1 Answer
          1






          active

          oldest

          votes


















          2














          We have been resolved this issue.



          The background:




          We build a Android app, it has a JNI writed by go, which is build by gomobile.
          We use the Fabric Crashlytics to monitor the crash information.
          But in the Crashlytics, we could not see the full stack trace information which occurred in the JNI.




          The Solution is:




          At the first, please check your NDK version, it must be r17c or more.



          Add a param --work in the gomobile command, like gomobile bind --work YOUR-SOURCE-CODE-PATH WORK=TEMP-PATH.



          After build successful, move the all of files in the jniLibs to YOUR-PROJECT-PATH/app/obj.



          At the last, do the steps list in Fabric docs.




          Hope our experiences can save your time :-)






          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%2f53370341%2fhow-to-get-the-stack-trace-of-golang-in-the-crashlytics%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









            2














            We have been resolved this issue.



            The background:




            We build a Android app, it has a JNI writed by go, which is build by gomobile.
            We use the Fabric Crashlytics to monitor the crash information.
            But in the Crashlytics, we could not see the full stack trace information which occurred in the JNI.




            The Solution is:




            At the first, please check your NDK version, it must be r17c or more.



            Add a param --work in the gomobile command, like gomobile bind --work YOUR-SOURCE-CODE-PATH WORK=TEMP-PATH.



            After build successful, move the all of files in the jniLibs to YOUR-PROJECT-PATH/app/obj.



            At the last, do the steps list in Fabric docs.




            Hope our experiences can save your time :-)






            share|improve this answer




























              2














              We have been resolved this issue.



              The background:




              We build a Android app, it has a JNI writed by go, which is build by gomobile.
              We use the Fabric Crashlytics to monitor the crash information.
              But in the Crashlytics, we could not see the full stack trace information which occurred in the JNI.




              The Solution is:




              At the first, please check your NDK version, it must be r17c or more.



              Add a param --work in the gomobile command, like gomobile bind --work YOUR-SOURCE-CODE-PATH WORK=TEMP-PATH.



              After build successful, move the all of files in the jniLibs to YOUR-PROJECT-PATH/app/obj.



              At the last, do the steps list in Fabric docs.




              Hope our experiences can save your time :-)






              share|improve this answer


























                2












                2








                2







                We have been resolved this issue.



                The background:




                We build a Android app, it has a JNI writed by go, which is build by gomobile.
                We use the Fabric Crashlytics to monitor the crash information.
                But in the Crashlytics, we could not see the full stack trace information which occurred in the JNI.




                The Solution is:




                At the first, please check your NDK version, it must be r17c or more.



                Add a param --work in the gomobile command, like gomobile bind --work YOUR-SOURCE-CODE-PATH WORK=TEMP-PATH.



                After build successful, move the all of files in the jniLibs to YOUR-PROJECT-PATH/app/obj.



                At the last, do the steps list in Fabric docs.




                Hope our experiences can save your time :-)






                share|improve this answer













                We have been resolved this issue.



                The background:




                We build a Android app, it has a JNI writed by go, which is build by gomobile.
                We use the Fabric Crashlytics to monitor the crash information.
                But in the Crashlytics, we could not see the full stack trace information which occurred in the JNI.




                The Solution is:




                At the first, please check your NDK version, it must be r17c or more.



                Add a param --work in the gomobile command, like gomobile bind --work YOUR-SOURCE-CODE-PATH WORK=TEMP-PATH.



                After build successful, move the all of files in the jniLibs to YOUR-PROJECT-PATH/app/obj.



                At the last, do the steps list in Fabric docs.




                Hope our experiences can save your time :-)







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 23 '18 at 14:19









                Romain XieRomain Xie

                567




                567
































                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370341%2fhow-to-get-the-stack-trace-of-golang-in-the-crashlytics%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

                    Costa Masnaga

                    Fotorealismo

                    Sidney Franklin