public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/17044] [3.5 Regression] libgcc2.c:169: internal compiler error: Segmentation fault
Date: Tue, 24 Aug 2004 20:00:00 -0000	[thread overview]
Message-ID: <20040824200042.6783.qmail@sourceware.org> (raw)
In-Reply-To: <20040816015952.17044.danglin@gcc.gnu.org>


------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca  2004-08-24 20:00 -------
Subject: Re:  [3.5 Regression] libgcc2.c:169: internal c

> > The exception occurs in the following call to free:
> > 
> > Breakpoint 13, 0x400000000031e350 in thread_block (bb=0x800003fffeacd8c0)
> >     at ../../gcc/gcc/tree-ssa-threadupdate.c:381
> > 381           free (rd);
> > (gdb) bt
> > #0  0x400000000031e350 in thread_block (bb=0x800003fffeacd8c0)
> >     at ../../gcc/gcc/tree-ssa-threadupdate.c:381
> OK.  That means there's got to be a memory management error of some
> kind.  I wonder if we're freeing GC'd memory or something stupid like
> that.

That might be the case although I didn't actually determine how the
object was created.  I know the fault occurred for i = 0 and all = false.

One problem is that the varray is a local and it's created and
managed using VARRAY macros that use GC.  There's also a missing
"struct" in the call to xcalloc.

I have an alternate fix that uses NOGC macros and VARRAY_FREE if
it's preferable to use malloc for the allocation of the varray.

Dave


-- 


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


  parent reply	other threads:[~2004-08-24 20:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16  1:59 [Bug middle-end/17044] New: " danglin at gcc dot gnu dot org
2004-08-16  2:03 ` [Bug middle-end/17044] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-08-16  2:11 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-16  4:18 ` danglin at gcc dot gnu dot org
2004-08-16  6:07 ` law at redhat dot com
2004-08-16 14:40 ` danglin at gcc dot gnu dot org
2004-08-17  5:26 ` pinskia at gcc dot gnu dot org
2004-08-17  5:44 ` law at redhat dot com
2004-08-17 16:27 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-17 17:38 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-17 20:49 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-18 15:36 ` pinskia at gcc dot gnu dot org
2004-08-24 19:48 ` law at redhat dot com
2004-08-24 20:00 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2004-08-24 20:04 ` law at redhat dot com
2004-08-24 20:59 ` cvs-commit at gcc dot gnu dot org
2004-08-24 21:04 ` pinskia 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=20040824200042.6783.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).