List Info

Thread: Re: Crash in handling tar files (Was: GDB debugger mode for Emacs in ELPA)




Re: Crash in handling tar files (Was: GDB debugger mode for Emacs in ELPA)
country flaguser name
India
2008-07-01 05:07:38
Hi,

----- Original Message ----
> From: Eli Zaretskii <elizgnu.org>
> > (gdb) bt
> > #0  0x0119eaf3 in re_search_2 (bufp=0x1376420,
str1=0x388a160 "ostfix 
> modifiers"n
"quail/latin-alt")n(register-input-methodn 
> "latin-3-alt-postfix" "Latin-3"
'quail-use-packagen "3<" "Latin-3 char
> 
> This is strange text!  What is your value of
auto-coding-regexp-alist?

(("^BABYL OPTIONS:[     ]*-\*-[     ]*rmail[    
]*-\*-" . no-conversion) ("\`þÿ" .
utf-16be-with-signature) ("\`ÿþ" .
utf-16le-with-signature) ("\`" . utf-8)
("\`;ELC

I am running 'emacs -q --no-site-file' on WXP built with
MinGW and see the above value

> Do you have any idea why
auto-coding-regexp-alist-lookup ended up
> looking at the string pointed to by str1 above?

Not a clue!

-dhruva



      Bring your gang together. Do your thing. Find your
favourite Yahoo! group at http://in.promos.y
ahoo.com/groups/




Re: Crash in handling tar files (Was: GDB debugger mode for Emacs in ELPA)
user name
2008-07-04 05:08:45
> Date: Tue, 1 Jul 2008 15:37:38 +0530 (IST)
> From: filerz-emacsyahoo.com
> Cc: emacs-develgnu.org
> 
> > From: Eli Zaretskii <elizgnu.org>
> > > (gdb) bt
> > > #0  0x0119eaf3 in re_search_2
(bufp=0x1376420, str1=0x388a160 "ostfix 
> > modifiers"n
"quail/latin-alt")n(register-input-methodn 
> > "latin-3-alt-postfix"
"Latin-3" 'quail-use-packagen
"3<" "Latin-3 char
> > 
> > This is strange text!  What is your value of
auto-coding-regexp-alist?
> 
> (("^BABYL OPTIONS:[     ]*-\*-[     ]*rmail[    
]*-\*-" . no-conversion) ("\`þÿ" .
utf-16be-with-signature) ("\`ÿþ" .
utf-16le-with-signature) ("\`" . utf-8)
("\`;ELC
> 
> I am running 'emacs -q --no-site-file' on WXP built
with MinGW and see the above value
> 
> > Do you have any idea why
auto-coding-regexp-alist-lookup ended up
> > looking at the string pointed to by str1 above?
> 
> Not a clue!

In that case, my guess is that this is the result of some
memory
mess-up, perhaps a GC with un-GCPRO'ed variables.  That
could explain
the strange text we see in regex search initiated by
auto-coding-regexp-alist-lookup, since GC could relocate
strings.

Unfortunately, I will be traveling for 3 weeks starting
tomorrow, so I
probably won't have time to debug this.  Maybe someone beats
me to it;
if not, I hope to look into this in 3 weeks time.




[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )