public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "l dot jirkovsky at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38625] Segmentation fault when dereferencing valid pointer, probably REGRESSION
Date: Thu, 29 Jan 2009 11:19:00 -0000	[thread overview]
Message-ID: <20090129111914.10012.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38625-16054@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from l dot jirkovsky at gmail dot com  2009-01-29 11:19 -------
First, I'd like to thank you for doing this hard work and for finding out which
patch causes this problem.

Anyway I've done more investigation to the problematic code.

The problem actually begins in
CachedFileImageIteratorBase::operator*()

In correct build (without optimizations, with debugging enabled or with
"--param inline-unit-growth=60") the currentRow pointer is pointer to
"ordinary" array, I'm guessing it's array of unsigned shorts.

But in segfaulting build my debugger (gdb) shows me, that currentRow is:
vigra::TinyVectorBase<unsigned char, 3, unsigned char [3],
vigra::TinyVector<unsigned char, 3> >
which _data structure doesn't exist in memory. Because it deems really weird
I'm not sure the debugger was right (it was run with higly optimized code when
only some parts of enblend actually had debugging information on).

However if I'm wrong in previous statement, the currentRow should still be
valid. I'd took if I was trying to access, lets say, currentRow[1000] which
could be out of array bounds, but this code segfaults when I'm trying to access
currentRow[0].


-- 


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


  parent reply	other threads:[~2009-01-29 11:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-25 10:12 [Bug c++/38625] New: " l dot jirkovsky at gmail dot com
2008-12-25 15:38 ` [Bug c++/38625] " pinskia at gcc dot gnu dot org
2008-12-25 17:27 ` l dot jirkovsky at gmail dot com
2008-12-25 18:08 ` l dot jirkovsky at gmail dot com
2008-12-25 18:10 ` pinskia at gcc dot gnu dot org
2008-12-25 18:52 ` l dot jirkovsky at gmail dot com
2009-01-10 16:42 ` l dot jirkovsky at gmail dot com
2009-01-10 16:47 ` l dot jirkovsky at gmail dot com
2009-01-11 23:32 ` hjl dot tools at gmail dot com
2009-01-11 23:33 ` hjl dot tools at gmail dot com
2009-01-11 23:47 ` hjl dot tools at gmail dot com
2009-01-29 11:19 ` l dot jirkovsky at gmail dot com [this message]
2010-01-02 19:40 ` rguenth 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=20090129111914.10012.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).