I believe that technically, the public API hasn't been changed. The API
doesn't specify whether the returned pointer should be free()d, and is
broken by sometimes returning a pointer that needs to be free()d and
sometimes one that mustn't, so one must never free() the pointer. Some
distributions de
IMO, this is not an acceptable solution.
th_get_pathname() is part of the public API, and must not change behaviour
unless the major version of libtar is changed. This severely breaks
compatibility
with existing programs, and affects portability a lot.
If a program uses libtar 1.2.11 on Solaris,
This bug was fixed in the package libtar - 1.2.11-8
---
libtar (1.2.11-8) unstable; urgency=low
* libtool.patch: Set SHELL to the configured shell in those Makefile.in
where libtool is used; otherwise libtool fails when /bin/sh is dash
but bash is expected (Closes: #621935).
** Branch linked: lp:debian/libtar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/41804
Title:
Major memory leak
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
No, it's not resolved.
I was applying this patch to the package in Debian, but after looking a
bit closer I'm not so sure anymore. The problem that the patch attempts
to solve is that th_get_pathname() in some cases (namely, if
gnu_longname is not set) strdup()s a local buffer. But th_get_pathname
Is this issue resolved, or are there still leaks in the current
distribution?
Thanks,
Mike
--
Major memory leak
https://bugs.launchpad.net/bugs/41804
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bug
** Changed in: libtar (Ubuntu)
Status: Incomplete => Confirmed
--
Major memory leak
https://bugs.launchpad.net/bugs/41804
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
Has this issue been fixed already?
** Changed in: libtar (Ubuntu)
Status: New => Incomplete
--
Major memory leak
https://bugs.launchpad.net/bugs/41804
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ub
