Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@fsmware.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: System calls debugging
Date: Wed, 11 Feb 2004 17:37:00 -0000	[thread overview]
Message-ID: <20040211093618.G17066@demos.bsdclusters.com> (raw)
In-Reply-To: <402A3D11.7080704@gnu.org>

What would that look like?
Would you just type
(gdb) strace <args>

and have it print out what strace does now while it runs,
or do you have something more in mind?


		-Kip

On Wed, 11 Feb 2004, Andrew Cagney wrote:

> > Will strace command for you ?
>
> BTW, a wish-list item is for GDB to directly include strace support.
>
> enjoy,
> Andrew
>
>
> > -----Original Message-----
> > From: MuthuKumar-Hotpop [mailto:kmuthu_linux@HotPOP.com]
> > Sent: Wednesday, February 11, 2004 9:19 AM
> > Cc: gdb@sources.redhat.com
> > Subject: System calls debugging
> >
> >
> >
> > Hello deBUGies,
> >
> >         Is there any way to debug what are all the "system calls" usage and process happening over on the program.
> >
> >         I have written a simple program which gets the a string.I have made it to wait for the input and using that process-id,
> >         I have attached the process with gdb.Now the "where" command gives the stackframes about the system calls information.
> >         To find the processings of other system calls what is the way.
> >
> > Regards,
> > Muthu.
> >
> >
> >
>
>
>


  reply	other threads:[~2004-02-11 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11  3:55 Kotian, Deepak
2004-02-11 14:32 ` Andrew Cagney
2004-02-11 17:37   ` Kip Macy [this message]
2004-02-11 18:28     ` Andrew Cagney
2004-02-12 11:28       ` Muthukumar
  -- strict thread matches above, loose matches on Subject: below --
2004-02-12 11:35 Kotian, Deepak
2004-02-09 20:02 Pending breakpoints and scripts Andrew Cagney
2004-02-09 22:32 ` Daniel Jacobowitz
2004-02-10 21:22   ` Andrew Cagney
2004-02-10 22:26     ` Daniel Jacobowitz
2004-02-11  3:48       ` System calls debugging MuthuKumar-Hotpop

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=20040211093618.G17066@demos.bsdclusters.com \
    --to=kmacy@fsmware.com \
    --cc=cagney@gnu.org \
    --cc=gdb@sources.redhat.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