public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Konstantin Karganov <kostik@ispras.ru>
To: gdb@sources.redhat.com
Subject: Debuggee cmd-line arguments bug
Date: Mon, 25 Jul 2005 14:15:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0507251746140.20828-100000@ispserv.ispras.ru> (raw)

Hello.

Playing with the program startup arguments I've found the following 
"feature" of gdb. I have a program that prints its argc/argv parameters.

(gdb) set args a b c d
(gdb) run
Starting program: /home/kostik/Work/a.out a b c d
Argc=5, Argv=/home/kostik/Work/a.out,a,b,c,d
 
Program exited normally.
(gdb) set args a b c d
(gdb) run >out
Starting program: /home/kostik/Work/a.out >out

Program exited normally.
(gdb)

In file out there are the folowing:

Argc=1, Argv=/home/kostik/Work/a.out

So when trying to redirect debuggee IO we've lost all cmd-line parameters.
The same of cource happens with MI (and breaks the debugging startup for 
MPI program!).

Is it a bug?

And what is about my previous posts (still unanswered) on:

- running out of source code (stepping past main)
  http://sources.redhat.com/ml/gdb/2005-07/msg00152.html

- incorrect breakpoint diagnostics in MI
  http://sources.redhat.com/ml/gdb/2005-07/msg00175.html

- vanishing stopping reason in MI
  http://sources.redhat.com/ml/gdb/2005-07/msg00173.html

"And there's no doing anything about it" ?


Best regards,
Konstantin.


             reply	other threads:[~2005-07-25 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 14:15 Konstantin Karganov [this message]
2005-07-25 14:24 ` Daniel Jacobowitz
2005-07-25 18:21   ` Konstantin Karganov
2005-07-25 18:24     ` Daniel Jacobowitz

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=Pine.LNX.4.44.0507251746140.20828-100000@ispserv.ispras.ru \
    --to=kostik@ispras.ru \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).