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/17612] New: gdb should be able to clip large memory reads to a certain size
Date: Mon, 17 Nov 2014 18:21:00 -0000	[thread overview]
Message-ID: <bug-17612-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17612
           Summary: gdb should be able to clip large memory reads to a
                    certain size
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

Someone on irc was having a problem printing a VLA (gdb ran out of memory) and
that got me wondering how gdb handles printing of large objects.

#include <stdlib.h>

struct big { char foo[1 * 1024 * 1024 * 1024]; };

int
main ()
{
  struct big *p = malloc (sizeof (*p));
  return 0;
}

Printing *p takes forever.
Plus it's not interruptable.

So there's two bugs here:
1) we should provide a way to clip the amount of memory read, akin to how we
clip how much we print with "set print elements".  Maybe we could use the same
parameter, I'm not sure.
2) this should be interruptable.
[I'll file a separate bug for this in a bit.]

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


             reply	other threads:[~2014-11-17 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 18:21 dje at google dot com [this message]
2014-11-17 19:40 ` [Bug gdb/17612] " dje at google dot com
2014-11-17 20:04 ` dje at google dot com
2020-04-06 18:29 ` ssbssa 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-17612-4717@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).