From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Madhu Newsgroups: gmane.emacs.devel Subject: Re: Possible XInput2 cursor bug ? Date: Sun, 12 Dec 2021 23:45:41 +0530 (IST) Message-ID: <20211212.234541.993962340401484244.enometh@meer.net> References: <83ilvup9lx.fsf@gnu.org> <20211212.202502.2129015728198180732.enometh@meer.net> <83czm1oo82.fsf@gnu.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13348"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: eliz@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 12 19:16:43 2021 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 1mwTOt-0003FX-C1 for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Dec 2021 19:16:43 +0100 Original-Received: from localhost ([::1]:38536 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mwTOr-0004tV-Tt for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Dec 2021 13:16:42 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:53324) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mwTNf-00049P-B3 for emacs-devel@gnu.org; Sun, 12 Dec 2021 13:15:27 -0500 Original-Received: from smtp6.ctinetworks.com ([205.166.61.199]:43824) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mwTNd-0003WK-AJ; Sun, 12 Dec 2021 13:15:27 -0500 Original-Received: from localhost (unknown [117.254.34.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: enometh@meer.net) by smtp6.ctinetworks.com (Postfix) with ESMTPSA id C6254815C5; Sun, 12 Dec 2021 13:15:18 -0500 (EST) In-Reply-To: <83czm1oo82.fsf@gnu.org> X-Mailer: Mew version 6.8 on Emacs 29.0.50 X-ctinetworks-Information: Please contact the ISP for more information X-ctinetworks-MailScanner-ID: C6254815C5.A80B4 X-ctinetworks-VirusCheck: Found to be clean X-ctinetworks-Watermark: 1640196923.52448@QhD2WR3xjKgVRjum5sj/fA Received-SPF: pass client-ip=205.166.61.199; envelope-from=enometh@meer.net; helo=smtp6.ctinetworks.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:281805 Archived-At: * Eli Zaretskii <83czm1oo82.fsf@gnu.org> Wrote on Sun, 12 Dec 2021 17:08:13 +0200 >> Date: Sun, 12 Dec 2021 20:25:02 +0530 (IST) >> From: Madhu >> That helps a lot. (It brings down the RES reported in top to 2.5G >> in jit builds, I may be misinterpreting what I'm seeing but a >> non-native build shows only some 100M in use by gdb) > On my system, debugging a natively-compiled Emacs takes GDB just a bit > more that debugging non-native one: 120MB vs 100MB. The first number > is similar to yours, so I wonder how come the second number is so much > different on you're system. Is that with "emacs -Q" run under a > debugger? In any case, a full Emacs version running for 10 days under > GDB causes GDB to have just 200MB of memory here, which is a far cry > from your 2.5GB. I wonder why such a large difference. yes for emacs -Q -D. I can confirm that by the time I get to the end of the first backtrace I have 2GB rss in a native build, and about 100M RSS for a non-native build. I do have some system libraries (glib, etc.) compiled with debug info, but that doesn't explain the difference. > Yes, but regenerating the *.eln files takes a few minutes, so why is > that such a big problem? It takes a little longer for me and it's wasteful if youre just going to throw it away anyway. >> But I hit another problem. When I edited xterm.c and hit `make' emacs >> was built but is not able to run, I got a >> >> emacs: Trying to load incoherent dumped eln file /12/build/emacs/build-xt/native-lisp/29.0.50-473a9dd2/preloaded/subr-13adf6a6-a6425de0.eln > > Look closer at the build process, something probably failed there, so > the build didn't complete successfully. [I couldn't spot it, but a ./configure and build fixed it after recompiling all the c files while retaining the same eln directory (i think) ]