binutils is now recent enough in 14.10
** Changed in: binutils (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365664
Title:
gdb source test suites are fa
This bug was fixed in the package gdb - 7.8-0ubuntu2
---
gdb (7.8-0ubuntu2) utopic; urgency=medium
* Update gdb from the 7.8 release branch.
- Fix regression for Linux vDSO in GDB (PR gdb/17407).
- Fix regression, GDB stopped on run with attached process (PR gdb/17347).
** Branch linked: lp:ubuntu/utopic-proposed/gdb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365664
Title:
gdb source test suites are failing in Ubuntu14.10
To manage notifications about this bug
** Also affects: binutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365664
Title:
gdb source test suites are failing in Ubuntu14.10
To mana
Moving section headers to the end sounds good.
However, maybe we should make the bfd_from_remote_memory change too, in
order to cope with kernels already in the field?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I'm looking into moving the section headers to the end of the object
file for ld.bfd. It doesn't look too hard, but there will likely be
some testsuite tweaking needed. It looks like gold puts section headers
last.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
On second glance, looks I'm wrong: .symtab and .strtab actually do come *after*
the section headers in "normal" executables too.
So I guess the best thing to do would be to fix bfd_from_remote_memory to
actually include enough memory to cover all sections, even those after the
section headers.
Hmmm ... usually, the section headers come at the very end of the file.
It's a bit strange that there is section data *after* the headers in
this case; maybe that's what confuses GDB/BFD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Of course it's the actual section headers at that offset. Now the
question is, should we fix bfd_from_remote_memory so it can read
sections after the section headers assuming they are in memory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still trawling through gdb, but the issue appears to be in
bfd/elfcode.h, bfd_from_remote_memory:
shdr_end = i_ehdr.e_shoff + i_ehdr.e_shnum * i_ehdr.e_shentsize;
[17] .shstrtab STRTAB 001603 be 00
0 0 1
[18] .symtab SYMTAB 000
Well, GDB assumes that the VDSO contains the whole ELF *file*, not just
segments that would be loaded into memory if the object were loaded by
the dynamic loader.
In particular, none of the symbol table (.symtab, .strtab) or debug info
sections usually reside in loaded segments, but the debugger o
I see what is going on, but don't know how to fix it yet.
Gdb must be checking for program headers that are marked load or
segments that are marked allocate (not exactly sure what yet). The
.symtab and .strtab are not, because normally they are not loaded into
memory.
The problem is bfd_elf_get_e
Anton Blanchard wrote:
>I wonder if the gdb complaint about the kernel VDSO is causing the test to
>fail. The warning is almost certainly a result of
>this kernel patch:
>
>powerpc: Use unstripped VDSO image for more accurate profiling data
Whether or not this complaint is causing that test
(gdb) break /home/ubuntu/binutils-gdb/gdb/testsuite/gdb.base/annota1.c:28
Breakpoint 1 at 0x16e4: file
/home/ubuntu/binutils-gdb/gdb/testsuite/gdb.base/annota1.c, line 28.
(gdb) run
Starting program: /tmp/foo
Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
Brea
** Changed in: gdb (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365664
Title:
gdb source test suites are failing in Ubuntu14.10
To manage notificat
how did you check? are these regressions, or new tests failing?
** Changed in: gdb (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365664
Title:
gdb source
** Package changed: ubuntu => gdb (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365664
Title:
gdb source test suites are failing in Ubuntu14.10
To manage notifications about this bug go t
17 matches
Mail list logo
