Re: Emacs 28 on OSX: emacsclient.c:1415: warning: implicit declaration of function 'openat'

[Alan Third]

On Fri, Apr 22, 2022 at 02:29:34PM -0700, Keith David Bershatsky wrote:
> I observed a lot of leaking messages when building Emacs master branch on OSX 
> 10.6.8, and the initial output of gdb is as follows.  Is this anything that 
> needs to be addressed?
> 
> Starting program: 
> /Users/HOME/Desktop/emacs/nextstep/Emacs.app/Contents/MacOS/Emacs 
> 2022-04-22 14:24:31.450 Emacs[15180:60f] *** __NSAutoreleaseNoPool(): Object 
> 0x100918460 of class NSPathStore2 autoreleased with no pool in place - just 
> leaking
> 2022-04-22 14:24:31.453 Emacs[15180:60f] *** __NSAutoreleaseNoPool(): Object 
> 0x10091c290 of class NSPathStore2 autoreleased with no pool in place - just 
> leaking
> 2022-04-22 14:24:31.454 Emacs[15180:60f] *** __NSAutoreleaseNoPool(): Object 
> 0x1009185f0 of class NSCFString autoreleased with no pool in place - just 
> leaking
> 2022-04-22 14:24:31.454 Emacs[15180:60f] *** __NSAutoreleaseNoPool(): Object 
> 0x10091cc40 of class NSCFArray autoreleased with no pool in place - just 
> leaking
> 2022-04-22 14:24:31.454 Emacs[15180:60f] *** __NSAutoreleaseNoPool(): Object 
> 0x10091cd30 of class NSPathStore2 autoreleased with no pool in place - just 
> leaking
> 2022-04-22 14:24:31.455 Emacs[15180:60f] *** __NSAutoreleaseNoPool(): Object 
> 0x10091ce90 of class NSCFData autoreleased with no pool in place - just 
> leaking

To be honest, I'm unsure as I don't know where in the code those leaks
are occurring. I guess it's maybe possible to put a breakpoint on
__NSAutoreleaseNoPool and then get a backtrace when it's caught, but I
don't see these messages here so I suspect you'd have to do that work.

Do the messages continue as you use Emacs or are they just at startup?
-- 
Alan Third