From: DervishD <zsh@dervishd.net>
To: Deliverable Mail <deliverable@gmail.com>
Cc: zsh-users@sunsite.dk
Subject: Re: startup
Date: Tue, 30 Aug 2005 19:59:38 +0200 [thread overview]
Message-ID: <20050830175938.GA79@DervishD> (raw)
In-Reply-To: <7c737f30050830102367dfccb@mail.gmail.com>
Hi Alexy :)
* Deliverable Mail <deliverable@gmail.com> dixit:
> I have subtle problems running programs under gdb since I switched
> to zsh and configured a lot of aliases and zsh-specific things.
What kind of problems?
> For some reason, the examples .zshrc's I see do not distinguish
> between login shell and non-login one...
The zshrc and .zshrc files are read for ALL interactive shells,
no matter if they are login shells or not. If you want to do things
only for login shells, do them in zprofile and .zprofile files (and
zlogin and .zlogin, of course).
> How does zsh differentiates between them
Do you mean between a login shell and a not login shell? Well, if
zsh is invoked as "/bin/zsh -l" then it is a login shell, and if the
first character of the invocation name is '-' (for example, the
/bin/login program exec()'s the shell as -/bin/zsh).
> and what happens when gdb starts a process when run under zsh (does it
> even run zsh, or /bin/sh, and how do they interact)?...
They don't interact except if some environment variable affects
the behaviour of gdb, or maybe some tty setting. zsh will fork&exec
gdb, which in turn forks+exec+ptraces the debugged program (AFAIK).
Please, tell us (or better, since this doesn't seem to be
zsh-related, just tell *me* in private) which kind of problem do you
have when debugging programs and we look after a solution ;)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...
prev parent reply other threads:[~2005-08-30 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 17:23 startup Deliverable Mail
2005-08-30 17:59 ` DervishD [this message]
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=20050830175938.GA79@DervishD \
--to=zsh@dervishd.net \
--cc=deliverable@gmail.com \
--cc=zsh-users@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).