commit 8b1961511c93962ea2a9b918af8e9c32e3c24d71
Author: Balint Reczey
Date: Thu Nov 28 13:34:21 2019 +0100
Don't look for debug alt file in debug image if it is already found
With dwz the .gnu_debuglink section may appear duplicated in the
debug file referenced originally in
It was a bit of a struggle to get this reproduced. Installing debuginfo
(dbgsym) packages is not the simplest thing. But once you finally manage
then you can indeed replicate it simply with: valgrind/vg-in-place -v
/usr/bin/gio ~
--3475-- Reading syms from /usr/bin/gio
--3475-- Considering
(In reply to Balint Reczey from comment #4)
> Please see the linked original bug for the reproducer.
I looked at
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1848211 but I
still don't fully understand how/why/when this happens.
There is some confusion because the patch is for
Is this still a real problem?
I am not sure I understand how this can happen:
With dwz the .gnu_debuglink section may appear duplicated in the
debug file referenced originally in the .gnu_debuglink section.
I assume that is meant to say .gnu_debugaltlink. But if you somehow got
a
Yes, there was one testcase that wasn't handled by the patch.
There is an updated patch that handles both the original file and the new
testcase.
https://sourceware.org/ml/bzip2-devel/2019-q3/msg7.html
** Patch added: "Accept as many selectors as the file format allows"
Please see the discussion and analysis of the issue on the bzip2-devel
mailinglist: https://sourceware.org/ml/bzip2-devel/2019-q2/msg00024.html
There is a proposed workaround patch for decompression of the (buggy lbzip2
compressed) files:
** Patch added: "Proposed workaround. Still under analysis. Testing
appreciated."
https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+attachment/5274014/+files/0001-Be-more-liberal-in-the-number-of-selectors-we-accept.patch
--
You received this bug notification because you are a
On Sat, Oct 08, 2016 at 10:57:10PM -, Brad Parker wrote:
> Valgrind crashes when run on all applications linked to openssl.
>
> Valgrind reports:
>
> vex: the `impossible' happened:
> isZeroU
>
> valgrind: the 'impossible' happened:
> LibVEX called failure_exit().
>
>
On Tue, Mar 01, 2016 at 08:09:59AM -, bugproxy wrote:
> --- Comment From ravi.bango...@in.ibm.com 2016-03-01 03:09 EDT---
> Hi Mark,
>
> > > * Fix finding the debug info for Ubuntu kernels (Mark Wielaard). LP:
> > > #1537125.
> >
> > Just a note that the patch that went upstream is
On Wed, Feb 24, 2016 at 07:57:55AM -, Launchpad Bug Tracker wrote:
> This bug was fixed in the package elfutils - 0.165-3ubuntu1
>
> ---
> elfutils (0.165-3ubuntu1) xenial; urgency=medium
>
> * Fix finding the debug info for Ubuntu kernels (Mark Wielaard). LP:
> #1537125.
Just
On the build.log for powerpc and ppc64el one can see that the native-
core unwind seems to succeed, while the native (ptrace attach) variant
of the same test fails (in glibc/raise). I am not sure how that happens
since they should fine the same unwind/DWARF/eh_frame data to unwind
through that
Just for reference it also fails to open with another version I have
around libreoffice-writer-4.0.3.3-1.el6.rhis.x86_64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/401003
Title:
[upstream]
The attached document still doesn't open for me. Neither with
LibreOffice 3.6 (libreoffice-writer-3.6.6.2-9.fc18.x86_64) nor with a
local build of 4.1 (libreoffice-4.1.0.1-141-gca0bbec --enable-symbols
--with-system-headers).
Could someone confirm or deny that the attached document does load for
(In reply to comment #17)
Mark Wielaard, this report is not about your attachment, but the attachment
noted in the Description
https://bugs.freedesktop.org/show_bug.cgi?id=34268#c0
Yes, that is the one I am talking about. The attachement to this bug
report you reference above. Since that one
The problem is that CONFIG_DEBUG_INFO is not set.
Setting it to CONFIG_DEBUG_INFO=y will make the .debug_* sections available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886085
Title:
Public bug reported:
The linux-ac100 dbgsym ddeb packages from
http://ddebs.ubuntu.com/pool/universe/l/linux-ac100/ don't actually
contain any dwarf information. If you compare them with the ones from
http://ddebs.ubuntu.com/pool/main/l/linux/ you notice they are much
smaller and the vmlinux elf
16 matches
Mail list logo
