Hamish's report beat mine by 25 minutes, and included
more detail as well. Please merge this one (#375925)
with #375923.
- Larry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Michael -
On Thu, Jun 01, 2006 at 10:31:41AM +0200, Michael Ablassmeier wrote:
> On Wed, May 31, 2006 at 09:47:11PM -0700, Steve Langasek wrote:
> > The attached patch fixes [typedef void (*XwStrProc)], and gives
> > me a minimally-usable package on amd64.
I can confirm this. Thanks, Steve!
> t
PAGE_SIZE patch for Debian verilog 0.8-4.1, fixing bug#411063.
If for some reason the sysconf() call fails, I think 0 is
the best possible result: it is obviously incorrect.
Steve, the same change should also be applied to 0.9.
- Larry
--- /home/ldoolitt/deb-src/verilog-0.8/vvp/main.cc
Daniel -
For both the broken.xwd and broken2.xwd files in bug #414045,
the offending operation is in libx11-1.0.3/src/ImUtil.c:505
dst++ = *src++;
and in fact it's the src pointer that is out of range.
This suggests it's "only" a DOS problem, or at worst an
information leak problem, but no dire
The root problem is integer overflow in the multiplication at
line 292 of graphicsmagick-1.1.7/coders/xwd.c. With the appended
patch, the two test cases result in the following on my amd64 sid
box:
$ gm convert broken.xwd test.png
gm convert: Memory allocation failed (broken.xwd).
$ echo $?
1
$ g
On Sat, Mar 24, 2007 at 04:29:23PM +0100, Julien Cristau wrote:
> So you're saying the remaining problem is in graphicsmagick, not Xlib?
I recommend further testing and investigation by others.
My analysis showed a clear bug in graphicsmagick, and I
posted a fix for it. When I retested, only brok
On Sat, Mar 24, 2007 at 04:29:23PM +0100, Julien Cristau wrote:
> So you're saying the remaining problem is in graphicsmagick, not Xlib?
I previously posted a patch for graphicsmagick that fixes broken.xwd.
Here is a patch for libx11 that fixes broken2.xwd.
I thought about possible ways to fixing
I have to walk away from this bug for a while. Maybe this
message can give someone else a head start.
It's quite a Heisenbug, disappearing when you put any
malloc in besides vanilla libc; I tried electric fence
and dmalloc, I understand valgrind is the same.
My comments refer to broken2.jp2. Th
On Tue, Mar 27, 2007 at 11:08:20AM -0700, [EMAIL PROTECTED] wrote:
> It's quite a Heisenbug, disappearing when you put any
> malloc in besides vanilla libc; I tried electric fence
> and dmalloc, I understand valgrind is the same.
I don't know what went wrong the first time, I tried
again and Elect
Maks -
On Thu, Aug 17, 2006 at 12:48:15AM -0700, Debian Bug Tracking System wrote:
> On Wed, Aug 16, 2006 at 05:17:34PM -0700, Larry Doolittle wrote:
> > Package: linux-2.6
> > Severity: serious
> > Justification: Policy 2.1
>
> how about if you check for duplicate bug reports!
> see #242866 for
The most recent tg3.c patch posted here (by Herbert Xu on Tue, 11 May
2004) does not apply cleanly to linux-2.6.17. No surprise, a lot has
changed in the last two years. I applied it by hand (it wasn't hard),
and I can verify that the result (freshened patch attached) compiles
without error. I c
This patch looks like it will fix the spurious error message.
Nominally tested.
--- /var/lib/dpkg/info/console-common.preinst 2006-10-15 09:25:20.0
-0700
+++ console-common.preinst 2006-10-16 08:49:46.0 -0700
@@ -58,7 +58,6 @@
WARNING: /usr/lib/kbd/ not removed - other fil
Florian Weimer's April 5 post asserts that the origin of
this bug is an integer overflow in multiplication
(clusters*fs->cluster_size).
The canonical check for such overflow (within the constructs
of ANSI C) is well known to regular readers of comp.lang.c.
It goes something like this:
#define OVE
eyck -
As the author of the patch that apparently broke your application,
this report totally baffles me. Can you confirm that downgrading
to libx11-6 version 2:1.0.3-6 removes the problem?
Are you able to patch and rebuild test versions of libx11?
If so, one quick thing to try is to put back th
Using info in apt bug #351056, I cleared my problem.
Sorry for the extra noise. Maybe someone could move
this report to apt, and merge with the above bug.
In my case, it was enough to delete some stale files
from /var/cache/apt/archives. I only had this problem
with libselinux1 and libbonobo2-0.
15 matches
Mail list logo
