From: Oguz Kayral <oguzkayral@gmail.com>
To: archer@sourceware.org
Subject: [RFC][0/5] Python event handling
Date: Sun, 23 Aug 2009 15:34:00 -0000 [thread overview]
Message-ID: <36a35d480908230834y46a44e08od4645db444bb5e7a@mail.gmail.com> (raw)
Hi,
This patch series adds inferior event handling support to GDB Python
scripting. The work is based on archer-tromey-python branch.
An example gdb session:
gsoc-gdb/install/bin/gdb ./simple
GNU gdb (GDB) 6.8.50.20090717-cvs
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(gdb) require command check_segfault
(gdb) start
Temporary breakpoint 1 at 0x80483a5: file simple.c, line 7.
Starting program: /home/oguz/simple
Temporary breakpoint 1, main () at simple.c:7
7 *p = simple();
(gdb) check_segfault
SIGSEGV handler registered.
(gdb) cont
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x080483af in main () at simple.c:7
7 *p = simple();
event type : stop
stop reason: signal
stop signal: SIGSEGV
#0 0x080483af in main () at simple.c:7
next reply other threads:[~2009-08-23 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 15:34 Oguz Kayral [this message]
2009-09-21 21:17 ` Tom Tromey
2009-09-24 1:52 ` Richard Ward
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=36a35d480908230834y46a44e08od4645db444bb5e7a@mail.gmail.com \
--to=oguzkayral@gmail.com \
--cc=archer@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).