From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Extend gdb to filter registers Date: Sat, 25 Jan 2020 09:58:49 +0100 Message-ID: References: <83v9pb314t.fsf@gnu.org> <838sm510d6.fsf@gnu.org> <83muakzoy5.fsf@gnu.org> <71042c9f-478b-47c8-f27e-1348e9f4536d@gmx.at> <83iml8zkbm.fsf@gnu.org> <6ad85759-7408-f177-38f6-45a72c2f5a9e@gmx.at> <83eevwzi79.fsf@gnu.org> <68ef651e-9319-b392-af1c-4564d5db9112@gmx.at> <831rrvzc81.fsf@gnu.org> <997C9AD2-D8DD-45DC-9195-28FEC907B2C4@gmail.com> <83muajxs04.fsf@gnu.org> <416593FF-C4BE-478F-B5AC-3379235146ED@gmail.com> <83lfq3xp66.fsf@gnu.org> <679953AF-F50A-4ABE-B836-150BA0F95DAE@gmail.com> <83h80rxlae.fsf@gnu.org> <8A5A507A-6036-4894-A8B1-749109EBE605@gmail.com> <83wo9mvwco.fsf@gnu.org> <2BEA3843-859E-481B-8561-35384438EF7F@gmail.com> <83lfpxs4sl.fsf@gnu.org> <83zhecoseo.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="59145"; mail-complaints-to="usenet@ciao.gmane.io" Cc: juri@linkov.net, john@yates-sheets.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii , Yuan Fu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 25 10:02:00 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ivHKI-000FKc-W5 for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jan 2020 10:01:58 +0100 Original-Received: from localhost ([::1]:52032 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ivHKH-0000lx-TZ for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jan 2020 04:01:58 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47282) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ivHHS-0008Kf-Ln for emacs-devel@gnu.org; Sat, 25 Jan 2020 03:59:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ivHHR-0000nX-J8 for emacs-devel@gnu.org; Sat, 25 Jan 2020 03:59:02 -0500 Original-Received: from mout.gmx.net ([212.227.15.19]:56529) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ivHHP-0000lc-Jh; Sat, 25 Jan 2020 03:58:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1579942731; bh=gfMEWlPj9uAlGowUYWpPlIIlFiZrWcEiXDXmf/zz5CA=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=N7B0stdsP8Z1kmS8lFPQdFh1klpZ8ayo/nqQLlrmFtTfuhl4tkp6g3DA4n8prJ8MP dd/hWlIQ3C4PApxX0uaM71xSh2x8Dtjp6WVtWEt0jTUoIvd4SW20eDsUcKNOuD0a6J 81iTPMXjkom5CQBmry/Eqylw5wGLVfXVcYB4IC8g= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.101] ([212.95.5.109]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M7sHo-1j0F5t0BSU-0050CN; Sat, 25 Jan 2020 09:58:51 +0100 In-Reply-To: <83zhecoseo.fsf@gnu.org> Content-Language: en-US X-Provags-ID: V03:K1:MsW/zwx7szNcUYlI0NRLuD66X+akDTk6QygjJ5ud/rVuEIEkwQS r8HDJ3/w5/bP/QdZvQ6QLm2HYPSAhrQ86+d5/TxNvF16XZvPJFv5I/nzoaw5o/GuAiQWBqz tuQ5oz+LOU8ghZ2gUCp3Cwt2iGw2F5+lMVZGg3d9j1Te6b3uy+h5BGBsmDKaJGDpojiP+sM A3WRlxIRN+A+r0VAGV9Zw== X-UI-Out-Filterresults: notjunk:1;V03:K0:e02ugCb1IFo=:wu7SORUFB2k2JyP4khvtRM uDDlDjPiXS4t+p5EhRTwSTS+grH5i+wMyKlTqLTAuzPVPAmqdH+vvt9ZWGeckW5XD0fc3YbHn hWWn+ue4+a84eisF9wq7rbZsEVc8eW0UICWYCWv4hUmykg/WdLV7RFd/ZUzjVvqtC7N5leIeZ Q75H3p6RC+/zp1OmxHZrT5ONfl8lTxJ9RmRuxpq7GqcrWEXGZUJcV0tSWAf6RZGBA7gdqoW0t 2Vsu9+yut3jhhzVxjh9qLbWP2MLDK1acOJlzIa/cTNQ+cGr+UkOO60ZyhK6M+p/Qg4hjKGyxV SA4hXjwW6exqo8VpxppvvwuBFmkymoldQvVZuFmIejlNa7A8GH8kdyYigKI4ys73AGcVXSNWl FhBy13rkcefIX5DZPLSJnjIaVRIiYKPwLxHAE65bSzXbTMwhvnTa0+fZU6dwr+riwdKhg41u/ 7GWw6hCDGwxqV3ZoxsJA5YWMLM/MG9ujOgp3bqgItjCduBEzmOvLRJjbSRuSA1pYQJIYGdUAO J/IBCglkR13VbhPEqrSM0el5iIygHMf2z+smmWlMqnsGpND9P1jBpRhr5POA/H0iHDAZuQu9v xuFwuAmYDGIJGCS/b6P5w0l+iitol9pqEggECoM6RdVFNmlU1O5czN+LGGaNtD7grAgBnDeJZ BGWGV8E9cfFjxdgUEtlO7TO/Mju90mfKAVCvvYwuraKI/98akl4CS0+IGaJdWnur0eTIedJn1 FEJqcAwZaMQe+mChdWqpxrZllo58/RlhEejNW+IZzPcisDxjCR82mu5+zcnDzP6wuRd5KP7j X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.15.19 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:244607 Archived-At: >> I still haven=E2=80=99t had a clear idea on =E2=80=9Chow to open the = new window=E2=80=9D part. In the previous patch I simply used >> display-window-pop-window so the code works, but we should definitely= come up with something else. >> Currently my naive idea is to use (display-buffer buffer gdb-display-= source-buffer-action), where >> gdb-display-source-buffer-action can be customized by user. WDYT? > > Sounds OK, but I'd still like to hear martin's views on this. I think gdb could provide customizations via one or more customizable actions but always let users override them via their own buffer display customizations. >> I don't understand this part: wasn't the original motivation to cau= se >> gdb-mi to _always_ reuse the source window? >> >> You have the choice. If I want gdb to always reuse the window, I can = set the number to 1. > > Yes, I think we should probably start at 1 and let users customize > that if they want to. I agree that having always one source window should be the, somewhat austere, default behavior. > No, the usual complaint is that gdb-mi messes up windows during the > debugging session itself. E.g., if you had several source files > displayed in carefully configured windows on a frame, starting > "M-x gdb" will typically mess up your window configuration on that > frame. Using a separate frame works around that. But only if you have not customized 'reusable-frames' and 'pop-up-frames'. > That could be another way, but running a debugging session usually > benefits from maximizing the frame. Funnily, I always unmaximize my frame when running a debugging session. How could I otherwise see the debuggee's frame? martin