[Bug c++/24918] New: GDB is very slow loading.

[glaubitz at physik dot fu-berlin.de]

https://sourceware.org/bugzilla/show_bug.cgi?id=24918

            Bug ID: 24918
           Summary: GDB is very slow loading.
           Product: gdb
           Version: 7.12
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: eorlovsky at gmail dot com
  Target Milestone: ---

I wrote small program (hello, world!) using Qt 5.13. I set breakpoint on first
line of main() function. GDB is stopped on this breakpoint over 10 sec after
starting. Is it possible speed up work.

--
You are receiving this mail because:
You are on the CC list for the bug.

[glaubitz at physik dot fu-berlin.de]

https://sourceware.org/bugzilla/show_bug.cgi?id=24918

--- Comment #1 from eugene <eorlovsky at gmail dot com> ---
I'm using AstraLinux (Debian)

--
You are receiving this mail because:
You are on the CC list for the bug.

[glaubitz at physik dot fu-berlin.de]

https://sourceware.org/bugzilla/show_bug.cgi?id=24918

eugene <eorlovsky at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c++                         |gdb

--
You are receiving this mail because:
You are on the CC list for the bug.

[glaubitz at physik dot fu-berlin.de]

https://sourceware.org/bugzilla/show_bug.cgi?id=24918

eugene <eorlovsky at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eorlovsky at gmail dot com

--
You are receiving this mail because:
You are on the CC list for the bug.

[Sourceware - gdb-prs mailing list]

https://sourceware.org/bugzilla/show_bug.cgi?id=24918

Peter Foelsche <peter_foelsche at mentor dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |peter_foelsche at mentor dot com

--- Comment #2 from Peter Foelsche <peter_foelsche at mentor dot com> ---
when using strace on a gdb process hanging in symbol loading, one can see pages
of calls to deal with signal handling...

rt_sigaction(SIGSEGV, {SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, NULL, 8) = 0
rt_sigaction(SIGSEGV, {0x68a820, [], SA_RESTORER|SA_STACK, 0x3bfc60f710},
{SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigaction(SIGSEGV, {SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, NULL, 8) = 0
rt_sigaction(SIGSEGV, {0x68a820, [], SA_RESTORER|SA_STACK, 0x3bfc60f710},
{SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigaction(SIGSEGV, {SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, NULL, 8) = 0
rt_sigaction(SIGSEGV, {0x68a820, [], SA_RESTORER|SA_STACK, 0x3bfc60f710},
{SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigaction(SIGSEGV, {SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, NULL, 8) = 0
rt_sigaction(SIGSEGV, {0x68a820, [], SA_RESTORER|SA_STACK, 0x3bfc60f710},
{SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
rt_sigaction(SIGSEGV, {SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, NULL, 8) = 0
rt_sigaction(SIGSEGV, {0x68a820, [], SA_RESTORER|SA_STACK, 0x3bfc60f710},
{SIG_DFL, [], SA_RESTORER, 0x3bfc60f710}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0

--
You are receiving this mail because:
You are on the CC list for the bug.

[Sourceware - gdb-prs mailing list]

https://sourceware.org/bugzilla/show_bug.cgi?id=24918

Christian Biesinger <cbiesinger at google dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cbiesinger at google dot com

--- Comment #3 from Christian Biesinger <cbiesinger at google dot com> ---
gdb 9 had some performance improvements in this area, especially if you use
'maint set worker-threads unlimited'. Have you tried that?

Also, strace is probably not that useful for this, try using a profiler instead
(e.g. 'perf record' or sysprof)

--
You are receiving this mail because:
You are on the CC list for the bug.