unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: schwab@suse.de, 23949@debbugs.gnu.org, monnier@iro.umontreal.ca,
	npostavs@users.sourceforge.net
Subject: bug#23949: 25.0.95; Regression in handling error caused by (string-match-p "." nil)
Date: Tue, 12 Jul 2016 22:12:10 +0300	[thread overview]
Message-ID: <83shveacxh.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY1zcyNU_FzL3yxeXmXSwWHER6Pp79NqxS2-L8Obmu4dSQ@mail.gmail.com> (message from Kaushal Modi on Tue, 12 Jul 2016 19:00:20 +0000)

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Tue, 12 Jul 2016 19:00:20 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>, 
> 	Andreas Schwab <schwab@suse.de>, 23949@debbugs.gnu.org
> 
> Thanks. Now it says "Lisp_String".
> 
> (gdb) xstring
> $18 = (struct Lisp_String *) 0x33a14e0
> "(nilory is relative, it is com"
> (gdb) p string
> $19 = 54138084
> (gdb) xtype
> Lisp_String
> (gdb)

If it says "Lisp_String", then using "xstring" is correct.





  reply	other threads:[~2016-07-12 19:12 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06  1:56 bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!) Clément Pit--Claudel
2016-08-06  2:15 ` npostavs
2016-08-06  3:03   ` Clément Pit--Claudel
2016-08-06  7:25   ` Eli Zaretskii
2016-08-06 10:28     ` Noam Postavsky
2016-08-06 10:34       ` Eli Zaretskii
2016-08-06 10:49         ` Noam Postavsky
2016-08-06 11:19           ` Eli Zaretskii
2016-08-06 12:25             ` npostavs
2016-08-07 14:12               ` Eli Zaretskii
2016-08-07 14:27                 ` npostavs
2016-07-11 20:12                   ` bug#23949: 25.0.95; Regression in handling error caused by (string-match-p "." nil) Kaushal Modi
2016-07-12 12:29                     ` Kaushal Modi
2016-07-12 13:14                       ` Eli Zaretskii
2016-07-12 13:33                         ` Kaushal Modi
2016-07-12 13:37                           ` Kaushal Modi
2016-07-12 14:03                             ` Eli Zaretskii
2016-07-12 14:01                           ` Eli Zaretskii
2016-07-12 18:35                             ` Kaushal Modi
2016-07-12 18:55                               ` Noam Postavsky
2016-07-12 19:00                                 ` Kaushal Modi
2016-07-12 19:12                                   ` Eli Zaretskii [this message]
2016-07-12 19:10                               ` Eli Zaretskii
2016-07-12 19:19                               ` Eli Zaretskii
2016-07-12 19:29                                 ` Kaushal Modi
2016-07-12 20:27                               ` Stefan Monnier
2016-07-13 13:10                                 ` Kaushal Modi
2016-07-13 13:59                                   ` Stefan Monnier
2016-07-13 15:06                                     ` Eli Zaretskii
2016-07-13 15:03                                   ` Eli Zaretskii
2016-07-13 14:24                                 ` Eli Zaretskii
2016-07-13 14:48                                   ` Stefan Monnier
2016-07-13 15:14                                     ` Eli Zaretskii
2016-07-13 16:00                                       ` Stefan Monnier
2016-07-13 16:18                                         ` Eli Zaretskii
2016-07-13 16:41                                           ` Stefan Monnier
2016-07-13 15:03                                   ` Andreas Schwab
2016-07-13 15:17                                     ` Eli Zaretskii
2016-07-12 14:15                           ` Andreas Schwab
     [not found]                     ` <handler.23949.C.147058007223290.notifdonectrl.2@debbugs.gnu.org>
2016-08-09 15:56                       ` bug#23949: acknowledged by developer (Re: bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)) Kaushal Modi
2016-08-07 15:43                   ` bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!) Clément Pit--Claudel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83shveacxh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23949@debbugs.gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=npostavs@users.sourceforge.net \
    --cc=schwab@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).