public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/21322] O2 and O3 memory access error - compiled program - incorrect debug output
Date: Sun, 01 May 2005 19:13:00 -0000	[thread overview]
Message-ID: <20050501191326.22464.qmail@sourceware.org> (raw)
In-Reply-To: <20050501191141.21322.fastsnip-gcc@yahoo.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-01 19:13 -------
What version of gdb?
Read <http://gcc.gnu.org/gcc-4.0/changes.html>:
GCC now generates location lists by default when compiling with debug  info and optimization.

GDB 6.0 and older crashes when it sees location lists.  GDB 6.1 or later is needed to debug binaries 
containing location  lists.

When you are trying to view a value of a variable in a part of  a function where it has no location (for 
example when the variable  is no longer used and thus its location was used for something  else) GDB 
will say that it is not available.

-- 


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


  reply	other threads:[~2005-05-01 19:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01 19:11 [Bug c/21322] New: " fastsnip-gcc at yahoo dot com
2005-05-01 19:13 ` pinskia at gcc dot gnu dot org [this message]
2005-05-01 19:19 ` [Bug c/21322] " pinskia at gcc dot gnu dot org
2005-05-01 19:21 ` fastsnip-gcc at yahoo dot com
2005-05-01 19:28 ` pinskia at gcc dot gnu dot org
2005-05-01 19:34 ` fastsnip-bcard1 at yahoo dot com
2005-05-01 19:40 ` pinskia at gcc dot gnu dot org
2005-05-01 20:04 ` fastsnip-bcard1 at yahoo dot com
2005-05-01 20:05 ` fastsnip-bcard1 at yahoo dot com
2005-05-01 20:25 ` fastsnip-bcard1 at yahoo dot com
2005-05-01 20:30 ` fastsnip-bcard1 at yahoo dot com
2005-05-03 20:17 ` [Bug other/21322] " jsm28 at gcc dot gnu dot org
2005-07-06 14:29 ` 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=20050501191326.22464.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).