This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/649: ``(gdb) strace'' command
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 15 Aug 2002 01:08:00 -0000
- Subject: Re: gdb/649: ``(gdb) strace'' command
- Reply-to: Daniel Jacobowitz <drow at mvista dot com>
The following reply was made to PR gdb/649; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@mvista.com>
To: ac131313@redhat.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/649: ``(gdb) strace'' command
Date: Wed, 14 Aug 2002 20:59:47 -0400
On Wed, Aug 14, 2002 at 11:57:30PM -0000, ac131313@redhat.com wrote:
>
> >Number: 649
> >Category: gdb
> >Synopsis: ``(gdb) strace'' command
> >Confidential: no
> >Severity: serious
> >Priority: medium
> >Responsible: unassigned
> >State: open
> >Class: change-request
> >Submitter-Id: net
> >Arrival-Date: Wed Aug 14 16:58:01 PDT 2002
> >Closed-Date:
> >Last-Modified:
> >Originator: ac131313@redhat.com
> >Release: 2002-08-14
> >Organization:
> >Environment:
>
> >Description:
> You know things are bad when you're reduced to modifying code to read:
>
> fprintf (stderr, "msg 1\n");
> gettext ("message");
> fprintf (stderr, "msg 2\n");
>
> and then looking at strace output, you know things are bad. Suggest a new command (strace?) that works something like:
>
> 10 gettext ("message");
> (gdb) set strace on
> (gdb) next
> open("/non/existant/file", 0) = -1, ENOENT
> 11 fprintf (...);
Your timing is again impeccable... I seem to be telling people that a
lot recently...
I'm in the middle of adding catchpoints for fork/vfork/execve to the
Linux port. It'll take me a little time to clean them, and then I hope
to move on to system call tracing. There's some discussion going on
right now about producing a library we can use from the strace code.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer