public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tomas.vanek at fbl dot cz" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29738] New: Arm v8 M-profile secure extension dwarf2 unwinder performance
Date: Mon, 31 Oct 2022 18:18:15 +0000	[thread overview]
Message-ID: <bug-29738-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29738
           Summary: Arm v8 M-profile secure extension dwarf2 unwinder
                    performance
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: tomas.vanek at fbl dot cz
  Target Milestone: ---

Commit a6e4a48c02acf29d6bec2ff63fc909b57cf4bc78
introduced synchronization sp with other xsp_x registers.
Unfortunately the code reads all four xsp_x registers by
get_frame_register_unsigned(). dwarf2 unwinder just passes this
request to the next inner frame. If the next inner frame is also
serviced by dwarf2, each of 4 xsp_x requests generates another 4 requests.

So e.g. 'backtrace' command on the chain of dwarf2 frames (normal debugging)
needs
  4 ^ number_of_frame
calls of arm_dwarf2_prev_register() just for stack unwinding!!!
The number of calls gets to very insane high values very soon,
8th and 9th frame unwinding is noticeable slow and 10 and more frames
looks as if gdb hangs.

Empirically tested with a counter added to the beginning of
arm_dwarf2_prev_register():

'bt' frames   total arm_dwarf2_prev_register() calls
        2       42
        3       181
        4       828
        5       3909
        6       18652
        7       89271
        8       427608
        9       2048659

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

             reply	other threads:[~2022-10-31 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 18:18 tomas.vanek at fbl dot cz [this message]
2022-11-02  8:16 ` [Bug tdep/29738] " luis.machado at arm dot com
2022-11-02 16:26 ` luis.machado at arm dot com
2022-11-03  8:20 ` luis.machado at arm dot com
2022-11-03  8:43 ` [Bug tdep/29738] Arm M-profile dwarf2 unwinder performance suffers from exponential grows tomas.vanek at fbl dot cz
2022-11-03  8:44 ` [Bug tdep/29738] Arm M-profile dwarf2 unwinder performance suffers from exponential growth tomas.vanek at fbl dot cz
2022-11-04 11:04 ` tomas.vanek at fbl dot cz
2022-11-04 15:27 ` torbjorn.svensson at st dot com
2023-02-02  3:43 ` brobecker at gnat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29738-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).