From: Daniel Jacobowitz <drow@false.org>
To: Konstantin Karganov <kostik@ispras.ru>
Cc: gdb@sources.redhat.com
Subject: Re: Debuggee cmd-line arguments bug
Date: Mon, 25 Jul 2005 14:24:00 -0000 [thread overview]
Message-ID: <20050725142445.GA4525@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0507251746140.20828-100000@ispserv.ispras.ru>
On Mon, Jul 25, 2005 at 05:59:31PM +0400, Konstantin Karganov wrote:
> 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?
No. If you provide any options on the "run" command line, you are
replacing the arguments set by set args. I think the text in section
4.3, "Your program's arguments", is pretty clear; please let us know if
it isn't.
> And what is about my previous posts (still unanswered) on:
Please don't reply to list messages to post to the list, by the way.
It messes up threading; you can see the problem in the list archives.
> - running out of source code (stepping past main)
> http://sources.redhat.com/ml/gdb/2005-07/msg00152.html
Your assumption that with step-mode set the PC will always be in user
code is incorrect. For instance, you could be stopped by a signal, or
by a user interrupt, or by a breakpoint in a function without source
code available.
> - incorrect breakpoint diagnostics in MI
> http://sources.redhat.com/ml/gdb/2005-07/msg00175.html
If someone knew the answer, they would have responded. Sorry, that
just happens sometimes.
> - vanishing stopping reason in MI
> http://sources.redhat.com/ml/gdb/2005-07/msg00173.html
>
> "And there's no doing anything about it" ?
You _got_ an answer. Bob agreed that there ought to be a reason.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-25 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 14:15 Konstantin Karganov
2005-07-25 14:24 ` Daniel Jacobowitz [this message]
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=20050725142445.GA4525@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kostik@ispras.ru \
/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).