321257 – sys-libs/db fails to compile with gcc 4.5.0 (tar buffer overflow detected)

Bug 321257 - sys-libs/db fails to compile with gcc 4.5.0 (tar buffer overflow detected)

Summary: sys-libs/db fails to compile with gcc 4.5.0 (tar buffer overflow detected)

Status:	RESOLVED DUPLICATE of bug 317139

Alias:	None

Product:	Gentoo Security
Classification:	Unclassified
Component:	Vulnerabilities (show other bugs)
Hardware:	All Linux

Importance:	High major (vote)
Assignee:	Gentoo Security

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-05-23 22:59 UTC by David Carlos Manuelda
Modified:	2010-05-23 23:41 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Compile log (sys-libs:db-4.7.25_p4:20100523-212954.log,2.69 KB, text/plain) 2010-05-23 23:00 UTC, David Carlos Manuelda	no flags	Details
Backtrace (backtrace,21.74 KB, text/plain) 2010-05-23 23:02 UTC, David Carlos Manuelda	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

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

Description David Carlos Manuelda 2010-05-23 22:59:01 UTC

I report this here because it seems a buffer overflow, and I think it could be worse than only not compile sys-libs/db. If it's not than important, please move it where it belongs :)

Compiling with gcc 4.5.0, glibc 2.11.1 (amd64 10.0/desktop/kde profile)
(compile log attached after).

Should you need more info, request it.

Reproducible: Always

Comment 1 David Carlos Manuelda 2010-05-23 23:00:28 UTC

Created attachment 232639 [details]
Compile log

This is the full compile log

Comment 2 David Carlos Manuelda 2010-05-23 23:02:10 UTC

Created attachment 232641 [details]
Backtrace

I got also in konsole a little backtrace wich seems not added to compile log, so I attach too.

Comment 3 David Carlos Manuelda 2010-05-23 23:05:08 UTC

the same happens when trying to compile libpcre

Comment 4 David Carlos Manuelda 2010-05-23 23:41:22 UTC

OK, seems a dup of #317139

*** This bug has been marked as a duplicate of bug 317139 ***