Hi Jean,
Seems you already got your answer to the build question solved.
On Tue, 2014-02-25 at 18:17 +0100, Jean Pihet wrote:
> The goal is to add the libdw support for perf on ARM (and later AARCH64).
Note that there is some code in elfutils git that handles .debug_frame
for ARM, but not yet co
On Tue, 2014-02-25 at 09:28 -0800, Josh Stone wrote:
> On 02/25/2014 01:43 AM, Florian Weimer wrote:
> > On 02/24/2014 05:54 PM, Mark Wielaard wrote:
> >
> >>> Is there a reliable way to recognize separate debugging information?
> >>> Then I could avoid extracting data from phdrs.
> >>
> >> I look
On Sat, 2014-02-22 at 22:09 +0100, Jan Kratochvil wrote:
> the core. The testcase mostly comes from the former patch.
>
> > libdwfl/
> > 2014-02-22 Jan Kratochvil
> >
> > Access deleted files by /dev/PID/mem.
> > * dwfl_module.c (dwfl_report_module_pid): New function.
> > * dwfl_mo
On Sat, 2014-02-22 at 22:08 +0100, Jan Kratochvil wrote:
> probably obvious, easy to debug with [patch 3/3] applied.
>
> > 2014-02-22 Jan Kratochvil
> >
> > Fix abort() on missing section headers.
> > * dwarf_begin_elf.c (check_section): Replace abort call by a return;
> > [...]
> > @@
On Sat, 2014-02-22 at 22:08 +0100, Jan Kratochvil wrote:
> > 2014-02-22 Jan Kratochvil
> >
> > Extend __libdw_open_file and elf_begin as *_at_offset.
> > * NEWS (libelf): New, with elf_begin_at_offset.
I rather not extend the libelf interface if possible. The various libelf
implementat
On Sat, 2014-02-22 at 22:08 +0100, Jan Kratochvil wrote:
> jankratochvil/devmem
The name, the subject and some of the comments talks about /dev.
But I assume this is really about /proc?
> An security breach countercase upstream is ftruncate(2) for mmap(2)ed and
> close(2)ed file which was not pos
Hi Jan, Frank,
On 25 February 2014 18:26, Frank Ch. Eigler wrote:
> Hi -
>
>> I am trying to compile libdw for ARM, both natively and on x86_64. I
>> am getting build errors, it seems that the build is always targeted to
>> x86_64. [...]
>
>> *** missing i386_dis.h; configure with --enable-mainta
Hi -
> I am trying to compile libdw for ARM, both natively and on x86_64. I
> am getting build errors, it seems that the build is always targeted to
> x86_64. [...]
> *** missing i386_dis.h; configure with --enable-maintainer-mode
> *** missing x86_64_dis.h; configure with --enable-maintainer-mod
On Tue, 25 Feb 2014 18:17:24 +0100, Jean Pihet wrote:
> I am trying to compile libdw for ARM,
There is no need/possibility to specify ARM target or any other target, every
build of elfutils will always handle all the supported targets.
> *** missing i386_dis.h; configure with --enable-maintainer
On 02/25/2014 01:43 AM, Florian Weimer wrote:
> On 02/24/2014 05:54 PM, Mark Wielaard wrote:
>
>>> Is there a reliable way to recognize separate debugging information?
>>> Then I could avoid extracting data from phdrs.
>>
>> I looked a bit into this and I don't see any way to detect that the
>> ph
Hi Jan, Mark,
I have a simple question which I cannot find the solution for.
The goal is to add the libdw support for perf on ARM (and later AARCH64).
I am trying to compile libdw for ARM, both natively and on x86_64. I
am getting build errors, it seems that the build is always targeted to
x86_64
On 02/24/2014 05:54 PM, Mark Wielaard wrote:
Is there a reliable way to recognize separate debugging information?
Then I could avoid extracting data from phdrs.
I looked a bit into this and I don't see any way to detect that the
phdrs are invalid, unless you already know this is a separate deb
12 matches
Mail list logo
