On Mon, Sep 09, 2013 at 12:00:15PM +0200, Jean Pihet wrote:
> On ARM the debug info is not present in the .eh_frame sections but
> in .debug_frame instead, in the dwarf format.
> Use libunwind to load and parse the debug info.
>
> Dependencies:
> . if present, libunwind >= 1.1 is needed to
On Mon, Sep 09, 2013 at 12:00:15PM +0200, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
in .debug_frame instead, in the dwarf format.
Use libunwind to load and parse the debug info.
Dependencies:
. if present, libunwind = 1.1 is needed to prevent a
On 10 September 2013 21:14, David Ahern wrote:
> On 9/9/13 3:00 AM, Jean Pihet wrote:
>>
>> diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
>> index 7014373..54532b8 100644
>> --- a/tools/perf/config/Makefile
>> +++ b/tools/perf/config/Makefile
>> @@ -222,7 +222,7 @@ endif
>>
On 9/9/13 3:00 AM, Jean Pihet wrote:
diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
index 7014373..54532b8 100644
--- a/tools/perf/config/Makefile
+++ b/tools/perf/config/Makefile
@@ -222,7 +222,7 @@ endif
FLAGS_UNWIND=$(LIBUNWIND_CFLAGS) $(CFLAGS) $(LIBUNWIND_LDFLAGS)
On 9/9/13 3:00 AM, Jean Pihet wrote:
diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
index 7014373..54532b8 100644
--- a/tools/perf/config/Makefile
+++ b/tools/perf/config/Makefile
@@ -222,7 +222,7 @@ endif
FLAGS_UNWIND=$(LIBUNWIND_CFLAGS) $(CFLAGS) $(LIBUNWIND_LDFLAGS)
On 10 September 2013 21:14, David Ahern dsah...@gmail.com wrote:
On 9/9/13 3:00 AM, Jean Pihet wrote:
diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
index 7014373..54532b8 100644
--- a/tools/perf/config/Makefile
+++ b/tools/perf/config/Makefile
@@ -222,7 +222,7 @@
On ARM the debug info is not present in the .eh_frame sections but
in .debug_frame instead, in the dwarf format.
Use libunwind to load and parse the debug info.
Dependencies:
. if present, libunwind >= 1.1 is needed to prevent a segfault when
parsing the dwarf info,
. libunwind needs to be
On ARM the debug info is not present in the .eh_frame sections but
in .debug_frame instead, in the dwarf format.
Use libunwind to load and parse the debug info.
Dependencies:
. if present, libunwind = 1.1 is needed to prevent a segfault when
parsing the dwarf info,
. libunwind needs to be
On 6 September 2013 12:17, Jiri Olsa wrote:
> On Fri, Sep 06, 2013 at 11:31:17AM +0200, Jean Pihet wrote:
>> Hi Jiri,
>>
>> On 5 September 2013 18:30, Jiri Olsa wrote:
>> > On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
>> >> On ARM the debug info is not present in the .eh_frame
On Fri, Sep 06, 2013 at 11:31:17AM +0200, Jean Pihet wrote:
> Hi Jiri,
>
> On 5 September 2013 18:30, Jiri Olsa wrote:
> > On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
> >> On ARM the debug info is not present in the .eh_frame sections but
> >> instead in .debug_frame.
> >> Use
On Thu, Sep 05, 2013 at 06:49:13PM +0200, Jean Pihet wrote:
> Hi Jiri,
>
> On 5 September 2013 18:30, Jiri Olsa wrote:
> > On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
> >> On ARM the debug info is not present in the .eh_frame sections but
> >> instead in .debug_frame.
> >> Use
Hi Jiri,
On 5 September 2013 18:30, Jiri Olsa wrote:
> On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
>> On ARM the debug info is not present in the .eh_frame sections but
>> instead in .debug_frame.
>> Use libunwind to load and parse the debug info.
>
> hum, cannot make final link:
Hi Jiri,
On 5 September 2013 18:30, Jiri Olsa jo...@redhat.com wrote:
On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use libunwind to load and parse the debug info.
hum, cannot make
On Thu, Sep 05, 2013 at 06:49:13PM +0200, Jean Pihet wrote:
Hi Jiri,
On 5 September 2013 18:30, Jiri Olsa jo...@redhat.com wrote:
On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use
On Fri, Sep 06, 2013 at 11:31:17AM +0200, Jean Pihet wrote:
Hi Jiri,
On 5 September 2013 18:30, Jiri Olsa jo...@redhat.com wrote:
On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use
On 6 September 2013 12:17, Jiri Olsa jo...@redhat.com wrote:
On Fri, Sep 06, 2013 at 11:31:17AM +0200, Jean Pihet wrote:
Hi Jiri,
On 5 September 2013 18:30, Jiri Olsa jo...@redhat.com wrote:
On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
On ARM the debug info is not present in
Hi Jiri,
On 5 September 2013 18:30, Jiri Olsa wrote:
> On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
>> On ARM the debug info is not present in the .eh_frame sections but
>> instead in .debug_frame.
>> Use libunwind to load and parse the debug info.
>
> hum, cannot make final link:
On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
> On ARM the debug info is not present in the .eh_frame sections but
> instead in .debug_frame.
> Use libunwind to load and parse the debug info.
hum, cannot make final link:
$ make LIBUNWIND_DIR=/opt/libunwind/
CHK
On 5 September 2013 17:29, Jean Pihet wrote:
[...]
> The segfault is caused by libunwind. With the latest version [1],
> dwarf unwinding works fine.
> Investigation on-going, more to come!
>
> [1] git://git.sv.gnu.org/libunwind.git
>
I managed to get it to work by upgrading to Ubuntu Saucy's
Hi,
On 5 September 2013 15:33, Jean Pihet wrote:
> On 5 September 2013 15:19, Will Deacon wrote:
>> On Thu, Sep 05, 2013 at 02:17:30PM +0100, Ard Biesheuvel wrote:
>>> On 5 September 2013 15:05, Jean Pihet wrote:
>>> [..]
>>> > Here are the commands I have been using:
>>> > perf record -g
On 5 September 2013 15:19, Will Deacon wrote:
> On Thu, Sep 05, 2013 at 02:17:30PM +0100, Ard Biesheuvel wrote:
>> On 5 September 2013 15:05, Jean Pihet wrote:
>> [..]
>> > Here are the commands I have been using:
>> > perf record -g dwarf --
>> > perf report --sort symbol --call-graph
On Thu, Sep 05, 2013 at 02:17:30PM +0100, Ard Biesheuvel wrote:
> On 5 September 2013 15:05, Jean Pihet wrote:
> [..]
> > Here are the commands I have been using:
> > perf record -g dwarf --
> > perf report --sort symbol --call-graph --stdio
> >
>
> Ah, I failed to add the 'dwarf' after -g,
On 5 September 2013 15:05, Jean Pihet wrote:
[..]
> Here are the commands I have been using:
> perf record -g dwarf --
> perf report --sort symbol --call-graph --stdio
>
Ah, I failed to add the 'dwarf' after -g, however, in that case, my
perf report segfaults:
#0 locate_debug_info
On 5 September 2013 14:45, Will Deacon wrote:
> Hi Jean,
>
> [adding Michael, since I know he was interested in this]
>
> On Wed, Sep 04, 2013 at 07:04:14PM +0100, Jean Pihet wrote:
>> On ARM the debug info is not present in the .eh_frame sections but
>> instead in .debug_frame.
>> Use libunwind
Hi Will,
On Thu, Sep 5, 2013 at 2:45 PM, Will Deacon wrote:
> Hi Jean,
>
> [adding Michael, since I know he was interested in this]
>
> On Wed, Sep 04, 2013 at 07:04:14PM +0100, Jean Pihet wrote:
>> On ARM the debug info is not present in the .eh_frame sections but
>> instead in .debug_frame.
Hi Jean,
[adding Michael, since I know he was interested in this]
On Wed, Sep 04, 2013 at 07:04:14PM +0100, Jean Pihet wrote:
> On ARM the debug info is not present in the .eh_frame sections but
> instead in .debug_frame.
> Use libunwind to load and parse the debug info.
How have you tested
Hi Jean,
[adding Michael, since I know he was interested in this]
On Wed, Sep 04, 2013 at 07:04:14PM +0100, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use libunwind to load and parse the debug info.
How have you tested this?
Hi Will,
On Thu, Sep 5, 2013 at 2:45 PM, Will Deacon will.dea...@arm.com wrote:
Hi Jean,
[adding Michael, since I know he was interested in this]
On Wed, Sep 04, 2013 at 07:04:14PM +0100, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
instead in
On 5 September 2013 14:45, Will Deacon will.dea...@arm.com wrote:
Hi Jean,
[adding Michael, since I know he was interested in this]
On Wed, Sep 04, 2013 at 07:04:14PM +0100, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use
On 5 September 2013 15:05, Jean Pihet jean.pi...@newoldbits.com wrote:
[..]
Here are the commands I have been using:
perf record -g dwarf -- binary to profile
perf report --sort symbol --call-graph --stdio
Ah, I failed to add the 'dwarf' after -g, however, in that case, my
perf report
On Thu, Sep 05, 2013 at 02:17:30PM +0100, Ard Biesheuvel wrote:
On 5 September 2013 15:05, Jean Pihet jean.pi...@newoldbits.com wrote:
[..]
Here are the commands I have been using:
perf record -g dwarf -- binary to profile
perf report --sort symbol --call-graph --stdio
Ah, I failed
On 5 September 2013 15:19, Will Deacon will.dea...@arm.com wrote:
On Thu, Sep 05, 2013 at 02:17:30PM +0100, Ard Biesheuvel wrote:
On 5 September 2013 15:05, Jean Pihet jean.pi...@newoldbits.com wrote:
[..]
Here are the commands I have been using:
perf record -g dwarf -- binary to profile
Hi,
On 5 September 2013 15:33, Jean Pihet jean.pi...@linaro.org wrote:
On 5 September 2013 15:19, Will Deacon will.dea...@arm.com wrote:
On Thu, Sep 05, 2013 at 02:17:30PM +0100, Ard Biesheuvel wrote:
On 5 September 2013 15:05, Jean Pihet jean.pi...@newoldbits.com wrote:
[..]
Here are the
On 5 September 2013 17:29, Jean Pihet jean.pi...@linaro.org wrote:
[...]
The segfault is caused by libunwind. With the latest version [1],
dwarf unwinding works fine.
Investigation on-going, more to come!
[1] git://git.sv.gnu.org/libunwind.git
I managed to get it to work by upgrading to
On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use libunwind to load and parse the debug info.
hum, cannot make final link:
$ make LIBUNWIND_DIR=/opt/libunwind/
CHK
Hi Jiri,
On 5 September 2013 18:30, Jiri Olsa jo...@redhat.com wrote:
On Wed, Sep 04, 2013 at 08:04:14PM +0200, Jean Pihet wrote:
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use libunwind to load and parse the debug info.
hum, cannot make
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use libunwind to load and parse the debug info.
Signed-off-by: Jean Pihet
---
tools/perf/util/unwind.c | 70 +---
1 file changed, 54 insertions(+), 16
On ARM the debug info is not present in the .eh_frame sections but
instead in .debug_frame.
Use libunwind to load and parse the debug info.
Signed-off-by: Jean Pihet jean.pi...@linaro.org
---
tools/perf/util/unwind.c | 70 +---
1 file changed, 54
38 matches
Mail list logo
