emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Asynchronous DNS


From: Lars Ingebrigtsen
Subject: Re: Asynchronous DNS
Date: Tue, 02 Feb 2016 04:48:38 +0100
User-agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1.50 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

> Of course it does.  It's a major architecture change that we should
> know about, and probably discuss before doing.

Ok.  :-)  The last time this was discussed, I mentioned threads and I
think the response was basically "sure, if you can get it to work"...

What problems do you see with stopping/starting threads in Emacs (that
do no Lisp-related stuff)?  I'm assuming there are plenty of libraries
that Emacs uses that already does this behind Emacs' back, and we don't
seem to care...

For instance, if we run the current trunk under gdb, it says:


DISPLAY = :0
TERM = xterm-256color
Breakpoint 1 at 0x4eeef0: file emacs.c, line 354.
Temporary breakpoint 2 at 0x508260: init_sys_modes. (3 locations)
(gdb) run
Starting program: /home/larsi/src/emacs/trunk/src/emacs 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe5cad700 (LWP 18679)]
[New Thread 0x7fffe4e86700 (LWP 18680)]
[New Thread 0x7fffdffff700 (LWP 18681)]

Running eww or Gnus will output a lot of

[New Thread 0x7fffdde17700 (LWP 18698)]
[New Thread 0x7fffdd3f0700 (LWP 18700)]
[New Thread 0x7fffdcbef700 (LWP 18701)]
[Thread 0x7fffdcbef700 (LWP 18701) exited]
[Thread 0x7fffdd3f0700 (LWP 18700) exited]

So...

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?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



reply via email to

[Prev in Thread] Current Thread [Next in Thread]