Hello,

On Mon 22 Aug 2022 at 02:55AM +02, Vincent Lefevre wrote:

> Control: found -1 1:28.1+1-2
> Control: severity -1 serious
>
> On 2022-08-19 12:10:31 +0200, Vincent Lefevre wrote:
>> I have noticed that Emacs left a 137 MB coredump.
>
> This has occurred again (this time a 54 MB coredump).
> This is going to use much disk space...
>
>> gdb says:
>>
>> Reading symbols from /usr/bin/emacs...
>> Reading symbols from 
>> /usr/lib/debug/.build-id/d0/b7c40dc33110b0623ea2ca797a6d3f3eb166b5.debug...
>> [New LWP 1483812]
>> [New LWP 1483816]
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> Core was generated by `/usr/bin/emacs --batch -l 
>> /tmp/emacs-async-comp-cc-engine.el-2UV1nf.el'.
>
> This time,
>
> Core was generated by `/usr/bin/emacs --batch -l 
> /tmp/emacs-async-comp-auth-source.el-84YT0a.el'.
> Program terminated with signal SIGABRT, Aborted.
>
> I'm wondering whether this is related to bug 1017845, as a
> "/usr/bin/emacs --batch -l /tmp/emacs-async-..." is also involved.

Can you reproduce this with what's in sid now?

It may have been fixed by adding the emacs-el dependency.

Thanks.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature

Reply via email to