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

[Eli Zaretskii]

> From: Jean-Christophe Helary <address@hidden>
> Date: Thu, 3 May 2018 00:06:07 +0900
> 
> 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.


I didn't realize this was an Apple system...

> 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.

Do these errors, when you run as sudo, prevent GDB from displaying a
backtrace?  If so, I guess you will have to use LLDB instead.