From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Asynchronous DNS Date: Wed, 03 Feb 2016 11:42:57 +1100 Message-ID: <87k2mmzkry.fsf@gnus.org> References: <87si1gx6wz.fsf@gnus.org> <86y4b5zvzt.fsf@gmail.com> <8760y9kwrk.fsf@gnus.org> <87wpqpjgwy.fsf@gnus.org> <83a8nk1cxk.fsf@gnu.org> <87h9hrnc8x.fsf@gnus.org> <83powfzsqt.fsf@gnu.org> <87y4b393hl.fsf@gnus.org> <83io27ytu3.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1454460237 20235 80.91.229.3 (3 Feb 2016 00:43:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 3 Feb 2016 00:43:57 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 03 01:43:48 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aQlXu-0005m1-La for ged-emacs-devel@m.gmane.org; Wed, 03 Feb 2016 01:43:46 +0100 Original-Received: from localhost ([::1]:60119 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQlXq-0007nN-P9 for ged-emacs-devel@m.gmane.org; Tue, 02 Feb 2016 19:43:42 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52399) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQlXe-0007n7-9P for emacs-devel@gnu.org; Tue, 02 Feb 2016 19:43:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aQlXb-0005Lz-3F for emacs-devel@gnu.org; Tue, 02 Feb 2016 19:43:30 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:37793) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQlXa-0005Lv-Sk; Tue, 02 Feb 2016 19:43:27 -0500 Original-Received: from cpe-60-225-211-161.nsw.bigpond.net.au ([60.225.211.161] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1aQlXB-0008CP-R1; Wed, 03 Feb 2016 01:43:02 +0100 In-Reply-To: <83io27ytu3.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 02 Feb 2016 18:12:36 +0200") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1.50 (gnu/linux) X-MailScanner-ID: 1aQlXB-0008CP-R1 MailScanner-NULL-Check: 1455064983.12849@08l/9ROqI2EYJcFNmyPJpA X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:199201 Archived-At: Eli Zaretskii writes: > We need to know which code can run on a separate thread, because some > things cannot be safely done from any thread but the main > (a.k.a. "Lisp") thread. Running the Lisp interpreter is one of them, > but it's not the only one. You cannot QUIT or signal an error or do > anything else that throws to top-level. You cannot call malloc or > free, or any code that does. You cannot modify any data structures > visible from Lisp, like buffers, Lisp strings, and the undo list. You > cannot access or modify global variables or call any non-reentrant > Emacs functions. And there are other no-no's, these are just a few > that popped in my mind within the first 5 sec. Except the malloc thing, that just boils down to "you can't do anything Lispy on the other threads" I think? Which nobody has proposed, anyway. > However, it sounds like this is all much ado about nothing: I see no > references to any threads, old or new, in the changes you made on your > feature branch, so is there really anything to discuss here? (I asked > the question which led to this sub-thread because you mentioned that > you "start a new thread that does getaddrinfo".) No, I wrote that that's what getaddrinfo_a does, so we could just do that ourselves and not have to rely on getaddrinfo_a. >> Anyway, this reminds me of something that I've been wondering about gdb >> output when running Emacs. It often says something like this: >> >> warning: Corrupted shared library list: 0x84582e0 != 0x5104c30 >> warning: Corrupted shared library list: 0x2f172a0 != 0x21688a0 >> warning: Corrupted shared library list: 0x79f1910 != 0x21688a0 >> warning: Corrupted shared library list: 0x79f1910 != 0x21688a0 >> warning: Corrupted shared library list: 0x7a07ae0 != 0x21688a0 >> >> Is that something to be worried about, or is it... normal? > > It's a real problem. Crystal ball says that some of the system > libraries Emacs uses don't have debug info files to match them; > instead, you have debug info files from different versions of the > libraries. Try "info sharedlibrary" at the GDB prompt, maybe it will > tell you which libraries are the offending ones. Ok, but it's a problem when debugging in gdb, and not a problem for an Emacs running without gdb? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no