emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#18140: closed ([PATCH] macros.c: CHECK_VECTOR_OR_S


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#18140: closed ([PATCH] macros.c: CHECK_VECTOR_OR_STRING invokes wrong_type_argument for Qnil instead of return 0)
Date: Tue, 29 Jul 2014 08:11:02 +0000

Your message dated Tue, 29 Jul 2014 10:10:11 +0200
with message-id <address@hidden>
and subject line Re: bug#18140: [PATCH] macros.c: CHECK_VECTOR_OR_STRING 
invokes wrong_type_argument for Qnil instead of return 0
has caused the debbugs.gnu.org bug report #18140,
regarding [PATCH] macros.c: CHECK_VECTOR_OR_STRING invokes wrong_type_argument 
for Qnil instead of return 0
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
18140: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18140
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH] macros.c: CHECK_VECTOR_OR_STRING invokes wrong_type_argument for Qnil instead of return 0 Date: Tue, 29 Jul 2014 07:01:58 +0200 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
In function Fstart_kbd_macro (macros.c), Vlast_kbd_macro of current_kboard is 
Qnil for the first invocation.
If NILP (append) is false, current_kboard->kbd_macro_ptr has random value (in 
our case 0x5353535353535353),
which after CHECK_VECTOR_OR_STRING failure (invocation of wrong_type_argument) 
results in garbage collecting.
During gc, marking of objects is processed and mark_kboards (keyboard.c) is 
invoked. Following for loop is fired:

for (p = kb->kbd_macro_buffer; p < kb->kbd_macro_ptr; p++)
                  mark_object (*p);

Since kb->kbd_macro_ptr is set to 0x5353535353535353, mark_object (*p) is 
trying to mark object on address
out of memory space (or memory that cannot be accessed). Thus resulting in 
SIGSEGV signal.

Solution is to check for Qnil before calling CHECK_VECTOR_OR_STRING and set len 
to 0 if Qnil occurs.

https://bugzilla.redhat.com/show_bug.cgi?id=1104012

Signed-off-by: Jan Chaloupka <address@hidden>
---
 src/macros.c |   18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/src/macros.c b/src/macros.c
index 4730a8b..219eb39 100644
--- a/src/macros.c
+++ b/src/macros.c
@@ -85,7 +85,23 @@ macro before appending to it.  */)
       bool cvt;
/* Check the type of last-kbd-macro in case Lisp code changed it. */
-      len = CHECK_VECTOR_OR_STRING (KVAR (current_kboard, Vlast_kbd_macro));
+      /* If Vlast_kbd_macro is Qnil, skip the check and set len to 0.
+       * Flength returns 0 for Qnil, CHECK_VECTOR_OR_STRING has to do the same.
+       * Otherwise CHECK_VECTOR_OR_STRING fails and results in garbage 
collecting,
+       * which results in (keyboard.c, mark_kboards(void))
+       *
+       * for (p = kb->kbd_macro_buffer; p < kb->kbd_macro_ptr; p++)
+       *         mark_object (*p);
+       *
+       * Here, kb->kbd_macro_ptr is not initialized and can contain address
+       * 0x5353535353535353, which results in SIGSEGV trying to access the 
address.
+       *
+       * https://bugzilla.redhat.com/show_bug.cgi?id=1104012
+       */
+      if (!NILP (KVAR (current_kboard, Vlast_kbd_macro) ))
+        len = CHECK_VECTOR_OR_STRING (KVAR (current_kboard, Vlast_kbd_macro));
+      else
+        len = 0;
/* Copy last-kbd-macro into the buffer, in case the Lisp code
         has put another macro there.  */




--- End Message ---
--- Begin Message --- Subject: Re: bug#18140: [PATCH] macros.c: CHECK_VECTOR_OR_STRING invokes wrong_type_argument for Qnil instead of return 0 Date: Tue, 29 Jul 2014 10:10:11 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Fixed for emacs 24.4.  Thanks for the report.

Andreas.

-- 
Andreas Schwab, SUSE Labs, address@hidden
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]