387941 – media-gfx/shotwell-0.11.3 terminates when compiled with SSP

Bug 387941 - media-gfx/shotwell-0.11.3 terminates when compiled with SSP

Summary: media-gfx/shotwell-0.11.3 terminates when compiled with SSP

Status:	RESOLVED UPSTREAM

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	AMD64 Linux

Importance:	Normal normal (vote)
Assignee:	Christoph Mende (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-10-20 22:32 UTC by Alexander Tsoy
Modified:	2012-03-24 12:20 UTC (History)
CC List:	1 user (show)

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

Attachments
patch to ebuild (shotwell-0.11.5-no-ssp.patch,622 bytes, patch) 2011-10-22 14:16 UTC, Alexander Tsoy	Details \| Diff
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 Alexander Tsoy 2011-10-20 22:32:58 UTC

I'm using hardened profile. When I try to import photos from flash card shotwell terminates immediately after I open "Mass Storage Camera" folder with this message:

*** stack smashing detected ***: shotwell - terminated
shotwell: stack smashing attack in function <unknown> - terminated
Report to http://bugs.gentoo.org/

Reproducible: Always




$ gcc-config -l
 [1] x86_64-pc-linux-gnu-4.6.1 *
 [2] x86_64-pc-linux-gnu-4.6.1-hardenednopie
 [3] x86_64-pc-linux-gnu-4.6.1-hardenednopiessp
 [4] x86_64-pc-linux-gnu-4.6.1-hardenednossp
 [5] x86_64-pc-linux-gnu-4.6.1-vanilla

Comment 1 Alexander Tsoy 2011-10-21 19:09:25 UTC

Same issue with 0.11.5

Comment 2 Alexander Tsoy 2011-10-22 14:15:47 UTC

Upstream bugreport: http://redmine.yorba.org/issues/4294

Workarounds:

1. Temporary switch gcc profile to *-hardenednossp
2. Apply attached patch to ebuild

Comment 3 Alexander Tsoy 2011-10-22 14:16:32 UTC

Created attachment 290523 [details, diff]
patch to ebuild

Comment 4 Markos Chandras (RETIRED) gentoo-dev

2012-03-24 12:20:38 UTC

Upstream requested serveral details from you. Please reopen this bug when you respond to the upstream bug