public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make STARTUP_WITH_SHELL a runtime toggle -- add new "set/show startup-with-shell" option.
Date: Wed, 23 Oct 2013 15:38:00 -0000	[thread overview]
Message-ID: <83ppqwhu98.fsf@gnu.org> (raw)
In-Reply-To: <1382532024-28890-1-git-send-email-palves@redhat.com>

> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 23 Oct 2013 13:40:24 +0100
> 
> Occasionaly we hear about people having problems with GDB not being
> able to start programs (with "run"/"start").  GDB spawns a shell to
> start the program, and most often, it'll be the case that the problem
> is actually with the user's shell setup.
> 
> GDB has code to disable the use of the shell to start programs.
> That's the STARTUP_WITH_SHELL macro that native targets could set to 0
> in their nm.h file (though no target actually uses it nowadays).
> 
> This patch makes that setting a run-time knob instead.  This will be
> useful to quickly diagnose such shell issues, and might also come in
> handy at other times (such as when debugging the shell itself, if you
> don't have a different shell handy).

Thanks.

> Comments?  Are the docs OK?

The docs are OK with a few comments.

> +@smallexample
> +(@value{GDBP}) During startup program terminated with signal SIGSEGV, Segmentation fault.
> +@end smallexample

This line is too long, it will cause overflow of the page boundaries.

> +which indicates the shell or the wrapper specified with
> +@samp{exec-wrapper} crashed, not your program.  Most often, this is
> +caused by something odd in your shell's initialization file---such as
> +@file{.cshrc} for C-shell, or @file{.bashrc} for BASH.  To help
> +diagnose such issues, you can disable use of a shell with @kbd{set
> +startup-with-shell off}.

There should be a prominent note here to the effect that invoking the
inferior bypassing the shell disables command-line redirection.

OK with those changes.

  parent reply	other threads:[~2013-10-23 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 12:40 Pedro Alves
2013-10-23 13:38 ` Gary Benson
2013-10-23 13:41 ` Andreas Schwab
2013-10-23 14:49   ` Pedro Alves
2013-10-25 11:11     ` [PATCH] [DOC] shell startup files, clarifications and fixes. (was: Re: [PATCH] Make STARTUP_WITH_SHELL a runtime toggle -- add new "set/show startup-with-shell" option.) Pedro Alves
2013-11-05 17:56       ` [PATCH] [DOC] shell startup files, clarifications and fixes Pedro Alves
2013-11-05 18:06         ` Eli Zaretskii
2013-11-06 12:30           ` Pedro Alves
2013-10-23 15:38 ` Eli Zaretskii [this message]
2013-10-24 15:17   ` [PATCH] Make STARTUP_WITH_SHELL a runtime toggle -- add new "set/show startup-with-shell" option Pedro Alves
2014-01-08 21:21     ` Thomas Schwinge
2014-01-09 12:10       ` Pedro Alves

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=83ppqwhu98.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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).