From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14254 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: dalias Newsgroups: gmane.linux.lib.musl.general Subject: Re: Child process is blocked when debugging with gdb Date: Fri, 21 Jun 2019 16:31:32 -0400 Message-ID: <20190621203132.GZ1506@brightrain.aerifal.cx> References: <824f0993-245f-4238-9a38-21d0960ae9bc.xulu@allwinnertech.com> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="255995"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) Cc: musl@lists.openwall.com To: =?utf-8?B?5b6Q6Zyy?= Original-X-From: musl-return-14270-gllmg-musl=m.gmane.org@lists.openwall.com Fri Jun 21 22:31:57 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1heQCP-0014Na-JA for gllmg-musl@m.gmane.org; Fri, 21 Jun 2019 22:31:53 +0200 Original-Received: (qmail 23838 invoked by uid 550); 21 Jun 2019 20:31:50 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 23815 invoked from network); 21 Jun 2019 20:31:50 -0000 Content-Disposition: inline In-Reply-To: <824f0993-245f-4238-9a38-21d0960ae9bc.xulu@allwinnertech.com> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:14254 Archived-At: On Tue, Jun 11, 2019 at 11:46:52AM +0800, 徐露 wrote: > Hi all, > > I use Openwrt project and the version of musl-libc is 1.1.16. > > I call wordexp() in my programs and it runs well. But when I debug my programs with gdb, it is blocked on wordexp(). > After some tests, I found that wordexp() call fork(), and after fork the child process is blocked. > > I write a demo and the source code is as follows. > ``` > #include > #include > int main() > { > pid_t pid; > pid = fork(); > if (!pid) { > printf("== child process ==\n"); > while (1) { > printf("--child--\n"); > sleep(1); > } > } > printf("== parent process ==\n"); > sleep(20); > return 0; > } > ``` > > The debug log is as follows. > ``` > root@Linux:/# gdb /test > GNU gdb (GDB) 8.2.1 > Copyright (C) 2018 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "arm-openwrt-linux". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > . > Find the GDB manual and other documentation resources online at: > . > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from /test...done. > (gdb) show follow-fork-mode > Debugger response to a program call of fork or vfork is "parent". > (gdb) show detach-on-fork > Whether gdb will detach the child of a fork is on. > (gdb) r > Starting program: /test > [Detaching after fork from child process 1697] > == parent process == > [Inferior 1 (process 1694) exited normally] > (gdb) > ``` > When the parent process is sleeping, I get these processes information. > ``` > root@Linux:/# ps | grep test > 1692 root 10916 S gdb /test > 1694 root 680 S /test > 1697 root 680 t /test > 1706 root 1072 S grep test > ``` > > I have set gdb "follow-fork-mode" to "child", the child process can run, but I want to debug the parent process. > > Besides, I have tried GDB 7.10.1 and musl-libc 1.1.22, the question still exists. > I also have swithed the C library to Glibc, and there is no question. > > Could you please give us some pointers, thanks! I can supply more details as needed. Sorry I missed this when you first sent it! wordexp() reads back output from the child via a pipe, so the child will stay blocked on writing to the pipe if it writes more than the pipe buffer size without the parent reading anything back. You'll need to let the parent advance past these reads before the child can exit. Does that help? Rich