GNU bug report logs - #52295
windows 98: Killing text results in coding system complaint

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 52295 <at> debbugs.gnu.org
Subject: Re: bug#52295: 28.0.90; Killing text results in coding system complaint
Date: Tue, 07 Dec 2021 12:07:53 +0200

On December 7, 2021 11:20:10 AM GMT+02:00, Po Lu <luangruo <at> yahoo.com> wrote:
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Maybe 'intern' signals an error?  There's a check_obarray test inside
> > intern_1, which could signal an error.
> 
> No error is signalled:
> 
> > If you print the value which 'intern' returns in coding_from_cp, do
> > you see a nil value printed?
> 
> `nil' is printed in this case.
> 
> Thanks.
> 
> (I will not have access to that machine for a while, so I can't perform
> any further testing on it for the next week or so.)
> 

So I think there's no way around stepping into intern_1 and the functions it calls, and figuring out what happens there.  I thought you said GDB doesn't work on the target?  Then perhaps printfs will help?

Thanks.

Previous Next

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