public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/61905] New: zero variable length array bound in cp-demangle.c cplus_demangle_print_callback
@ 2014-07-25  8:13 zeccav at gmail dot com
  2014-09-04  9:48 ` [Bug other/61905] " mpolacek at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: zeccav at gmail dot com @ 2014-07-25  8:13 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61905

            Bug ID: 61905
           Summary: zero variable length array bound in cp-demangle.c
                    cplus_demangle_print_callback
           Product: gcc
           Version: 4.9.1
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zeccav at gmail dot com

The sanitizer claims that compiling the testsuite files pr21255-2-mb.c and
pr21255-4.c and pr21255-3.c and pr21255-2-ml.c
a zero variable length array bound occurs
"../../gcc-4.9.1/libiberty/cp-demangle.c:4039:40: runtime error: 
variable length array bound evaluates to non-positive value 0"

Same at line 4040
"    __extension__ struct d_saved_scope scopes[dpi.num_saved_scopes];
    __extension__ struct d_print_template temps[dpi.num_copy_templates];"


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-06-26 20:30 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-25  8:13 [Bug c/61905] New: zero variable length array bound in cp-demangle.c cplus_demangle_print_callback zeccav at gmail dot com
2014-09-04  9:48 ` [Bug other/61905] " mpolacek at gcc dot gnu.org
2014-09-28  9:30 ` [Bug target/61905] " trippels at gcc dot gnu.org
2014-10-30 10:39 ` jakub at gcc dot gnu.org
2015-06-26 20:01 ` jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub at gcc dot gnu.org

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).