From: Michael Snyder <msnyder@vmware.com>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/4] 'catch syscall' feature
Date: Wed, 01 Oct 2008 22:40:00 -0000 [thread overview]
Message-ID: <48E3FBE1.9030800@vmware.com> (raw)
In-Reply-To: <1222798405.30389.22.camel@miki>
Hi Sergio,
What source tree or snapshot is your diff taken from?
I tried applying it to current cvs, and got a lot of
failures and fuzzes.
Sérgio Durigan Júnior wrote:
> Hello guys,
>
> As this is my first "serious" patch to GDB, I'm sure there will be a lot
> of mistakes in it :-). Anyway, I hope this adds something useful to the
> program.
>
> The purpose of this patch is to implement a new feature in GDB called
> "catch syscall". In this first moment, the feature should look something
> like the 'strace' utility, but less "capable" (it still can't, for
> example, get the syscall arguments and return code - although, the way I
> see, this would be easy to do).
>
> With this feature, you can start over you GDB and tell it to start
> catching syscalls in the inferior. Whenever a syscall is called (or
> returns), GDB stops and tell you the name of it. You can also ask GDB to
> "filter" the syscalls so that you'll only see calls/returns from that
> specific syscall.
>
> For now the feature is only implemented for PPC32 and PPC64, but in a
> future not so distant I intend to send patches for x86 and x86_64 too.
>
> I've tried to organize the code the best way I could, and I've
> extensively used the codes for "catch fork", "catch exec" and "catch
> unload" as an example. I'd be glad if you could give some opinions about
> the way I did it :-).
>
> I've also splitted the patch into 4 logical "sequences", that are
> organized in this way:
>
> - First part implements the architecture-independent part of the
> feature.
> - Second part implements the architecture-dependent (PPC32 and PPC64)
> part of the feature.
> - Third part refers to the documentation.
> - Fourth part brings the testcase.
>
> Unfortunately, if one applies the patch and compiles GDB for PPC64, it
> doesn't work properly. This is due to a bug which we have found that
> makes the inferior segfault when there is a breakpoint inserted at its
> entrypoint (AT_ENTRY). Luis Machado is taking a closer look into this
> issue, so I think he'll have a solution soon :-).
>
> Special thanks goes to Thiago Bauermann, Luis Machado and Carlos Seo,
> who helped me a lot with my never-ending questions about GDB.
>
> Regards,
>
> --
> Sérgio Durigan Júnior
> Linux on Power Toolchain - Software Engineer
> Linux Technology Center - LTC
> IBM Brazil
>
>
next prev parent reply other threads:[~2008-10-01 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 18:12 Sérgio Durigan Júnior
2008-10-01 22:40 ` Michael Snyder [this message]
2008-10-01 23:02 ` Sérgio Durigan Júnior
2008-10-01 23:53 ` Michael Snyder
2008-10-02 3:42 ` Luis Machado
2008-10-02 3:47 ` Sérgio Durigan Júnior
2008-10-02 22:01 ` Michael Snyder
2008-10-03 2:14 ` Sérgio Durigan Júnior
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=48E3FBE1.9030800@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@linux.vnet.ibm.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