Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA/HPUX] somread.c: avoid stack overflow
Date: Wed, 04 Oct 2006 18:25:00 -0000	[thread overview]
Message-ID: <20061004182505.GH23247@adacore.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

Hello,

A customer of ours ran into a GDB crash that was caused by a stack
overflow. Their executables are very large, and it turned out when
we started debugging that the overflow happened during an alloca
besides which there already was a FIXME:.

We replace the calls to alloca by a call to xmalloc followed by
make_cleanup and the problem was gone.

2006-10-04  Joel Brobecker  <brobecker@adacore.com>

        * somread.c (som_symtab_read): Avoid using alloca for potentially
        large buffers.

Tested on pa-hpux, no regression.

OK to commit?

Thanks,
-- 
Joel

[-- Attachment #2: som.diff --]
[-- Type: text/plain, Size: 1525 bytes --]

Index: somread.c
===================================================================
RCS file: /cvs/src/src/gdb/somread.c,v
retrieving revision 1.30
diff -u -p -r1.30 somread.c
--- somread.c	1 Mar 2006 05:47:46 -0000	1.30
+++ somread.c	4 Oct 2006 18:20:41 -0000
@@ -88,15 +88,22 @@ som_symtab_read (bfd *abfd, struct objfi
 
   number_of_symbols = bfd_get_symcount (abfd);
 
-  /* FIXME (alloca): could be quite large. */
-  buf = alloca (symsize * number_of_symbols);
+  /* Allocate a buffer to read in the debug info.
+     We avoid using alloca because the memory size could be so large
+     that we could hit the stack size limit.  */
+  buf = xmalloc (symsize * number_of_symbols);
+  make_cleanup (xfree, buf);
   bfd_seek (abfd, obj_som_sym_filepos (abfd), SEEK_SET);
   val = bfd_bread (buf, symsize * number_of_symbols, abfd);
   if (val != symsize * number_of_symbols)
     error (_("Couldn't read symbol dictionary!"));
 
-  /* FIXME (alloca): could be quite large. */
-  stringtab = alloca (obj_som_stringtab_size (abfd));
+  /* Allocate a buffer to read in the som stringtab section of
+     the debugging info.  Again, we avoid using alloca because
+     the data could be so large that we could potentially hit
+     the stack size limitat.  */
+  stringtab = xmalloc (obj_som_stringtab_size (abfd));
+  make_cleanup (xfree, stringtab);
   bfd_seek (abfd, obj_som_str_filepos (abfd), SEEK_SET);
   val = bfd_bread (stringtab, obj_som_stringtab_size (abfd), abfd);
   if (val != obj_som_stringtab_size (abfd))

             reply	other threads:[~2006-10-04 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 18:25 Joel Brobecker [this message]
2006-10-04 19:32 ` Mark Kettenis
2006-10-04 21:38   ` Joel Brobecker

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=20061004182505.GH23247@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    /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