natty has seen the end of its life and is no longer receiving any
updates. Marking the natty task for this ticket as "Won't Fix".
** Changed in: gmemusage (Ubuntu Natty)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** No longer affects: linuxmint
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/370735
Title:
terminated on stack smashing detected message
To manage notifications about this bug go to:
https://bugs.
** Branch linked: lp:ubuntu/gmemusage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/370735
Title:
terminated on stack smashing detected message
To manage notifications about this bug go to:
https:/
This bug was fixed in the package gmemusage - 0.2-11ubuntu1
---
gmemusage (0.2-11ubuntu1) oneiric; urgency=low
* Add debian/patches/30_stacksmash2.patch: fix stack smashing crash on
startup (LP: #370735).
-- Akkana PeckWed, 01 Jun 2011 10:02:33 -0700
** Changed in: gmemusa
I've updated the debdiff with Chris's suggestions, and fixed up the
changelog to use LP-style bug numbering. Thanks for the work on this,
I'll get it uploaded shortly.
** Changed in: gmemusage (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you a
** Changed in: gmemusage (Ubuntu)
Status: Triaged => Incomplete
** Changed in: gmemusage (Ubuntu Natty)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/370735
Ti
There is a typo in my last comment. I should have said "You hardcode
"%15s" in the format string for sscanf"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/370735
Title:
terminated on stack smashing
Hi,
Thanks for working on this. I have a couple of comments though:
- The scope of the patch seems to expand beyond the original bug. Whilst
it's perfectly ok for you to fix the additional issues, would you mind
splitting those changes in to a separate patch? (I'm referring to the
cast you added
** Patch added: "debdiff of the patch"
https://bugs.launchpad.net/ubuntu/+source/gmemusage/+bug/370735/+attachment/2151093/+files/gmemusage_0.2-11ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Also affects: gmemusage (Ubuntu Natty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/370735
Title:
terminated on stack smashing detected message
--
u
This is still an issue in Lucid. I just installed version 0.2-11 in
Lucid and got the same error.
--
terminated on stack smashing detected message
https://bugs.launchpad.net/bugs/370735
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Thanks for your work on it.
Yes, a debdiff is necessary if you want a sponsor. You can have more details on
https://wiki.ubuntu.com/MOTU/Contributing
Also, it would be nice to post this patch to Debian also, they should have the
same problem, and we can keep packages in sync.
I unsubscribe ubunt
Would a debdiff help in getting this patch accepted? I've never made a
debdiff but I can try.
--
terminated on stack smashing detected message
https://bugs.launchpad.net/bugs/370735
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Changed in: linuxmint
Status: In Progress => Triaged
--
terminated on stack smashing detected message
https://bugs.launchpad.net/bugs/370735
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
** Also affects: linuxmint
Importance: Undecided
Status: New
** Changed in: linuxmint
Importance: Undecided => Medium
** Changed in: linuxmint
Status: New => In Progress
--
terminated on stack smashing detected message
https://bugs.launchpad.net/bugs/370735
You received this
Here's a better patch: I fixed one more strcpy and one more warning, and
added a field width in the sscanf for procName.
** Attachment added: "better patch, fix the problem plus all warnings"
http://launchpadlibrarian.net/28828752/stacksmash2.diff
--
terminated on stack smashing detected mess
Building the hardy package on hardy with dpkg-buildpackage also results
in a binary that gives the stack-smashing error (though the hardy binary
package worked fine).
Building with -fno-stack-protector as part of CFLAGS makes it ignore the
stack smashing, and the program works again.
My guess (I
Confirmed, installing the squeeze deb fixes the problem for me as well
in jaunty. Curiously, building from the squeeze tarball with patches
added still crashes, so I'm not sure what they've changed.
--
terminated on stack smashing detected message
https://bugs.launchpad.net/bugs/370735
You receiv
I can confirm that this is still an issue in Jaunty, reported from linux
mint Gloria: http://forums.linuxmint.com/viewtopic.php?f=166&t=27666
chattr:
"if I ' apt-get remove gmemusage ' and grab the Debian testing/squeeze 0.2-11
i386 package and install that package via ' dpkg -i ', then gmemusage
Same error here. Worked in intrepid, broken in jaunty. Nominating for
jaunty since the program doesn't work at all now.
--
terminated on stack smashing detected message
https://bugs.launchpad.net/bugs/370735
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
20 matches
Mail list logo
