public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/14321] New: find can clobber memory Date: Sun, 01 Jul 2012 18:52:00 -0000 [thread overview] Message-ID: <bug-14321-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14321 Bug #: 14321 Summary: find can clobber memory Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: cli AssignedTo: unassigned@sourceware.org ReportedBy: jan.kratochvil@redhat.com Classification: Unclassified GNU gdb (GDB) 7.4.50.20120630-cvs ./gdb ./gdb (gdb) find main,+100000000,xop_table memory clobbered past end of allocated block This code does not expect val_bytes can be huge: findcmd.c: /* Keep it simple and assume size == 'g' when watching for when we need to grow the pattern buf. */ if ((pattern_buf_end - pattern_buf + max (val_bytes, sizeof (int64_t))) > pattern_buf_size) { size_t current_offset = pattern_buf_end - pattern_buf; pattern_buf_size *= 2; pattern_buf = xrealloc (pattern_buf, pattern_buf_size); pattern_buf_end = pattern_buf + current_offset; } -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-07-01 18:52 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-01 18:52 jan.kratochvil at redhat dot com [this message] 2012-07-01 19:42 ` [Bug cli/14321] find may " jan.kratochvil at redhat dot com 2012-07-06 15:52 ` cvs-commit at gcc dot gnu.org 2012-07-06 15:55 ` jan.kratochvil at redhat dot com
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-14321-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: 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).