Re: emacs locked when internet connection is cut...

[Jean-Christophe Helary <jean.christophe.helary@gmail.com>]

> On May 2, 2018, at 23:56, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
>> Date: Wed, 2 May 2018 15:56:27 +0900
>> 
>> I've reconfigured emacs to make debugging easier (./configure --enable-checking='yes,glyphs'
>> --enable-check-lisp-object-type CFLAGS='-O0 -g3') re-"make install"-ed it and launched gdb attached to its
>> PID.
>> 
>> I can't seem to be able to run gdb and attach emacs without getting a lot of error messages so I'm wondering
>> if there is a better way to get what you need to investigate into this issue.
> 
> Which error messages do you get?  They could be just warnings that can
> be disregarded, ore they could be problems that will get in the way
> when you run Emacs under GDB in any other way.  So please show the
> messages.

When I attach emacs to gdb from Emacs I get this:

Attaching to process 42692
Unable to find Mach task port for process-id 42692: (os/kern) failure (0x5).
 (please check gdb is codesigned - see taskgated(8))
(gdb) thread.c:1555: internal-error: scoped_restore_current_thread::scoped_restore_current_thread(): Assertion `tp != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

When I start gdb from the command line and attach emacs there I get this:
Attaching to process 42692
Unable to find Mach task port for process-id 42692: (os/kern) failure (0x5).
 (please check gdb is codesigned - see taskgated(8))

After investigating a bit it looks like running gdb as sudo fixes the thing (I could not create a certificate for it) but I still get this:

Attaching to process 42692
[New Thread 0x1503 of process 42692]
[New Thread 0x1603 of process 42692]
[New Thread 0x1703 of process 42692]
[New Thread 0x1803 of process 42692]
[New Thread 0x2803 of process 42692]
[New Thread 0x2903 of process 42692]
Reading symbols from /Users/suzume/Documents/Code/emacs/nextstep/Emacs.app/Contents/MacOS/Emacs...done.
Error while mapping shared library sections:
`/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit': not a shared-library: File format not recognized
Error while mapping shared library sections:
`/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit': not a shared-library: File format not recognized
Error while mapping shared library sections:
`/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon': not a shared-library: File format not recognized
Error while mapping shared library sections:
`/usr/lib/libSystem.B.dylib': not a shared-library: File format not recognized
Error while mapping shared library sections:
`/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation': not a shared-library: File format not recognized
Error while mapping shared library sections:
`/usr/lib/libxml2.2.dylib': not a shared-library: File format not recognized

and a big bunch of other similar errors.

Jean-Christophe 

> Hoe to run Emacs under GDB in a way that will allow you to get control
> back to GDB is described in etc/DEBUG.  However, attaching GDB to a
> running Emacs is much easier, so maybe it's worth your while to invest
> some additional effort into trying to use that.

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune