lldb hangs when opening a dump











up vote
0
down vote

favorite












lldb-3.9 hangs when I try to open a dump from a dotnet application. The process gets completely stuck, without consuming CPU.



$ gdb -v
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git

$ lldb-3.9 -v
lldb version 3.9.1 ( revision )

$ dotnet --version
2.1.403

$ sudo gcore 27247
[New LWP 27248]
[New LWP 27249]
[New LWP 27250]
[New LWP 27251]
[New LWP 27252]
[New LWP 27253]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f6c157d8ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7ffff444dcd0, expected=0, futex_word=0x1cb3468) at ../sysdeps/unix/sysv/linux/futex-internal.h:142
142 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.
warning: target file /proc/27247/cmdline contained unexpected null characters
Saved corefile core.27247

$ ll core.27247
-rw-r--r-- 1 root root 2571743080 oct 20 19:17 core.27247

$ sudo lldb-3.9 `which dotnet` -c core.27247 -d
(lldb) target create "/usr/bin/dotnet" --core "core.27247"


The prompt never gets to (lldb) ever again. I do not even have the chance to load SOS plugin.



The application is just a infinite loop that prints "Hello world" and sleeps for one second before looping again.



UPDATE



It loads with lldb-3.6, but unfortunately lldb-3.6 has an unrelated bug



https://superuser.com/questions/1098503/characters-turn-into-unicode-in-gnome-terminal-with-lldb










share|improve this question




























    up vote
    0
    down vote

    favorite












    lldb-3.9 hangs when I try to open a dump from a dotnet application. The process gets completely stuck, without consuming CPU.



    $ gdb -v
    GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git

    $ lldb-3.9 -v
    lldb version 3.9.1 ( revision )

    $ dotnet --version
    2.1.403

    $ sudo gcore 27247
    [New LWP 27248]
    [New LWP 27249]
    [New LWP 27250]
    [New LWP 27251]
    [New LWP 27252]
    [New LWP 27253]
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    0x00007f6c157d8ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7ffff444dcd0, expected=0, futex_word=0x1cb3468) at ../sysdeps/unix/sysv/linux/futex-internal.h:142
    142 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.
    warning: target file /proc/27247/cmdline contained unexpected null characters
    Saved corefile core.27247

    $ ll core.27247
    -rw-r--r-- 1 root root 2571743080 oct 20 19:17 core.27247

    $ sudo lldb-3.9 `which dotnet` -c core.27247 -d
    (lldb) target create "/usr/bin/dotnet" --core "core.27247"


    The prompt never gets to (lldb) ever again. I do not even have the chance to load SOS plugin.



    The application is just a infinite loop that prints "Hello world" and sleeps for one second before looping again.



    UPDATE



    It loads with lldb-3.6, but unfortunately lldb-3.6 has an unrelated bug



    https://superuser.com/questions/1098503/characters-turn-into-unicode-in-gnome-terminal-with-lldb










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      lldb-3.9 hangs when I try to open a dump from a dotnet application. The process gets completely stuck, without consuming CPU.



      $ gdb -v
      GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git

      $ lldb-3.9 -v
      lldb version 3.9.1 ( revision )

      $ dotnet --version
      2.1.403

      $ sudo gcore 27247
      [New LWP 27248]
      [New LWP 27249]
      [New LWP 27250]
      [New LWP 27251]
      [New LWP 27252]
      [New LWP 27253]
      [Thread debugging using libthread_db enabled]
      Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
      0x00007f6c157d8ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7ffff444dcd0, expected=0, futex_word=0x1cb3468) at ../sysdeps/unix/sysv/linux/futex-internal.h:142
      142 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.
      warning: target file /proc/27247/cmdline contained unexpected null characters
      Saved corefile core.27247

      $ ll core.27247
      -rw-r--r-- 1 root root 2571743080 oct 20 19:17 core.27247

      $ sudo lldb-3.9 `which dotnet` -c core.27247 -d
      (lldb) target create "/usr/bin/dotnet" --core "core.27247"


      The prompt never gets to (lldb) ever again. I do not even have the chance to load SOS plugin.



      The application is just a infinite loop that prints "Hello world" and sleeps for one second before looping again.



      UPDATE



      It loads with lldb-3.6, but unfortunately lldb-3.6 has an unrelated bug



      https://superuser.com/questions/1098503/characters-turn-into-unicode-in-gnome-terminal-with-lldb










      share|improve this question















      lldb-3.9 hangs when I try to open a dump from a dotnet application. The process gets completely stuck, without consuming CPU.



      $ gdb -v
      GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git

      $ lldb-3.9 -v
      lldb version 3.9.1 ( revision )

      $ dotnet --version
      2.1.403

      $ sudo gcore 27247
      [New LWP 27248]
      [New LWP 27249]
      [New LWP 27250]
      [New LWP 27251]
      [New LWP 27252]
      [New LWP 27253]
      [Thread debugging using libthread_db enabled]
      Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
      0x00007f6c157d8ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7ffff444dcd0, expected=0, futex_word=0x1cb3468) at ../sysdeps/unix/sysv/linux/futex-internal.h:142
      142 ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.
      warning: target file /proc/27247/cmdline contained unexpected null characters
      Saved corefile core.27247

      $ ll core.27247
      -rw-r--r-- 1 root root 2571743080 oct 20 19:17 core.27247

      $ sudo lldb-3.9 `which dotnet` -c core.27247 -d
      (lldb) target create "/usr/bin/dotnet" --core "core.27247"


      The prompt never gets to (lldb) ever again. I do not even have the chance to load SOS plugin.



      The application is just a infinite loop that prints "Hello world" and sleeps for one second before looping again.



      UPDATE



      It loads with lldb-3.6, but unfortunately lldb-3.6 has an unrelated bug



      https://superuser.com/questions/1098503/characters-turn-into-unicode-in-gnome-terminal-with-lldb







      ubuntu debugging






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Oct 20 at 22:41









      Rui F Ribeiro

      38.7k1479128




      38.7k1479128










      asked Oct 20 at 17:39









      Vlad

      33




      33






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          I use lldb-4.0



          yartat@TATARENKO:/mnt/e/Working/Dumps$ lldb-4.0 $(which dotnet) --core ./player-authentication.dump
          (lldb) target create "/usr/bin/dotnet" --core "./player-authentication.dump"
          Core file '/mnt/e/Working/Dumps/./player-authentication.dump' (x86_64) was loaded.
          (lldb) plugin load /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/libsosplugin.so
          (lldb) setclrpath /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6
          Set load path for sos/dac/dbi to '/usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/'
          (lldb) clrthread
          ThreadCount: 77
          UnstartedThread: 0
          BackgroundThread: 75
          PendingThread: 0
          DeadThread: 1
          Hosted Runtime: no
          Lock
          ID OSID ThreadOBJ State GC Mode GC Alloc Context Domain Count Apt Exception
          XXXX 1 1 0000000001674CB0 2020020 Preemptive 0000000000000000:0000000000000000 000000000171D6F0 0 Ukn





          share|improve this answer








          New contributor




          Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            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: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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%2funix.stackexchange.com%2fquestions%2f476771%2flldb-hangs-when-opening-a-dump%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








            up vote
            0
            down vote



            accepted










            I use lldb-4.0



            yartat@TATARENKO:/mnt/e/Working/Dumps$ lldb-4.0 $(which dotnet) --core ./player-authentication.dump
            (lldb) target create "/usr/bin/dotnet" --core "./player-authentication.dump"
            Core file '/mnt/e/Working/Dumps/./player-authentication.dump' (x86_64) was loaded.
            (lldb) plugin load /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/libsosplugin.so
            (lldb) setclrpath /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6
            Set load path for sos/dac/dbi to '/usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/'
            (lldb) clrthread
            ThreadCount: 77
            UnstartedThread: 0
            BackgroundThread: 75
            PendingThread: 0
            DeadThread: 1
            Hosted Runtime: no
            Lock
            ID OSID ThreadOBJ State GC Mode GC Alloc Context Domain Count Apt Exception
            XXXX 1 1 0000000001674CB0 2020020 Preemptive 0000000000000000:0000000000000000 000000000171D6F0 0 Ukn





            share|improve this answer








            New contributor




            Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.






















              up vote
              0
              down vote



              accepted










              I use lldb-4.0



              yartat@TATARENKO:/mnt/e/Working/Dumps$ lldb-4.0 $(which dotnet) --core ./player-authentication.dump
              (lldb) target create "/usr/bin/dotnet" --core "./player-authentication.dump"
              Core file '/mnt/e/Working/Dumps/./player-authentication.dump' (x86_64) was loaded.
              (lldb) plugin load /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/libsosplugin.so
              (lldb) setclrpath /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6
              Set load path for sos/dac/dbi to '/usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/'
              (lldb) clrthread
              ThreadCount: 77
              UnstartedThread: 0
              BackgroundThread: 75
              PendingThread: 0
              DeadThread: 1
              Hosted Runtime: no
              Lock
              ID OSID ThreadOBJ State GC Mode GC Alloc Context Domain Count Apt Exception
              XXXX 1 1 0000000001674CB0 2020020 Preemptive 0000000000000000:0000000000000000 000000000171D6F0 0 Ukn





              share|improve this answer








              New contributor




              Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.




















                up vote
                0
                down vote



                accepted







                up vote
                0
                down vote



                accepted






                I use lldb-4.0



                yartat@TATARENKO:/mnt/e/Working/Dumps$ lldb-4.0 $(which dotnet) --core ./player-authentication.dump
                (lldb) target create "/usr/bin/dotnet" --core "./player-authentication.dump"
                Core file '/mnt/e/Working/Dumps/./player-authentication.dump' (x86_64) was loaded.
                (lldb) plugin load /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/libsosplugin.so
                (lldb) setclrpath /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6
                Set load path for sos/dac/dbi to '/usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/'
                (lldb) clrthread
                ThreadCount: 77
                UnstartedThread: 0
                BackgroundThread: 75
                PendingThread: 0
                DeadThread: 1
                Hosted Runtime: no
                Lock
                ID OSID ThreadOBJ State GC Mode GC Alloc Context Domain Count Apt Exception
                XXXX 1 1 0000000001674CB0 2020020 Preemptive 0000000000000000:0000000000000000 000000000171D6F0 0 Ukn





                share|improve this answer








                New contributor




                Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                I use lldb-4.0



                yartat@TATARENKO:/mnt/e/Working/Dumps$ lldb-4.0 $(which dotnet) --core ./player-authentication.dump
                (lldb) target create "/usr/bin/dotnet" --core "./player-authentication.dump"
                Core file '/mnt/e/Working/Dumps/./player-authentication.dump' (x86_64) was loaded.
                (lldb) plugin load /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/libsosplugin.so
                (lldb) setclrpath /usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6
                Set load path for sos/dac/dbi to '/usr/share/dotnet/shared/Microsoft.NETCore.App/2.1.6/'
                (lldb) clrthread
                ThreadCount: 77
                UnstartedThread: 0
                BackgroundThread: 75
                PendingThread: 0
                DeadThread: 1
                Hosted Runtime: no
                Lock
                ID OSID ThreadOBJ State GC Mode GC Alloc Context Domain Count Apt Exception
                XXXX 1 1 0000000001674CB0 2020020 Preemptive 0000000000000000:0000000000000000 000000000171D6F0 0 Ukn






                share|improve this answer








                New contributor




                Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer






                New contributor




                Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered yesterday









                Yaroslav Tatarenko

                16




                16




                New contributor




                Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                Yaroslav Tatarenko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • 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%2funix.stackexchange.com%2fquestions%2f476771%2flldb-hangs-when-opening-a-dump%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

                    Entries order in /etc/network/interfaces

                    新発田市

                    Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)