GNU bug report logs - #75477
31.0.50; scratch/igc: crash on the latest commit

Previous Next

Full log

Message #100 received at 75477-done <at> debbugs.gnu.org (full text, mbox):

From: Pip Cet <pipcet <at> protonmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Ihor Radchenko <yantar92 <at> posteo.net>, 75477-done <at> debbugs.gnu.org
Subject: Re: bug#75477: 31.0.50; scratch/igc: crash on the latest commit
Date: Fri, 21 Feb 2025 18:05:08 +0000

"Eli Zaretskii" <eliz <at> gnu.org> writes:

>> Cc: 75477 <at> debbugs.gnu.org
>> From: Ihor Radchenko <yantar92 <at> posteo.net>
>> Date: Thu, 30 Jan 2025 19:48:08 +0000
>>
>> Pip Cet <pipcet <at> protonmail.com> writes:
>>
>> > Not trying to stop you or anything, but we would like to know more about
>> > what is causing those slowdowns.  If you're too frustrated now, you can
>> > save a coredump (gdb command gcore) and save it along with the emacs
>> > binary and emacs.pdmp somewhere :-)
>> >
>> > Just if you want to, that is.
>>
>> I got an impression that the priority for now is getting rid of the
>> crashes and other critical problems. If I am wrong, I can happily start
>> reporting about performance problems.
>
> Please do.  We are interested in fixing all kinds of problems with
> this branch.

I'm closing this bug because the problems described appear to have been
fixed or warrant new bug numbers.

Pip

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.