Your message dated Wed, 25 Oct 2006 11:49:09 -0600 (MDT)
with message-id <[EMAIL PROTECTED]>
and subject line fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: tar
Version: 1.13.93-3
Severity: normal
Hi,
tar simply dumps core with this command line:
tar -z -f foo.tar --delete bar
it doesn't matter if the archive foo.tar exists or not.
It corrupts the stack, so the backtrace isn't helpfull:
Core was generated by `tar -z -f foo.tar --delete bar'.
Program terminated with signal 6, Aborted.
0x00000025 in ?? ()
(gdb) bt
#0 0x00000025 in ?? ()
Cheers,
-- Guido
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.5-rc2-ben0-albook12
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages tar depends on:
hi libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
-- no debconf information
--- End Message ---
--- Begin Message ---
This is no longer true in tar 1.16-1.
Bdale
--- End Message ---
