From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.bugs Subject: bug#23424: 25.0.93; error in process sentinel with Melpa added to package-archives Date: Mon, 02 May 2016 22:05:50 +0000 Message-ID: References: <8337q0mpe7.fsf@gnu.org> <83twigl7mn.fsf@gnu.org> <83lh3skybm.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c0441f4a796060531e332e5 X-Trace: ger.gmane.org 1462226861 10947 80.91.229.3 (2 May 2016 22:07:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 2 May 2016 22:07:41 +0000 (UTC) Cc: 23424@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue May 03 00:07:32 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1axM03-0006tx-LR for geb-bug-gnu-emacs@m.gmane.org; Tue, 03 May 2016 00:07:31 +0200 Original-Received: from localhost ([::1]:38891 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axLzz-0001qP-Rp for geb-bug-gnu-emacs@m.gmane.org; Mon, 02 May 2016 18:07:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48710) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axLzq-0001cr-AS for bug-gnu-emacs@gnu.org; Mon, 02 May 2016 18:07:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1axLze-00051t-5j for bug-gnu-emacs@gnu.org; Mon, 02 May 2016 18:07:12 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:50210) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axLzc-00051F-Vr for bug-gnu-emacs@gnu.org; Mon, 02 May 2016 18:07:06 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1axLzZ-0001Qq-Kl for bug-gnu-emacs@gnu.org; Mon, 02 May 2016 18:07:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Kaushal Modi Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 02 May 2016 22:07:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 23424 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 23424-submit@debbugs.gnu.org id=B23424.14622267675439 (code B ref 23424); Mon, 02 May 2016 22:07:01 +0000 Original-Received: (at 23424) by debbugs.gnu.org; 2 May 2016 22:06:07 +0000 Original-Received: from localhost ([127.0.0.1]:34314 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1axLyh-0001Pf-9O for submit@debbugs.gnu.org; Mon, 02 May 2016 18:06:07 -0400 Original-Received: from mail-oi0-f65.google.com ([209.85.218.65]:35958) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1axLyg-0001P2-AK for 23424@debbugs.gnu.org; Mon, 02 May 2016 18:06:06 -0400 Original-Received: by mail-oi0-f65.google.com with SMTP id i2so189607oib.3 for <23424@debbugs.gnu.org>; Mon, 02 May 2016 15:06:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GHyhNkdC2ohHxj7C+pAjdYcVKtEu0LAekH/cyl3jLDQ=; b=BZYTGwmNXsOUz/xPm9dBbsHC6Fih3+ugtJGSBguZwnaEqUfsDJ8A9p6kFB4tTXsAnI lvJ9086BWTbZLj3vrZDBC6Z02UdZTWXwv+UmuQKf0vkcJYuJ5EybVvhJekAHUHf7IAHf LDqrvOvf0d2XICWXrk/7aijTPWa1K46uVknfFNO7KB8Z29vtmKo2/faRMAjc+mbQ0W4z nj4H4kd3nn1P1DvPJDidjt7TAa//4E5hNDdyRvF5UaG/JAGQshZZUT429MsQ0dkqjAHY hN3zJIu3YqaY7DB4dQBkrAFQ4NKV4Ni9PMvfIsOU9OqZSp38/NKNwOFfhrPSBrMbxfzw 6Dig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GHyhNkdC2ohHxj7C+pAjdYcVKtEu0LAekH/cyl3jLDQ=; b=Sky9fnqc0ZQPftHg3ORb20HGrqWiBxAJ147zWgS80Ss7R0LnpS9jHvfsGMePTSGsrE 1wIJL9r57I26R9nXGc8f5ZghX5n3KeTg5chQwMY9B4aKBZEIw7QCezEPH8NB/2V51I41 uJnXC+pHKwHfdfCjfRWtd33NblYUoOueBAk//uAL0cPYWcW42S35YK2uPwrytX/jSvcA Jx/4WMXNKsaGOMdLRXevi6cTdUSEfpfgcvx9/mzJpntos/ms9pmD/9eu4xb/YM5NOiiT WZIHPGh3vKaMbVMzI4Kxc7TH79nK/sUwtH451hzTkyIGUKQlNgKV/gXxahGtw6aJPONS UiLw== X-Gm-Message-State: AOPr4FXxFFjErFhbhgBrq990zMop2YJNa4BShY2gzPPL1qbRflS6RYU/NnpHD5BCK8hhLWcckCWgE3pqr7ASiQ== X-Received: by 10.157.0.68 with SMTP id 62mr5633932ota.189.1462226760730; Mon, 02 May 2016 15:06:00 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:117620 Archived-At: --94eb2c0441f4a796060531e332e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have a followup gdb 101 question: I thought I would improve the debug capability by adding the flags "--enable-checking=3D'yes,glyphs' --enable-check-lisp-object-type" to ./configure as per etc/DEBUG. I did not have those 2 flags earlier. But after rebuilding using the suggested options, the conditional breakpoints do not work. I also noticed that earlier "p error_symbol" gave something like, $1 =3D 41328 Now it gives something like, $1 =3D { i =3D 41328 } Also, when earlier I saw: Breakpoint 3, Fsignal (error_symbol=3D19056, data=3D16197139) at eval.c= :1471 , now I see instead: Breakpoint 3, Fsignal (error_symbol=3D..., data=3D...) at eval.c:1471 (those numbers for error_symbol and data are literally replaced with "...") =3D=3D=3D=3D=3D (emacs:22439): GLib-GIO-CRITICAL **: g_settings_schema_source_lookup: assertion 'source !=3D NULL' failed Breakpoint 3, Fsignal (error_symbol=3D..., data=3D...) at eval.c:1471 1471 =3D (NILP (error_symbol) ? Fcar (data) : error_symbol); (gdb) p error_symbol $1 =3D { i =3D 41328 } (gdb) xsymbol $2 =3D (struct Lisp_Symbol *) 0xdc3ee0 "scan-error" (gdb) condition 3 error_symbol!=3D41328 (gdb) c Continuing. Error in testing breakpoint condition: Structure has no component named operator!=3D. Error in testing breakpoint condition: Structure has no component named operator!=3D. Breakpoint 3, Fsignal (error_symbol=3D..., data=3D...) at eval.c:1471 1471 =3D (NILP (error_symbol) ? Fcar (data) : error_symbol); Here's my new ./configure command: ./configure options: --with-modules --prefix=3D/home/kmodi/usr_local/apps/6/emacs/emacs-25 --enable-checking=3Dyes,glyphs --enable-check-lisp-object-type 'CPPFLAGS=3D-fgnu89-inline -I/home/kmodi/usr_local/6/include -I/usr/include/freetype2 -I/usr/include' 'CFLAGS=3D-ggdb3 -O0' 'CXXFLAGS=3D-ggdb3 -O0' 'LDFLAGS=3D-L/home/kmodi/usr_local/6/lib -L/home/kmodi/usr_local/6/lib64 -ggdb3' PKG_CONFIG_PATH=3D/home/kmodi/usr_local/6/lib/pkgconfig:/home/kmodi/usr_loc= al/6/lib64/pkgconfig:/cad/adi/apps/gnu/linux/x86_64/6/lib/pkgconfig:/cad/ad= i/apps/gnu/linux/x86_64/6/lib64/pkgconfig:/usr/lib/pkgconfig:/usr/lib64/pkg= config:/usr/share/pkgconfig:/lib/pkgconfig:/lib64/pkgconfig For now, I will rebuild emacs without "--enable-checking=3D'yes,glyphs' --enable-check-lisp-object-type". But it would be good to know why those flags affected gdb (when etc/DEBUG says that those should not), and also why didn't conditional breakpoints work in this case. (I hope to get the old conditional-breakpoint-working-self back once I finish rebuilding without those flags.) --=20 --=20 Kaushal Modi --94eb2c0441f4a796060531e332e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have a followup gdb 101 question:

I t= hought I would improve the debug capability by adding the flags "--ena= ble-checking=3D'yes,glyphs' --enable-check-lisp-object-type" t= o ./configure as per etc/DEBUG. I did not have those 2 flags earlier. But a= fter rebuilding using the suggested options, the conditional breakpoints do= not work. I also noticed that earlier "p error_symbol" gave some= thing like,

$1 =3D 41328

= Now it gives something like,

$1 =3D {
=C2=A0 i =3D 41328
}

Also, when= earlier I saw:

=
=C2=A0 =C2=A0 Break= point 3, Fsignal (error_symbol=3D19056, data=3D16197139) at eval.c:1471

, now I= see instead:

=C2=A0 =C2=A0 Breakpoint 3, Fsignal = (error_symbol=3D..., data=3D...) at eval.c:1471

(those numbers for error_symbol and data are literally replaced with &quo= t;...")

=3D= =3D=3D=3D=3D

(emacs:22439): GLib-GIO-CRITICAL *= *: g_settings_schema_source_lookup: = assertion 'source !=3D NULL' failed

<= /div>
Breakpoint 3, Fsignal (error_symbol=3D..., data=3D...) at eval.c:= 1471
1471 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =3D (NILP (error_symbol) ? Fcar (data) : error_symbol);
(gdb) p e= rror_symbol
$1 =3D {
= =C2=A0 i =3D 41328
}
(gdb) xsymbol
$2 =3D (st= ruct Lisp_Symbol *) 0xdc3ee0 <lispsym+41328>
"scan-err= or"
(gdb) condition 3 error_symbol!=3D41328
(gdb) = c
Continuing.
Error in testing breakpoint condition:
Structure has no component named operator!=3D.
Error in t= esting breakpoint condition:
Structure has no component named ope= rator!=3D.

Breakpoint 3, Fsignal (error_symbol=3D.= .., data=3D...) at eval.c:1471
= 1471 =C2=A0 =C2=A0 =C2=A0 =C2=A0=3D (NILP (error_symbol) ? Fcar (data) : er= ror_symbol);

Here's my new ./configure command:

./c= onfigure options:
=C2=A0 --with-modules --prefix=3D/home/kmodi/us= r_local/apps/6/emacs/emacs-25 --enable-checking=3Dyes,glyphs --enable-check= -lisp-object-type 'CPPFLAGS=3D-fgnu89-inline -I/home/kmodi/usr_local/6/= include -I/usr/include/freetype2 -I/usr/include' 'CFLAGS=3D-ggdb3 -= O0' 'CXXFLAGS=3D-ggdb3 -O0' 'LDFLAGS=3D-L/home/kmodi/usr_lo= cal/6/lib -L/home/kmodi/usr_local/6/lib64 -ggdb3' PKG_CONFIG_PATH=3D/ho= me/kmodi/usr_local/6/lib/pkgconfig:/home/kmodi/usr_local/6/lib64/pkgconfig:= /cad/adi/apps/gnu/linux/x86_64/6/lib/pkgconfig:/cad/adi/apps/gnu/linux/x86_= 64/6/lib64/pkgconfig:/usr/lib/pkgconfig:/usr/lib64/pkgconfig:/usr/share/pkg= config:/lib/pkgconfig:/lib64/pkgconfig

For n= ow, I will rebuild emacs without=C2=A0"= ;--enable-checking=3D'yes,glyphs= ' --enable-check-lisp-object-typ= e". But it would be good to know why those flags affected gdb (when et= c/DEBUG says that those should not), and also why didn't conditional br= eakpoints work in this case. (I hope to get the old conditional-breakpoint-= working-self back once I finish rebuilding without those flags.)
--

--
Kaushal Modi

--94eb2c0441f4a796060531e332e5--