Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 61226 - Code produced by g++3 segfaults leaving no corefile
Code produced by g++3 segfaults leaving no corefile
Product: Red Hat Linux
Classification: Retired
Component: gcc3 (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2002-03-15 11:42 EST by Tor Andre Myrvoll
Modified: 2007-04-18 12:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-02 15:53:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Output from trying to run the in a GDB session (3.04 KB, text/plain)
2002-03-15 11:43 EST, Tor Andre Myrvoll
no flags Details

  None (edit)
Description Tor Andre Myrvoll 2002-03-15 11:42:01 EST
Description of Problem:
After updating my gcc3 suite to 3.0.4-1 one of my programs has started to 
segfault immidiately after starting. It doesn't even seem to enter my code, 
but crashes before main() and leaves no core.

Version-Release number of selected component (if applicable):
3.0.4-1 (Newest update from redhat)

How Reproducible:

Steps to Reproduce:
1. Compile program using g++3
2. Run program

Actual Results:
The program segfaults instantly

Expected Results:
The program should work

Additional Information:
Comment 1 Tor Andre Myrvoll 2002-03-15 11:43:39 EST
Created attachment 48644 [details]
Output from trying to run the in a GDB session
Comment 2 Neal D. Becker 2002-03-18 10:21:30 EST
I find that Hello World will segfault if linked static but dynamic is OK:

#include <iostream>
#include <stdexcept>

using std::cout;

main() {
  cout << "hello world\n";

I consider this very high priority.
Comment 3 Richard Henderson 2004-10-02 15:53:08 EDT
Fixed in gcc 3.2.

Note You need to log in before you can comment on or make changes to this bug.