GNU bug report logs - #21528
25.0.50; gud tries to guess what file we're debugging, which can take a long time

Previous Next

Full log

Message #26 received at 21528 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 21528 <at> debbugs.gnu.org, Dima Kogan <dima <at> secretsauce.net>
Subject: Re: bug#21528: 25.0.50; gud tries to guess what file we're
 debugging, which can take a long time
Date: Mon, 24 Jan 2022 14:56:59 +0100

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

>> Both of those could be true, but probably not all that often. Especially
>> the "program is executable part" easily fails for interpreted languages.
>
> How about bypassing this search in 2 situations:
>
>  . the debuggee is on a remote system
>  . the debugger being invoked is for an interpreted language
>
> Would that be "good enough"?

I don't think it's all that useful to separate interpreted vs compiled
here -- it'll be slow (or not) in any case (and interpreted files are
normally executable).

So I've just made it not do the loop if it's on a remote system, and
there's a lot of files there in Emacs 29.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

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