Your message dated Sun, 6 Oct 2024 18:07:07 -0400
with message-id
<az3a2xmq4v2zftll3ptl2modfouzovkenye6zisf3wrcmkik3f@tktwjjoj7ozt>
and subject line Re: Bug#676691: Valgrind doesn't notice debug libs
has caused the Debian Bug report #676691,
regarding Valgrind doesn't notice debug libs
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 ow...@bugs.debian.org
immediately.)
--
676691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblua5.1-0-dbg
Version: 5.1.5-2
Severity: important
When using valgrind, it doesn't show source code line numbers in lua
shared library. Is this debuglink vs build-is issue / valgrind failure
or something else?
The same with lua5.2.
Regards,
Andrey
--- End Message ---
--- Begin Message ---
On Sun, Jun 17, 2012 at 03:02:52PM +0200, Andrey Gursky wrote:
> I've discovered the reason for such behavior and filled a bug report:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677876
Since this was an issue in valgrind, I'm closing the bug.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--- End Message ---
