Your message dated Thu, 04 Mar 2010 10:45:44 +0200
with message-id <[email protected]>
and subject line Bug#216000 Close
has caused the Debian Bug report #216000,
regarding wiggle: Calls abort
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
216000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216000
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wiggle
Version: 0.6-3
Severity: normal
When applying a complicated reject with:
wiggle -v Gallery.class.php Gallery.class.php.rej
At the very least, it could print a more user friendly error
to indicate what went wrong.
Program received signal SIGABRT, Aborted.
0x400456c1 in kill () from /lib/libc.so.6
(gdb) bt
#0 0x400456c1 in kill () from /lib/libc.so.6
#1 0x40045465 in raise () from /lib/libc.so.6
#2 0x400469db in abort () from /lib/libc.so.6
#3 0x0804f85e in already_applied (cs1=0x80c9780, cs2=0x80ca048, start=
{pos = 41539, in_a = 1, c1 = 104, c2 = 291}, end=
{pos = 41550, in_a = 1, c1 = 106, c2 =
293},
a=0xbffffc94, b=0xbffffc9c,
c=0xbffffca4) at merge.c:793
#4 0x0804faac in print_merge (out=0x40143d80, a=0xbffffc94,
b=0xbffffc9c,
c=0xbffffca4, c1=0x80c9780, c2=0x80ca048, words=0) at
merge.c:847
#5 0x0804a9e7 in main (argc=4, argv=0xbffffd64) at wiggle.c:621
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux jade141 2.4.21-5-686 #1 Sun Aug 24 15:25:33 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages wiggle depends on:
ii libc6 2.3.2-7 GNU C Library: Shared libraries an
-- no debconf information
--- End Message ---
--- Begin Message ---
Reason for close:
Old bug from 2003. No 'moreinfo' available to investigate this in
detail. Please open new bug if the problem is found again.
--- End Message ---
