[Bug gdb/17612] gdb should be able to clip large memory reads to a certain size

["dje at google dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #2 from dje at google dot com ---
It's not the amount of memory read that is slowing things down here, though it
might still be nice to provide a knob - we don't want to accidently trip a
malloc failure.

What's taking forever in this example is computing the number of repeated
elements.  Change foo to 1M in size, and set target debug to 1 and it's easier
to see.

(gdb) set target debug 1
(gdb) p *p
target_thread_address_space (process 12972) = 1
native:target_xfer_partial (2, (null), 0x2dd1610, 0x0, 0x401ba8, 8) = 1, 8,
bytes =
 10 10 60 f7 ff 7f 00 00
native:target_xfer_partial (2, (null), 0x7f63eadcc010, 0x0, 0x7ffff7601010,
1048576) = 1, 1048576, bytes =
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...
$1 = {

[long uninterruptable pause here]

  foo =     '\000' <repeats 1048575 times>
}
(gdb) 

Should the "repeats xxx times" calculation take into account "print elements" ?
Maybe "repeats at least 200 times" (where 200 is the value of "print elements")
?

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