public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/14845] Segmentation fault on "info tracepoints"
Date: Thu, 15 Nov 2012 14:39:00 -0000	[thread overview]
Message-ID: <bug-14845-4717-T4ZT9E7tSn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14845-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14845

Yao Qi <qiyao at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |qiyao at gcc dot gnu.org

--- Comment #1 from Yao Qi <qiyao at gcc dot gnu.org> 2012-11-15 14:39:36 UTC ---
I don't see segfault on GDB 7.5 and head as below.  GDB is configured as
'i686-pc-linux-gnu'.

$ ./run-test.sh
make: Nothing to be done for `all'.
Process ./bar created; pid = 26552
Listening on port 7777
Python Exception <type 'exceptions.ImportError'> No module named gdb: 

warning: Could not load the Python gdb module from
`/usr/local/share/gdb/python'.

warning: Limited Python support is available from the _gdb module.
Remote debugging from host 127.0.0.1
0x4ce4c2b0 in _start () from /lib/ld-linux.so.2
Breakpoint 1 at 0x8048662: file bar.c, line 35.
Loading libfoo.so

Breakpoint 1, main () at bar.c:35
35          printf("\t%i\n", foo_ptr());
Tracepoint 2 at 0xb7ffb416: file foo.c, line 5.
Breakpoint 3 at 0x804867f: file bar.c, line 37.
        1
Unloading libfoo.so
warning: Temporarily disabling breakpoints for unloaded shared library
"./libfoo.so"

Breakpoint 3, main () at bar.c:37
37          return EXIT_SUCCESS;
Found trace frame 0, tracepoint 2
No trace frame found
Num     Type           Disp Enb Address    What
2       tracepoint     keep y   <PENDING>  foo
Killing all inferiors

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-11-15 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 14:04 [Bug breakpoints/14845] New: " m.lesniewski at samsung dot com
2012-11-15 14:05 ` [Bug breakpoints/14845] " m.lesniewski at samsung dot com
2012-11-15 14:06 ` m.lesniewski at samsung dot com
2012-11-15 14:39 ` qiyao at gcc dot gnu.org [this message]
2012-11-15 14:57 ` palves at redhat dot com
2012-11-15 15:34 ` m.lesniewski at samsung dot com
2012-11-15 15:35 ` m.lesniewski at samsung dot com

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=bug-14845-4717-T4ZT9E7tSn@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).