[Bug breakpoints/28288] GDBserver should hide unreported fork childs from thread lists

["massimiliano.cuoghi at systemceramics dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #39 from Massimiliano <massimiliano.cuoghi at systemceramics dot com> ---
(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

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