Opened 9 years ago
Closed 9 years ago
#45853 closed defect (invalid)
gcc48: simple program crashes with Segmentation fault: 11
Reported by: | trac-1948@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.2 |
Keywords: | yosemite | Cc: | larryv (Lawrence Velázquez) |
Port: | gcc48 |
Description
This worked fine with 2.3.1 on Mavericks.
#/tmp/ramdisk> cat t.cc #include <sstream> int main() { std::ostringstream oss; oss << " location "; return 0; } #/tmp/ramdisk> g++-mp-4.8 t.cc #/tmp/ramdisk> ./a.out Segmentation fault: 11 #/tmp/ramdisk> g++ t.cc #/tmp/ramdisk> ./a.out #/tmp/ramdisk> which g++-mp-4.8 /opt/local/bin/g++-mp-4.8 #/tmp/ramdisk> which g++ /usr/bin/g++
Change History (10)
comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | yosemite added |
---|---|
Owner: | changed from macports-tickets@… to mww@… |
Port: | gcc48 added |
Summary: | Something broken in GCC 4.8 port on Yosemite → gcc48: simple program crashes with Segmentation fault: 11 |
comment:2 Changed 9 years ago by trac-1948@…
Haven't checked with other versions of GCC. I just noticed that this issue does not occur on my other computer. Which is strange, I've got two Macs, both recently installed from scratch with Yosemite and MacPorts 2.3.2, I'll try to find a difference...
comment:3 Changed 9 years ago by trac-1948@…
On one machine Xcode 6.1 was installed from the App Store, on the other it was downloaded from the developer page (but still 6.1 final), can't quite imagine how that would make a difference though.
comment:4 Changed 9 years ago by trac-1948@…
Is there a possibility to retro-actively determine in which order the ports were installed? This would not be the first time that it made an important difference.
comment:5 follow-up: 6 Changed 9 years ago by Veence (Vincent)
Does not happen here on my MBA with Yosemite and Xcode 6.1
Air > cat > t.cc #include <sstream> int main() { std::ostringstream oss; oss << " location "; return 0; } Air > Air > g++-mp-4.8 t.cc Air > ./a.out Air >
comment:6 Changed 9 years ago by larryv (Lawrence Velázquez)
Cc: | larryv@… added |
---|
I can’t reproduce this, either. Could you attach a crash log?
comment:7 Changed 9 years ago by larryv (Lawrence Velázquez)
Also, what does port installed gcc48
say?
comment:8 Changed 9 years ago by trac-1948@…
Ok, it seems to be gcc 4.8.3_0 vs. 4.8.3_1, I'll double check though.
comment:9 follow-up: 10 Changed 9 years ago by trac-1948@…
Yepp, 4.8.3_1 fixed it. Must have been updated in the few hours between installing the first and the second computer... Sorry for the noise.
comment:10 Changed 9 years ago by larryv (Lawrence Velázquez)
Resolution: | → invalid |
---|---|
Status: | new → closed |
No worries.
Are other versions of MacPorts gcc affected as well, or just gcc48?