Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: markus.t.metzger@intel.com
Cc: kettenis@gnu.org, gdb-patches@sourceware.org, markus.t.metzger@gmail.com
Subject: Re: [PATCH 00/16] branch tracing support (resend)
Date: Fri, 25 May 2012 19:18:00 -0000	[thread overview]
Message-ID: <4FBFDAE8.6080707@redhat.com> (raw)
In-Reply-To: <1337772151-20265-1-git-send-email-markus.t.metzger@intel.com>

Hi, I've just tried out this series applied on current mainline, and I get:

>./gdb ./gdb
...
(gdb) start
Temporary breakpoint 1 at 0x456a03: file ../../src/gdb/gdb.c, line 29.
Starting program: /home/pedro/gdb/mygit/build/gdb/gdb
warning: Skipping deprecated .gdb_index section in /usr/lib/debug/lib64/ld-2.14.90.so.debug, pass --use-deprecated-index-sections to use them anyway
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffdd78) at ../../src/gdb/gdb.c:29
29        memset (&args, 0, sizeof args);
(gdb) btrace enable auto
(gdb) btrace enable all
(gdb) n

Program received signal SIGSEGV, Segmentation fault.
0x0000000000456a0e in main (argc=1, argv=0x7fffffffdd78) at ../../src/gdb/gdb.c:29
29        memset (&args, 0, sizeof args);
(gdb)

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)

Any idea off hand what this would be?

This in on x86_64 Fedora 16, Linux 3.3.5-2.fc16.x86_64.

Running the new tests with

$ make check RUNTESTFLAGS="--directory=gdb.btrace"

Results in

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../../../src/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
Running ../../../src/gdb/testsuite/gdb.btrace/allthreads_trace.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/decrement.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/disable_all.exp ...
NOTE: This is 64 bit host.
Running ../../../src/gdb/testsuite/gdb.btrace/enable.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/enable_all.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/enable_range.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/list.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/list_function.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/list_options.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/main_asm.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/main_segv.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/sanity_crash.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/threads_auto.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/threads_independent.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/threads_nonstop.exp ...
Running ../../../src/gdb/testsuite/gdb.btrace/trace_iteration.exp ...

                === gdb Summary ===

# of untested testcases         6
# of unsupported tests          7

The log file has a bunch of:

Assembler messages:
Fatal error: can't create /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.btrace/threads_asm.o: No such file or directory
compiler exited with status 1
output is:
Assembler messages:
Fatal error: can't create /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.btrace/threads_asm.o: No such file or directory

I build gdb with srcdir != builddir.

-- 
Pedro Alves


  parent reply	other threads:[~2012-05-25 19:18 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 11:23 markus.t.metzger
2012-05-23 11:24 ` [PATCH 10/16] btrace, config: enable btrace for 32bit and 64bit linux native markus.t.metzger
2012-05-23 11:24 ` [PATCH 06/16] configure: add check for perf_event header markus.t.metzger
2012-05-30 20:43   ` Jan Kratochvil
2012-05-31 15:34     ` Metzger, Markus T
2012-06-22 20:40       ` Tom Tromey
2012-06-25  8:50         ` Metzger, Markus T
2012-05-23 11:24 ` [PATCH 02/16] source: add flags to print_source_lines () markus.t.metzger
2012-05-30 20:41   ` Jan Kratochvil
2012-05-31 15:34     ` Metzger, Markus T
2012-06-22 20:08       ` Tom Tromey
2012-06-25  8:50         ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 16/16] gdbserver, linux, btrace: add btrace support for linux-low markus.t.metzger
2012-05-23 11:25 ` [PATCH 13/16] xml, btrace: define btrace xml document style markus.t.metzger
2012-05-30 20:44   ` Jan Kratochvil
2012-06-01  8:39     ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 15/16] gdbserver, btrace: add generic btrace support markus.t.metzger
2012-05-23 11:25 ` [PATCH 08/16] linux, btrace: perf_event based branch tracing markus.t.metzger
2012-05-30 20:43   ` Jan Kratochvil
2012-05-31 15:34     ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 03/16] source, disasm: optionally prefix source lines with filename markus.t.metzger
2012-05-30 20:41   ` Jan Kratochvil
2012-05-23 11:25 ` [PATCH 01/16] disas: add precise instructions flag markus.t.metzger
2012-05-23 11:25 ` [PATCH 14/16] remote, btrace: add branch trace remote ops markus.t.metzger
2012-05-30 20:44   ` Jan Kratochvil
2012-06-01  8:49     ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 05/16] cli, btrace: add btrace cli markus.t.metzger
2012-05-30 20:42   ` Jan Kratochvil
2012-05-31 15:33     ` Metzger, Markus T
2012-06-01 18:42       ` Jan Kratochvil
2012-06-05  9:56         ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 04/16] thread, btrace: add generic branch trace support markus.t.metzger
2012-05-30 20:42   ` Jan Kratochvil
2012-05-31 15:33     ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 09/16] btrace, linux: add linux native btrace target ops markus.t.metzger
2012-05-30 20:43   ` Jan Kratochvil
2012-05-31 15:34     ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 11/16] test, btrace: add branch trace tests markus.t.metzger
2012-05-30 20:44   ` Jan Kratochvil
2012-06-01 11:37     ` Metzger, Markus T
2012-05-23 11:26 ` [PATCH 12/16] test, btrace: more branch tracing tests markus.t.metzger
2012-05-23 11:26 ` [PATCH 07/16] configure: autoreconf markus.t.metzger
2012-06-22 20:44   ` Tom Tromey
2012-06-25  8:50     ` Metzger, Markus T
2012-05-25 19:18 ` Pedro Alves [this message]
2012-05-29 14:31   ` [PATCH 00/16] branch tracing support (resend) Metzger, Markus T
2012-05-30 14:49     ` Pedro Alves
2012-05-30 15:51       ` Metzger, Markus T
2012-05-30 17:56         ` Pedro Alves
2012-05-31 17:11           ` Metzger, Markus T
2012-06-04  6:46             ` Metzger, Markus T
2012-06-12 11:32           ` Metzger, Markus T
2012-06-12 12:09             ` Jan Kratochvil
2012-06-12 12:23             ` Pedro Alves
2012-06-12 12:25               ` Jan Kratochvil
2012-06-12 13:38                 ` Metzger, Markus T
2012-05-30 20:41 ` Jan Kratochvil
2012-05-31 15:33   ` Metzger, Markus T
2012-06-22 20:31 ` Tom Tromey
2012-06-25  8:50   ` Metzger, Markus T
2012-07-02  8:29     ` Metzger, Markus T

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FBFDAE8.6080707@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kettenis@gnu.org \
    --cc=markus.t.metzger@gmail.com \
    --cc=markus.t.metzger@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox