public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/17613] printing of large objects not interruptable Date: Mon, 17 Nov 2014 20:00:00 -0000 [thread overview] Message-ID: <bug-17613-4717-gVMuiGpPrw@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17613-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17613 --- Comment #1 from dje at google dot com --- I think what's taking awhile and is uninterruptable is computing repeated elements. The computation proceeds passed "print elements". E.g., change foo to 1M bytes and it still takes awhile, but it completes without taking "forever". (gdb) set debug target 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 uninterruptible pause here] foo = '\000' <repeats 1048575 times> } (gdb) Then if I change foo to contain random text (but leave it still 1GB in size) up to "print elements" (default = 200) then it completes reasonably quickly. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2014-11-17 20:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-17 19:39 [Bug gdb/17613] New: " dje at google dot com 2014-11-17 20:00 ` dje at google 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-17613-4717-gVMuiGpPrw@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).