Date: Sat, 27 Jun 2020 12:06:17 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Li-Wen Hsu <lwhsu@freebsd.org>, "Conrad E. Meyer" <cem@FreeBSD.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: weird Ctrl-T debug messages Message-ID: <14d1708f-74cc-4a60-3282-3308eb24743e@FreeBSD.org> In-Reply-To: <CAKBkRUx-TTWUxPJGiiyMxVFFK=v2is5Rc4QruiNgchWf_WY7Dg@mail.gmail.com> References: <20200627090406.68b5d637@hermann.fritz.box> <CAKBkRUx-TTWUxPJGiiyMxVFFK=v2is5Rc4QruiNgchWf_WY7Dg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27/06/2020 10:44, Li-Wen Hsu wrote: > On Sat, Jun 27, 2020 at 3:04 PM Hartmann, O. <ohartmann@walstatt.org> wrote: >> >> Running poudriere on recent CURRENT with (recent) 12-STABLE and CURRENT >> jails reveals a weird behaviour recently when hitting Ctrl-T: > ... >> Is this debug fallout from /bin/sh? > > It's because kern.tty_info_kstacks is on by default now: > > https://svnweb.freebsd.org/changeset/base/362141 May I suggest that the stack trace is printed procstat -kk style (single line) ? I think that the more compact output would be more convenient. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14d1708f-74cc-4a60-3282-3308eb24743e>