public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "massimiliano.cuoghi at systemceramics dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/28288] GDBserver should hide unreported fork childs from thread lists
Date: Mon, 15 Nov 2021 07:30:47 +0000 [thread overview]
Message-ID: <bug-28288-4717-1ZloopA10H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28288-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28288
--- Comment #40 from Massimiliano <massimiliano.cuoghi at systemceramics dot com> ---
(In reply to Massimiliano from comment #39)
> (In reply to Simon Marchi from comment #38)
> > For whether your GDB 11 build is optimized... I see some -O2 in the
> > config.log. But to be sure, go in the gdb/ directory and do "make clean &&
> > make V=1". If you see -O2 on the command line, that's good.
> >
> > The steps that seems to take time is this one. With GDB 8 (1-2 seconds):
> >
> > 10:19:12.918
> > 6362python
> > theDumper.fetchVariables({"autoderef":0,"context":"","displaystringlimit":
> > "100","dyntype":1,"expanded":["watch","local","inspect","return"],"fancy":1,
> > "formats":{},"nativemixed":0,"partialvar":"","passexceptions":0,
> > "qobjectnames":1,"resultvarname":"","stringcutoff":"10000","timestamps":1,
> > "token":6362,"typeformats":{},"watchers":[{"exp":"6472697665724964","iname":
> > "watch.0"},{"exp":"64737044726976657248617368","iname":"watch.1"},{"exp":
> > "657468496e666f726d6174696f6e48617368","iname":"watch.2"},{"exp":
> > "68526573756c74","iname":"watch.3"},{"exp":
> > "697041647272657373416e644e65746d61736b","iname":"watch.4"},{"exp":
> > "6c69737442617254797065","iname":"watch.5"},{"exp":
> > "6d61704d6f64756c61724d616368696e65496e666f","iname":"watch.6"},{"exp":
> > "6d6f64656c496e666f","iname":"watch.7"},{"exp":
> > "6d6f64656c6c6f5374616d70616e7465","iname":"watch.8"},{"exp":
> > "706172616d65746572546f436f6e76657274","iname":"watch.9"},{"exp":
> > "706172616d6574657273546f4265436f6e766572746564","iname":"watch.10"},{"exp":
> > "76616c7565","iname":"watch.11"},{"exp":"76617248617368","iname":"watch.
> > 12"}]})
> > 10:19:14.229
> >
> > With GDB 11 (~12 seconds):
> >
> > 11:22:22.323 [1ms]
> > 6462python
> > theDumper.fetchVariables({"autoderef":0,"context":"","displaystringlimit":
> > "100","dyntype":1,"expanded":["watch","local","inspect","return"],"fancy":1,
> > "formats":{},"nativemixed":0,"partialvar":"","passexceptions":0,
> > "qobjectnames":1,"resultvarname":"","stringcutoff":"10000","timestamps":1,
> > "token":6462,"typeformats":{},"watchers":[{"exp":"6472697665724964","iname":
> > "watch.0"},{"exp":"64737044726976657248617368","iname":"watch.1"},{"exp":
> > "657468496e666f726d6174696f6e48617368","iname":"watch.2"},{"exp":
> > "68526573756c74","iname":"watch.3"},{"exp":
> > "697041647272657373416e644e65746d61736b","iname":"watch.4"},{"exp":
> > "6c69737442617254797065","iname":"watch.5"},{"exp":
> > "6d61704d6f64756c61724d616368696e65496e666f","iname":"watch.6"},{"exp":
> > "6d6f64656c496e666f","iname":"watch.7"},{"exp":
> > "6d6f64656c6c6f5374616d70616e7465","iname":"watch.8"},{"exp":
> > "706172616d65746572546f436f6e76657274","iname":"watch.9"},{"exp":
> > "706172616d6574657273546f4265436f6e766572746564","iname":"watch.10"},{"exp":
> > "76616c7565","iname":"watch.11"},{"exp":"76617248617368","iname":"watch.
> > 12"}]})
> > 11:22:34.311
> >
> > That seems to be a Python helper used by QtCreator to dump variables. It
> > might be possible to reproduce the slowness out of QtCreator by running to
> > the same point, and doing a similar call to theDumper.fetchVariables.
> >
> > Do you see the same slowness if you debug locally instead of remotely?
>
> I had already checked the -o2 option and also in my opinion it is already
> optimized, even doing "make clean && make V = 1" does not change anything. i
> have the same problem using the gdb11 locally
I also tried a different linux distribution, the distribution included the
gdb10, I didn't have to recompile it, it has the same slowness defect
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-11-15 7:30 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 7:01 [Bug breakpoints/28288] New: gdbserver close connection massimiliano.cuoghi at systemceramics dot com
2021-08-30 15:32 ` [Bug breakpoints/28288] " simark at simark dot ca
2021-08-31 6:44 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:10 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:20 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:23 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:24 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 8:25 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 9:01 ` massimiliano.cuoghi at systemceramics dot com
2021-08-31 13:37 ` simark at simark dot ca
2021-08-31 13:39 ` simark at simark dot ca
2021-09-01 13:38 ` massimiliano.cuoghi at systemceramics dot com
2021-09-01 13:40 ` massimiliano.cuoghi at systemceramics dot com
2021-09-01 13:40 ` massimiliano.cuoghi at systemceramics dot com
2021-09-01 13:45 ` massimiliano.cuoghi at systemceramics dot com
2021-09-01 14:12 ` massimiliano.cuoghi at systemceramics dot com
2021-09-10 4:10 ` simark at simark dot ca
2021-09-10 4:10 ` [Bug breakpoints/28288] GDBserver should hide unreported fork childs from thread lists simark at simark dot ca
2021-09-10 4:12 ` simark at simark dot ca
2021-09-10 11:45 ` massimiliano.cuoghi at systemceramics dot com
2021-09-10 14:20 ` simark at simark dot ca
2021-10-29 9:22 ` massimiliano.cuoghi at systemceramics dot com
2021-10-29 12:03 ` simark at simark dot ca
2021-11-05 12:59 ` massimiliano.cuoghi at systemceramics dot com
2021-11-05 14:39 ` simark at simark dot ca
2021-11-05 14:39 ` simark at simark dot ca
2021-11-08 16:22 ` massimiliano.cuoghi at systemceramics dot com
2021-11-08 16:34 ` simark at simark dot ca
2021-11-11 8:21 ` massimiliano.cuoghi at systemceramics dot com
2021-11-11 8:26 ` massimiliano.cuoghi at systemceramics dot com
2021-11-11 8:28 ` massimiliano.cuoghi at systemceramics dot com
2021-11-11 19:06 ` simark at simark dot ca
2021-11-11 19:13 ` simark at simark dot ca
2021-11-12 10:29 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:29 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:30 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:31 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:31 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:32 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 10:34 ` massimiliano.cuoghi at systemceramics dot com
2021-11-12 13:07 ` simark at simark dot ca
2021-11-12 14:36 ` massimiliano.cuoghi at systemceramics dot com
2021-11-15 7:30 ` massimiliano.cuoghi at systemceramics dot com [this message]
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-28288-4717-1ZloopA10H@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).