Ubuntu
gcc-4.2 package

[PR35447] gcc (x86_64) crashes when compiling udev with -std=c99

Bug #276685 reported by Alan Jenkins
12
Affects Status Importance Assigned to Milestone
gcc
Fix Released
Medium
gcc-4.2 (Ubuntu)
Won't Fix
Low
Unassigned
Hardy
Won't Fix
Undecided
Unassigned
Jaunty
Won't Fix
Low
Unassigned
gcc-4.3 (Ubuntu)
Won't Fix
Low
Unassigned
Hardy
Won't Fix
Undecided
pavel
Jaunty
Won't Fix
Low
Unassigned
gcc-4.4 (Ubuntu)
Fix Released
Undecided
Unassigned
Hardy
Invalid
Undecided
Unassigned
Jaunty
Invalid
Undecided
Unassigned
gcc-snapshot (Ubuntu)
Fix Released
Low
Matthias Klose
Hardy
Fix Released
Undecided
Unassigned
Jaunty
Invalid
Low
Matthias Klose

Bug Description

Binary package hint: gcc-4.2

I tried compiling a version of udev based on release 127. When I tried adding "-std=c99", it crashed, and popped up an automatic bug report dialog.

...
libudev-device.c:368: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token
libudev-device.c:372: error: expected ‘{’ at end of input
libudev-device.c: In function ‘udev_device_new_from_devpath’:
libudev-device.c:372: error: expected declaration or statement at end of input
libudev-device.c:372: confused by earlier errors, bailing out
Preprocessed source stored into /tmp/ccIQunVC.out file, please attach this to your bugreport.

$ lsb_release -r
Release: 8.04
$ apt-cache policy gcc
gcc:
  Installed: 4:4.2.3-1ubuntu6

ProblemType: Crash
Architecture: amd64
Date: Wed Oct 1 10:55:12 2008
Dependencies:
 libgcc1 1:4.2.3-2ubuntu7
 gcc-4.2-base 4.2.3-2ubuntu7
 libc6 2.7-10ubuntu4
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gcc/x86_64-linux-gnu/4.2.3/cc1
Package: cpp-4.2 4.2.3-2ubuntu7
PackageArchitecture: amd64
SourcePackage: gcc-4.2
Uname: Linux 2.6.27-rc5-00322-gb84d508 x86_64

Revision history for this message
Alan Jenkins (aj504) wrote :
Matthias Klose (doko)
Changed in gcc-4.2:
importance: Undecided → Low
status: New → Triaged
Changed in gcc-4.3:
importance: Undecided → Low
status: New → Triaged
Changed in gcc-snapshot:
importance: Undecided → Low
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gcc:
status: Unknown → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

Subscribed motu-sru, for ack'ing the gcc-snapshot hardy-proposed upload. Please set appropriate tasks and clarify jaunty status.

Bug Watch Updater (bug-watch-updater)
Changed in gcc:
status: Confirmed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Matthias, tasks/jaunty status please.

motu-sru, fine for you?

Revision history for this message
Devid Antonio Filoni (d.filoni) wrote :

motu-sru ACK.

Revision history for this message
Martin Pitt (pitti) wrote :

Matthias, please update the jaunty task states for this; I'll accept gcc-snapshot for hardy now, but what about gcc-4.{2,3}?

Changed in gcc-snapshot:
assignee: nobody → doko
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted gcc-snapshot into hardy-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

pavel (gchoty)
Changed in gcc-4.3:
assignee: nobody → gchoty
Revision history for this message
Martin Pitt (pitti) wrote :

Any testers on the -proposed packages? What's the status in Jaunty?

Revision history for this message
Matthias Klose (doko) wrote :

gcc-snapshot in hardy installs fine, test results look ok, works as expected.

Revision history for this message
Matthias Klose (doko) wrote :

I'll update gcc-snapshot with the 4.4.1 release expected next week

Martin Pitt (pitti)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gcc-snapshot - 20090125-0ubuntu1

---------------
gcc-snapshot (20090125-0ubuntu1) hardy-proposed; urgency=low

  * Update to SVN 20090125 from the gcc-4_3-branch. Corresponding to
    the GCC-4.3.3 release. LP: #276685.

 -- Matthias Klose <email address hidden> Sun, 25 Jan 2009 12:34:01 +0100

Changed in gcc-snapshot (Ubuntu Hardy):
status: Fix Committed → Fix Released
Revision history for this message
Matthias Klose (doko) wrote :

"Fixed for 4.4.0; not fixing on prior release branches because the fragility of
this area of error recovery means there's a risk of changing one ICE-on-invalid
to another which would be inappropriate there."

Changed in gcc-4.4 (Ubuntu):
status: New → Fix Released
Changed in gcc-4.4 (Ubuntu Hardy):
status: New → Invalid
Changed in gcc-4.4 (Ubuntu Jaunty):
status: New → Invalid
Changed in gcc-snapshot (Ubuntu):
status: Triaged → Fix Released
Changed in gcc-snapshot (Ubuntu Jaunty):
status: Triaged → Invalid
Changed in gcc-4.3 (Ubuntu Jaunty):
status: Triaged → Won't Fix
Changed in gcc-4.3 (Ubuntu Hardy):
status: New → Won't Fix
Changed in gcc-4.3 (Ubuntu):
status: Triaged → Won't Fix
Changed in gcc-4.2 (Ubuntu Jaunty):
status: Triaged → Won't Fix
Matthias Klose (doko)
Changed in gcc-4.2 (Ubuntu Hardy):
status: New → Won't Fix
Changed in gcc-4.2 (Ubuntu):
status: Triaged → Won't Fix
Bug Watch Updater (bug-watch-updater)
Changed in gcc:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.