This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/209: Feature request: Pass subprogram command options on gdb command line
- To: gdb-gnats at sources dot redhat dot com
- Subject: gdb/209: Feature request: Pass subprogram command options on gdb command line
- From: gdb at treblig dot org
- Date: 9 Sep 2001 12:41:37 -0000
- Reply-To: gdb at treblig dot org
>Number: 209
>Category: gdb
>Synopsis: Feature request: Pass subprogram command options on gdb command line
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sun Sep 09 05:48:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Dr. David Alan Gilbert
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
Hi,
I would find useful a feature where you could do:
gdb --anoption programtorun programoptions
and which it would then run the program and only bring up a command line
if a signal was received (the exact condition of this should probably a little
more configurable).
The case I am trying to debug is a command being called from a shell script with some pretty hairy command line options and doing gdb programtorun and then copying the options in to the 'run' line is a serious pain.
It would also be useful with intermittent errors where you could replace the victim program with a shell script of the form:
gdb --theoption program.real $*
(Thanks for your good work on gdb - I have used it for many years but am
shamed by the fact I don't think I've ever said 'thanks'!)
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: