Bug 25744 - typename causes segmentation fault
Summary: typename causes segmentation fault
Status: RESOLVED DUPLICATE of bug 23797
Alias: None
Product: gcc
Classification: Unclassified
Component: c++ (show other bugs)
Version: 3.4.4
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-10 22:30 UTC by William K. Foster
Modified: 2006-01-10 22:40 UTC (History)
6 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments
The test.ii file that was too big for the text of the bug report. (37.13 KB, text/plain)
2006-01-10 22:31 UTC, William K. Foster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description William K. Foster 2006-01-10 22:30:25 UTC
gcc -v:

Reading specs from /tools/new/lib/gcc/i686-pc-linux-gnu/3.4.4/specs
Configured with: ../configure --enable-threads=posix --prefix=/tools/new --enable-language=c,c++,java --disable-checking --enable-shared
Thread model: posix
gcc version 3.4.4


Invoke gcc simply as:

gcc test.cc

Where test.cc is below.

test.cc: In function `void test()':
test.cc:10: internal compiler error: Segmentation fault
Please submit a full bug report.
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.



-------------------------test.cc------------------------------------

#include <map>
using namespace std;

void
test()
{
  map<int, int> testMap;
  map<int, int>::iterator itr = testMap.begin();

  testMap.insert(itr,
                 /* Delete next 'typename' to avoid crash */
                 typename map<int, int>::value_type(4, 3));
}

-----------------------test.ii---------------------------------------------

I'd give it to you but bugzilla complains that the report is longer than 64k.
Comment 1 William K. Foster 2006-01-10 22:31:23 UTC
Created attachment 10611 [details]
The test.ii file that was too big for the text of the bug report.
Comment 2 Andrew Pinski 2006-01-10 22:40:13 UTC

*** This bug has been marked as a duplicate of 23797 ***
Comment 3 Wolfgang Bangerth 2006-01-10 22:40:49 UTC
Confirmed, but this is already fixed as of 3.4.6 20060102 (prerelease)
W.