public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aditya24.garg at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31048] GDB commands very slow due to too many lseek calls Date: Thu, 09 Nov 2023 13:19:37 +0000 [thread overview] Message-ID: <bug-31048-4717-CDQqUjN5I9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31048-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31048 --- Comment #1 from Aditya Garg <aditya24.garg at gmail dot com> --- Regarding this: ``` Interesting fact: When i execute ptype <variable>. It takes 1 minute to run when current frame selected (lets say frame 5) is from file1.so. And if i go to frame 10 which belongs to file2.so, then same ptype command executes in 5 seconds. All the changes i have made are for file2.so and no change has been made to file1.so implementation. ``` Did some more investigation and found out that frame 5 and 10 belong to the same so file. My bad. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-09 13:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-09 12:47 [Bug gdb/31048] New: " aditya24.garg at gmail dot com 2023-11-09 13:19 ` aditya24.garg at gmail dot com [this message] 2023-11-10 15:09 ` [Bug gdb/31048] " aditya24.garg at gmail dot com 2023-11-10 18:29 ` simon.marchi at polymtl dot ca 2023-11-10 22:00 ` tromey at sourceware dot org 2023-11-10 23:05 ` sam at gentoo dot org 2023-11-12 14:25 ` ssbssa at sourceware dot org 2023-11-12 14:46 ` aditya24.garg at gmail dot com 2024-02-16 4:51 ` tromey at sourceware dot org
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-31048-4717-CDQqUjN5I9@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: linkBe 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).