Kurt Roeckx roeckx.be> writes:
> The new elfutils (0.157-1) segfaults on IA64. I've been trying
> to debug this on merulo but ran into #691576. When using a core
> file I also don't get any backtrace.
>
> The problem I'm seeing is:
> (sid_ia64-dchroot)kroeckx merulo:~/elfutils-0.157/tests$
> L
Hi Kurt,
Unfortunately, no, not yet, but I haven't given up or anything. I'm
actually on vacation for a couple more days. When I come back, I'll try it
out like you mentioned.
Patrick
On Sun, Oct 6, 2013 at 11:38 AM, Kurt Roeckx wrote:
> On Wed, Oct 02, 2013 at 09:10:58PM +0200, Kurt Roeckx w
On Wed, Oct 02, 2013 at 09:10:58PM +0200, Kurt Roeckx wrote:
> On Wed, Oct 02, 2013 at 02:02:41PM -0500, Patrick Baggett wrote:
> >
> > That's rather confusing to read. The code was compiled with "-O2 -g",
> > perhaps I should try -O0 first to rule out a compiler bug? If so, how do I
> > build it
On Wed, Oct 02, 2013 at 02:02:41PM -0500, Patrick Baggett wrote:
>
> That's rather confusing to read. The code was compiled with "-O2 -g",
> perhaps I should try -O0 first to rule out a compiler bug? If so, how do I
> build it with -O0?
With DEB_BUILD_OPTIONS=noopt dpkg-buildpackage -B
You might
On Wed, Oct 2, 2013 at 1:51 PM, Kurt Roeckx wrote:
> On Wed, Oct 02, 2013 at 01:43:56PM -0500, Patrick Baggett wrote:
> > I set the breakpoint, and it is called as you expected:
> > (gdb) bt
> > #0 ppc_register_info (ebl=0x60004120, regno=-1, name=0x0,
> > namelen=0, prefix=0x0, setname=
On Wed, Oct 02, 2013 at 01:43:56PM -0500, Patrick Baggett wrote:
> I set the breakpoint, and it is called as you expected:
> (gdb) bt
> #0 ppc_register_info (ebl=0x60004120, regno=-1, name=0x0,
> namelen=0, prefix=0x0, setname=0x0, bits=0x0, type=0x0) at ppc_regs.c:45
It's for the regno=1
I set the breakpoint, and it is called as you expected:
(gdb) bt
#0 ppc_register_info (ebl=0x60004120, regno=-1, name=0x0,
namelen=0, prefix=0x0, setname=0x0, bits=0x0, type=0x0) at ppc_regs.c:45
#1 0x200ba2c0 in ebl_register_info (ebl=0x60004120,
regno=-1, name=0x0, namel
On Wed, Oct 02, 2013 at 01:12:44PM -0500, Patrick Baggett wrote:
> OK, here's what I get when I run that test in GDB:
>
> Program received signal SIGSEGV, Segmentation fault.
> dwarf_frame_register (fs=0x6000be00, regno=,
> ops_mem=0x6fffb2d0, ops=0x6fffb2c8,
> nops
OK, here's what I get when I run that test in GDB:
Program received signal SIGSEGV, Segmentation fault.
dwarf_frame_register (fs=0x6000be00, regno=,
ops_mem=0x6fffb2d0, ops=0x6fffb2c8,
nops=0x6fffb2c0) at dwarf_frame_register.c:105
105 get_uleb12
Ah stupid issue, I didn't unpack the source correctly; it was in a separate
folder. Ahem, move along, nothing to see here. :)
I'll get some results for you soon!
Patrick
On Wed, Oct 2, 2013 at 2:13 AM, Kurt Roeckx wrote:
> On Tue, Oct 01, 2013 at 09:55:12PM -0500, Patrick Baggett wrote:
> > K
Hah, you and me both. I'm going to delete the whole directory, redownload
your files, and try again.
Patrick
On Wed, Oct 2, 2013 at 2:13 AM, Kurt Roeckx wrote:
> On Tue, Oct 01, 2013 at 09:55:12PM -0500, Patrick Baggett wrote:
> > Kurt,
> >
> > The package does not built with "dpkg-buildpackag
On Tue, Oct 01, 2013 at 09:55:12PM -0500, Patrick Baggett wrote:
> Kurt,
>
> The package does not built with "dpkg-buildpackage -B". It stops in the
> makefile saying that it does not know how to make target "configure.ac". I
> have automake and autoconf installed already, if that helps. Until thi
Kurt,
The package does not built with "dpkg-buildpackage -B". It stops in the
makefile saying that it does not know how to make target "configure.ac". I
have automake and autoconf installed already, if that helps. Until this
issue is resolved, I can't build the package to try it. :(
Patrick
On
Cool, thanks! I'll check it out later tonight and let you know what I find.
Patrick.
On Tue, Oct 1, 2013 at 2:46 PM, Kurt Roeckx wrote:
> You need to get the source first, which is probably still on
> incoming only. I've put a copy on:
> http://people.debian.org/~kroeckx/elfutils/
>
> A dpkg
You need to get the source first, which is probably still on
incoming only. I've put a copy on:
http://people.debian.org/~kroeckx/elfutils/
A dpkg-buildpackage -B should result in 1 test failing. You
can run that test manually like I showed below.
Kurt
On Tue, Oct 01, 2013 at 02:27:11PM -0500
Yeah, I can try. How do I reproduce this on sid?
Patrick
On Tue, Oct 1, 2013 at 1:43 PM, Kurt Roeckx wrote:
> Hi,
>
> The new elfutils (0.157-1) segfaults on IA64. I've been trying
> to debug this on merulo but ran into #691576. When using a core
> file I also don't get any backtrace.
>
> Th
Hi,
The new elfutils (0.157-1) segfaults on IA64. I've been trying
to debug this on merulo but ran into #691576. When using a core
file I also don't get any backtrace.
The problem I'm seeing is:
(sid_ia64-dchroot)kroeckx@merulo:~/elfutils-0.157/tests$
LD_LIBRARY_PATH=../libelf:../libdw:../back
17 matches
Mail list logo