public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: gcc@gcc.gnu.org
Subject: [tree-ssa] Tree browser unstable ?
Date: Thu, 03 Apr 2003 14:33:00 -0000	[thread overview]
Message-ID: <vpqhe9fzqbq.fsf@ecrins.imag.fr> (raw)

Hi,

I'm using  the tree-ssa branch of  GCC, and starting to  play with the
tree        browser        to        understand       the        code.
(http://gcc.gnu.org/projects/tree-ssa/tree-browser.html). 

It is  an interesting option,  but I find  it very unstable.  I rather
often get error messages like this :

,----
| (gdb) p browse_tree (fndecl)
| 
| Tree Browser
| myfunc
| 
| /home/moy/essais/c++/hello.cc:6: internal compiler error: in walk_tree, at 
|    tree-inline.c:1557
| Please submit a full bug report,
| with preprocessed source if appropriate.
| See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
| 
| Program exited with code 01.
| The program being debugged stopped while in a function called from GDB.
| When the function (browse_tree) is done executing, GDB will silently
| stop (instead of continuing to evaluate the expression containing
| the function call).
`----

So,  my question  is :  Am I  doing something  wrong, or  is  the tree
browser supposed to be robust to any kinds of use (So, should I make a
bug report each time I get this kind of message ?)

-- 
Matthieu

             reply	other threads:[~2003-04-03 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 14:33 Matthieu Moy [this message]
2003-04-03 16:09 ` Diego Novillo
2003-04-03 16:33   ` Pop Sébastian

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=vpqhe9fzqbq.fsf@ecrins.imag.fr \
    --to=matthieu.moy@imag.fr \
    --cc=gcc@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).