0.3.3+SVN20051028-3ubuntu1 no longer works

Bug #53341 reported by Rafael Ávila de Espíndola
8
Affects Status Importance Assigned to Milestone
gcc
Invalid
Medium
vpnc (Ubuntu)
Fix Released
Undecided
William Grant

Bug Description

Binary package hint: vpnc

0.3.3+SVN20051028-2ubuntu1 work correctly, but upgrading to "-3" caused the vpn to stop working. Vpnc runs normally, set up the routes, updates resolv.conf, but the no package returns.

Dowgrading to "-2" solved the problem.

Revision history for this message
William Grant (wgrant) wrote :

Thanks for the bug report. What part of the connection fails?

Changed in vpnc:
status: Unconfirmed → Needs Info
Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

I am not sure what part fails. But it looks like the problem is with gcc or a lib. I tried to compile the "-2" and the resulting deb has the same problem as the "-3". The "-2" from the archive works correctly.

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

compiling with gcc-4.0 solved the problem

Revision history for this message
William Grant (wgrant) wrote :

Which version of GCC were you compiling it with before? GCC 4.1?

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

Yes, I was using gcc 4.1. It works with -O0 but not with -O1 and higher

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

Compiling only vpnc.c with -O0 solved the problem

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

coping setup_link to a new file and compiling only it with -O0 solved the problem.

Revision history for this message
William Grant (wgrant) wrote :

Is it GCC 4.1 that works with -O0? If so, I'll get the package fixed.

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

Yes, the problem is in compiling setup_link with gcc 4.1 and optimizations enabled. Using another gcc or the -O0 option with gcc 4.1 solves the problem.

William Grant (wgrant)
Changed in vpnc:
assignee: nobody → fujitsu
status: Needs Info → In Progress
Revision history for this message
William Grant (wgrant) wrote :

I've added a patch to ensure it's compiled with -O0, rather than -O3. Can you please check the package I've just attached to see if it works? If it does, I'll get the fix uploaded to the archive.

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

I forgot to mention that I have an AMD64 :-(
Can you post the patch? I can compile and test it.

Revision history for this message
William Grant (wgrant) wrote :
Revision history for this message
William Grant (wgrant) wrote :
Revision history for this message
William Grant (wgrant) wrote :
Revision history for this message
William Grant (wgrant) wrote :

You can build the package using the three files I just attached above.

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

it works

Revision history for this message
William Grant (wgrant) wrote :

Thanks for testing that. I'll get the package uploaded to Edgy ASAP.

Revision history for this message
William Grant (wgrant) wrote :

vpnc 0.3.3+SVN20051028-2ubuntu2 was just uploaded to Edgy, fixing the issue.

Changed in vpnc:
status: In Progress → Fix Released
Changed in gcc:
status: Unknown → Unconfirmed
Revision history for this message
William Grant (wgrant) wrote :

It appears that this may be caused by a bug in vpnc, not GCC itself. I'll attach a new version of the package in a couple of minutes with the possible bug fixed. Rafael, can you please check if it works?

Changed in vpnc:
status: Fix Released → In Progress
Revision history for this message
William Grant (wgrant) wrote :

The bits of the new package can be found at http://people.ubuntu.com.au/~fujitsu/vpnc/.

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

I am now using debian testing, it also has gcc 4.1. I compiled the package with -O1 and -O3 and it works.

But I am not sure if the sizeof patch is the responsible. sizeof(struct in_addr)) is 4 in my system. But please keep it. It is a real bug fix.

I will check if there is any remaining edgy installs at work and test it once more.

Revision history for this message
William Grant (wgrant) wrote :

Does the Debian testing version also break if using the unpatched version?

Revision history for this message
Rafael Ávila de Espíndola (rafael-espindola) wrote :

I have just tested in a edgy chroot and it works correctly.

Maybe a GCC bug was fixed in more recent packages...

Thanks.

Revision history for this message
William Grant (wgrant) wrote :

Which version did you test in the Edgy chroot? One without the optimisation patch I added in 0.3.3+SVN20051028-3ubuntu2?

Changed in gcc:
status: Unconfirmed → Unknown
Changed in gcc:
status: Unknown → Needs Info
Revision history for this message
Ante Karamatić (ivoks) wrote :

OK to close this one?

Revision history for this message
William Grant (wgrant) wrote :

No. It's still a bug, and it's only been a month since the last response. Bugs don't expire.

Revision history for this message
Joel Stanley (shenki) wrote :

wfm on a machine that has been dist-upgraded throughout the edgy release cycle, as well as a fresh install from a edgy-rc1 alternate cd.

doing a debuild on my machine also compiles me a deb with no errors.

Changed in gcc:
status: Needs Info → Rejected
William Grant (wgrant)
Changed in vpnc:
status: In Progress → Fix Released
Revision history for this message
Daniel J Blueman (danielblueman) wrote :

I can confirm this bug is still at large on gutsy with vpnc-0.4.0-3ubuntu1 on amd64. Building vpnc.c with -O0 does allow it to correctly connect, so I'll look deeper into it.

I posted debug logs and requested where to start looking to the author of vpnc, but got no response.

Changed in gcc:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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