On Sun, Nov 03, 2013 at 02:58:54AM +0100, Kurt Roeckx wrote:
On Sat, Nov 02, 2013 at 10:06:20PM +0100, Mark Wielaard wrote:
Although the public ABI of libelf is stable and should never break,
the elfutils tools (at least readelf) also use some internals from
libelf, which isn't public
On Sun, Nov 03, 2013 at 10:47:16AM +0100, Mark Wielaard wrote:
On Sun, Nov 03, 2013 at 02:58:54AM +0100, Kurt Roeckx wrote:
On Sat, Nov 02, 2013 at 10:06:20PM +0100, Mark Wielaard wrote:
Although the public ABI of libelf is stable and should never break,
the elfutils tools (at least
On Sun, Nov 03, 2013 at 02:28:45PM +0100, Kurt Roeckx wrote:
The problem actually seems to be that I removed the configure
option --enable-thread-safety. Not sure how exactly this has
an effect yet.
That changes the definition of rwlock_define as used in the internal
libelfP.h struct Elf,
On Sun, Nov 03, 2013 at 03:29:36PM +0100, Mark Wielaard wrote:
On Sun, Nov 03, 2013 at 02:28:45PM +0100, Kurt Roeckx wrote:
The problem actually seems to be that I removed the configure
option --enable-thread-safety. Not sure how exactly this has
an effect yet.
That changes the
On Sun, Nov 03, 2013 at 10:47:16AM +0100, Mark Wielaard wrote:
If you package libasm separately it does depend on backend internals
so should depend on the exact version of libdw1 (in which the libebl
backends are).
The reason for elfutils to depend on libdw1 with the exact same
version was
On Sun, Nov 03, 2013 at 04:08:18PM +0100, Kurt Roeckx wrote:
On Sun, Nov 03, 2013 at 10:47:16AM +0100, Mark Wielaard wrote:
If you package libasm separately it does depend on backend internals
so should depend on the exact version of libdw1 (in which the libebl
backends are).
The
On Sun, 2013-11-03 at 15:53 +0100, Kurt Roeckx wrote:
I missed that part about rwlock_define. I know also see that
struct Elf is used in libelf.h, and things start to make sense to
me.
Note that in libelf.h struct Elf is opaque, users that just use libelf.h
cannot access the struct fields
On Sun, 2013-11-03 at 16:38 +0100, Kurt Roeckx wrote:
So after some changed I'm currently having this:
Package: elfutils
Version: 0.156-2
Depends: libasm1 (= 0.132), libc6 (= 2.14), libdw1 (= 0.156-2), libelf1 (=
0.156-2), libstdc++6 (= 4.1.1)
This is right, none of the elfutils tools use
Package: elfutils
Version: 0.148-1
Severity: important
I'm trying to use abi-dumper tool for analyzing the ABI of my own shared
library. This tools uses eu-readelf to actually read the library symbols
but eu-readelf crashes, making it unusable:
% eu-readelf -N --debug-dump=loc
On Sat, Nov 02, 2013 at 06:23:14PM +0100, Vadim Zeitlin wrote:
Package: elfutils
Version: 0.148-1
Severity: important
I'm trying to use abi-dumper tool for analyzing the ABI of my own shared
library. This tools uses eu-readelf to actually read the library symbols
but eu-readelf crashes,
On Sat, Nov 02, 2013 at 06:46:44PM +0100, Kurt Roeckx wrote:
On Sat, Nov 02, 2013 at 06:23:14PM +0100, Vadim Zeitlin wrote:
Package: elfutils
Version: 0.148-1
Severity: important
I'm trying to use abi-dumper tool for analyzing the ABI of my own shared
library. This tools uses
On Sat, Nov 02, 2013 at 06:23:14PM +0100, Vadim Zeitlin wrote:
I'm trying to use abi-dumper tool for analyzing the ABI of my own shared
library. This tools uses eu-readelf to actually read the library symbols
but eu-readelf crashes, making it unusable:
% eu-readelf -N --debug-dump=loc
On Sat, 2 Nov 2013 18:50:04 +0100 Kurt Roeckx k...@roeckx.be wrote:
KR On Sat, Nov 02, 2013 at 06:46:44PM +0100, Kurt Roeckx wrote:
KR On Sat, Nov 02, 2013 at 06:23:14PM +0100, Vadim Zeitlin wrote:
KR Package: elfutils
KR Version: 0.148-1
KR Severity: important
KR
KR I'm trying to use
On Sat, Nov 02, 2013 at 07:11:46PM +0100, Mark Wielaard wrote:
On Sat, Nov 02, 2013 at 06:23:14PM +0100, Vadim Zeitlin wrote:
I'm trying to use abi-dumper tool for analyzing the ABI of my own shared
library. This tools uses eu-readelf to actually read the library symbols
but eu-readelf
On Sat, Nov 02, 2013 at 07:28:27PM +0100, Kurt Roeckx wrote:
On Sat, Nov 02, 2013 at 07:11:46PM +0100, Mark Wielaard wrote:
On Sat, Nov 02, 2013 at 06:23:14PM +0100, Vadim Zeitlin wrote:
I'm trying to use abi-dumper tool for analyzing the ABI of my own shared
library. This tools uses
On Sat, 2 Nov 2013 19:35:39 +0100 Kurt Roeckx k...@roeckx.be wrote:
KR So for me I have this problem with this combination:
KR elfutils 0.157-1
KR libdw1 0.157-1
KR libelf1 0.153-2
KR
KR Upgrading libelf1 to 0.157-1 makes the problem go away for me.
Sorry, I was wrong in my initial bug report:
On Sat, Nov 02, 2013 at 07:35:39PM +0100, Kurt Roeckx wrote:
So for me I have this problem with this combination:
elfutils 0.157-1
libdw1 0.157-1
libelf1 0.153-2
Upgrading libelf1 to 0.157-1 makes the problem go away for me.
This looks like some ABI breakage in libelf?
Although the
On Sat, Nov 02, 2013 at 10:06:20PM +0100, Mark Wielaard wrote:
On Sat, Nov 02, 2013 at 07:35:39PM +0100, Kurt Roeckx wrote:
So for me I have this problem with this combination:
elfutils 0.157-1
libdw1 0.157-1
libelf1 0.153-2
Upgrading libelf1 to 0.157-1 makes the problem go away for
18 matches
Mail list logo
