all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23424@debbugs.gnu.org
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	[thread overview]
Message-ID: <CAFyQvY3WfB6=ejZ3GVxa+6tpfs0HE53gZtAK46Ot2t8yw2RP-g@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY3CKxbWHe6jZEiGT9O48ry7dqvMapwEEyW_aA5G=2isBw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2632 bytes --]

I have a followup gdb 101 question:

I thought I would improve the debug capability by adding the flags
"--enable-checking='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 = 41328

Now it gives something like,

$1 = {
  i = 41328
}

Also, when earlier I saw:

    Breakpoint 3, Fsignal (error_symbol=19056, data=16197139) at eval.c:1471

, now I see instead:

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

(those numbers for error_symbol and data are literally replaced with "...")

=====

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

Breakpoint 3, Fsignal (error_symbol=..., data=...) at eval.c:1471
1471        = (NILP (error_symbol) ? Fcar (data) : error_symbol);
(gdb) p error_symbol
$1 = {
  i = 41328
}
(gdb) xsymbol
$2 = (struct Lisp_Symbol *) 0xdc3ee0 <lispsym+41328>
"scan-error"
(gdb) condition 3 error_symbol!=41328
(gdb) c
Continuing.
Error in testing breakpoint condition:
Structure has no component named operator!=.
Error in testing breakpoint condition:
Structure has no component named operator!=.

Breakpoint 3, Fsignal (error_symbol=..., data=...) at eval.c:1471
1471        = (NILP (error_symbol) ? Fcar (data) : error_symbol);

Here's my new ./configure command:

./configure options:
  --with-modules --prefix=/home/kmodi/usr_local/apps/6/emacs/emacs-25
--enable-checking=yes,glyphs --enable-check-lisp-object-type
'CPPFLAGS=-fgnu89-inline -I/home/kmodi/usr_local/6/include
-I/usr/include/freetype2 -I/usr/include' 'CFLAGS=-ggdb3 -O0'
'CXXFLAGS=-ggdb3 -O0' 'LDFLAGS=-L/home/kmodi/usr_local/6/lib
-L/home/kmodi/usr_local/6/lib64 -ggdb3'
PKG_CONFIG_PATH=/home/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/pkgconfig:/lib/pkgconfig:/lib64/pkgconfig

For now, I will rebuild emacs without "--enable-checking='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.)
-- 

-- 
Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 3893 bytes --]

  reply	other threads:[~2016-05-02 22:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 15:19 bug#23424: 25.0.93; error in process sentinel with Melpa added to package-archives Kaushal Modi
2016-05-02 15:49 ` Eli Zaretskii
2016-05-02 15:54   ` Robert Pluim
2016-05-02 16:23     ` Eli Zaretskii
2016-05-02 16:22   ` Kaushal Modi
2016-05-02 16:41     ` Kaushal Modi
2016-05-02 16:54       ` Kaushal Modi
2016-05-02 16:58       ` Eli Zaretskii
2016-05-02 17:22         ` Kaushal Modi
2016-05-02 20:19           ` Eli Zaretskii
2016-05-02 20:51             ` Kaushal Modi
2016-05-02 22:05               ` Kaushal Modi [this message]
2016-05-02 23:18                 ` Kaushal Modi
2016-05-03 14:59                   ` Eli Zaretskii
2016-05-03 15:12                 ` Eli Zaretskii

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

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

  git send-email \
    --in-reply-to='CAFyQvY3WfB6=ejZ3GVxa+6tpfs0HE53gZtAK46Ot2t8yw2RP-g@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=23424@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.