FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian GCC

 
 
LinkBack Thread Tools
 
Old 11-20-2007, 06:04 PM
Török Edwin
 
Default Bug#452108: what binary packages to update?

> Note that this issue is in theory pretty serious as in principle
_any_
> binary package in the archive could be affected.

Since the abs() is optimized away on miscompilations, searching for
binaries that have the abs() symbol won't find the buggy ones.

The only reliable way to find out what packages could be affected,
is to grep for calls to abs() [I guess too many to hand-review].

Then the list could be filtered by dropping calls to abs() where
parameteres are provably positive numbers (either constants, or
unsigned types). Such a check could be implemented in static
analysis tools, like CIL, but trying to compile the entire archive
with CIL can be a challenge by itself.

How do you intend to handle this bug for stable?
Obviously updating all packages that call abs() is not a solution

A quicker way to find out could be to compile all the archive with
current gcc version. Then apply the patch that fixes the bug,
recompile the entire archive, and see which .o,.so,.a, and
executable files differ between the two. Is there a tool to automate
such a task?


--Edwin



--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 09:24 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org