-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-03-03 14:26, Moritz Muehlenhoff wrote:
On Fri, Mar 01, 2013 at 04:08:18PM -0800, Russ Allbery wrote:
At this point in the release process, I really think upgrading
with _FORTIFY_SOURCE disabled is the correct fix. Just
increasing a buffer
IOhannes m zmoelnig zmoel...@iem.at writes:
since i'm not in the position of uploading the package myself, i'd
like to kindly ask one of you DMs (alessio, paul?) to help me out here.
I've got it, thanks. Building for upload now. (I haven't done enough to
help out with the wheezy release yet,
On Fri, Mar 01, 2013 at 04:08:18PM -0800, Russ Allbery wrote:
At this point in the release process, I really think upgrading with
_FORTIFY_SOURCE disabled is the correct fix. Just increasing a buffer
size is usually not a good idea; that's the sort of change that can paper
over a deeper
At this point in the release process, I really think upgrading with
_FORTIFY_SOURCE disabled is the correct fix. Just increasing a buffer
size is usually not a good idea; that's the sort of change that can paper
over a deeper problem without actually solving it, just temporarily hiding
it. At
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-10-28 06:44, Matthew Grant wrote:
Talk to upstream before turning on _FORTIFY_SOURCE please.
i double-checked and tried to run a fairly big patch and couldn't
reproduce the crash.
do you think you could produce a minimal patch showing
Hi Matthew,
can you please try if the attached patch (bigger static buffer size)
fixes the issue, when fortify is still turned on? (We really want to
fortify.)
Thanks in advance,
Roland
--- puredata-0.43.2.orig/src/m_pd.h
+++ puredata-0.43.2/src/m_pd.h
@@ -57,7 +57,7 @@ extern C {
#include
Package: puredata
Followup-For: Bug #690410
Recompiled puredata with the following 2 lines added to the top of
debian/rules:
# Stop problems with puredata crashing due to buffer space issues?
export DEB_BUILD_MAINT_OPTIONS=hardening=+format,-fortify,+stackprotector,+relro
This turns off
Hi Matthew,
Thanks for the report, and sorry to hear you have trouble with your
valuable project.
I have no objection with rebuilding everything with FORTIFY_SOURCE=0,
but it seems it would be the bug you triggered is fairly rare, and it
would be nice to:
- have a minimal patch or set of
Package: puredata
Version: 0.43.2-4
Severity: grave
I have a large puerdata patch using GEM that was working early on last year.
At the moment it is crashing on start with calls to __fortify_fail() in libc.
There are two pds running, one handling sound and wiimote input, and a slave
doing GEM
9 matches
Mail list logo
