Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] gcore command script
Date: Thu, 17 Apr 2003 17:41:00 -0000	[thread overview]
Message-ID: <3E9EE73F.6D753CF7@redhat.com> (raw)
In-Reply-To: <16030.42551.529787.466304@localhost.redhat.com>

Elena Zannoni wrote:
> 
> This is a script that can be used to generate a core file for a given
> process. It works by invoking gdb on the process, and using the gcore
> command.
> 
> It was originally written by Michael Snyder, I think.

Michael Snyder and Karen Bennet.
 
> I picked the name gdb_gcore.sh. Seemed right at the moment.
> 
> On a side note, should we have a 'scripts' subdirectory in gdb?

Seems like we're getting to that point...


> --- /dev/null   Thu Apr 11 10:25:15 2002
> +++ src/gdb/gdb_gcore.sh        Mon Mar 31 17:28:28 2003
> @@ -0,0 +1,81 @@
> +#!/bin/sh
> +
> +#   Copyright 2003  Free Software Foundation, Inc.
> +
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 2 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program; if not, write to the Free Software
> +# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
> +
> +# Please email any bugs, comments, and/or additions to this file to:
> +# bug-gdb@prep.ai.mit.edu
> +
> +#
> +# gdb_gcore.sh
> +# Script to generate a core file of a running program.
> +# It starts up gdb, attaches to the given PID and invokes the gcore command.
> +#
> +
> +if [ "$#" -eq "0" ]
> +then
> +    echo "usage:  gcore [-o filename] pid"
> +    exit 2
> +fi
> +
> +# Need to check for -o option, but set default basename to "core".
> +name=core
> +
> +if [ "$1" = "-o" ]
> +then
> +    if [ "$#" -lt "3" ]
> +    then
> +       # Not enough arguments.
> +       echo "usage:  gcore [-o filename] pid"
> +       exit 2
> +    fi
> +    name=$2
> +
> +    # Shift over to start of pid list
> +    shift; shift
> +fi
> +
> +# Initialise return code.
> +rc=0
> +
> +# Loop through pids
> +for pid in $*
> +do
> +       # Write gdb script for pid $pid.
> +
> +       # Avoid need for temporary files by using funky "here
> +       # document" feature of sh.
> +
> +       /usr/bin/gdb > /dev/null << EOF
> +       attach $pid
> +       gcore $name.$pid
> +       detach
> +       quit
> +EOF
> +
> +       if [ -r $name.$pid ] ; then
> +           rc=0
> +       else
> +           echo gcore: failed to create $name.$pid
> +           rc=1
> +           break
> +       fi
> +
> +
> +done
> +
> +exit $rc
> +


  reply	other threads:[~2003-04-17 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 12:59 Elena Zannoni
2003-04-17 17:41 ` Michael Snyder [this message]
2003-04-17 20:35   ` Elena Zannoni

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=3E9EE73F.6D753CF7@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@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