public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brian.amberg at unibas dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/48667] New: [ skipping N instantiation contexts ] Skips exactly those which are of interest to me
Date: Mon, 18 Apr 2011 14:53:00 -0000	[thread overview]
Message-ID: <bug-48667-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [ skipping N instantiation contexts ] Skips exactly
                    those which are of interest to me
           Product: gcc
           Version: 4.5.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: brian.amberg@unibas.ch


A new gcc feature seems to be to emit [ skipping N instantiation contexts ]
after the first 10 contexts. I could not find a way to change 10 to another
value.

The problem is, that when using the terrific, but extremely templated eigen
library the instantiation contexts where my own bug happens are not shown, only
those within the library headers and my main routine, and I can not easily
debug my program.

This is very annoying.

kind regards,

Brian


             reply	other threads:[~2011-04-18 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 14:53 brian.amberg at unibas dot ch [this message]
2011-09-25 12:50 ` [Bug c++/48667] " paolo.carlini at oracle dot com
2011-09-25 15:18 ` manu at gcc dot gnu.org
2011-09-25 15:25 ` paolo.carlini at oracle dot com

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=bug-48667-4@http.gcc.gnu.org/bugzilla/ \
    --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).