public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29804] segfault with -fbounds-check on allocatable derived type components
Date: Tue, 10 Jul 2007 13:43:00 -0000	[thread overview]
Message-ID: <20070710134319.8934.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29804-9410@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from jvdelisle at verizon dot net  2007-07-10 13:43 -------
Subject: Re:  segfault with -fbounds-check on allocatable
 derived type components


Have you looked with valgrind or similar to see if there are errors occurring?

Please definitely put in the testsuite.  There may be something we don't see
yet 
going on here.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29804


  parent reply	other threads:[~2007-07-10 13:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 21:15 [Bug fortran/29804] New: " sfilippone at uniroma2 dot it
2006-11-11 21:16 ` [Bug fortran/29804] " sfilippone at uniroma2 dot it
2006-11-11 22:14 ` burnus at gcc dot gnu dot org
2006-11-11 22:31 ` burnus at gcc dot gnu dot org
2006-11-11 22:32 ` burnus at gcc dot gnu dot org
2006-11-11 22:53 ` pault at gcc dot gnu dot org
2006-11-11 23:12 ` pault at gcc dot gnu dot org
2007-07-07 19:07 ` dfranke at gcc dot gnu dot org
2007-07-10 13:21 ` tkoenig at gcc dot gnu dot org
2007-07-10 13:43   ` Jerry DeLisle
2007-07-10 13:43 ` jvdelisle at verizon dot net [this message]
2007-07-12 10:59 ` fxcoudert at gcc dot gnu dot org
2007-07-12 11:16 ` fxcoudert at gcc dot gnu 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=20070710134319.8934.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).