From: David Palma <dbpalma9@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36521@debbugs.gnu.org
Subject: bug#36521: 26.2; CEDET/Semantic - Semantic constantly entering debugger with scheme
Date: Mon, 8 Jul 2019 22:50:15 +0100 [thread overview]
Message-ID: <1a871d73-20d5-4020-ef60-7ba19bd2fe01@gmail.com> (raw)
In-Reply-To: <87lfx82ssb.fsf@mouse.gnus.org>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
I do, I have attached a scheme source example file.
1. Start emacs with "emacs -Q".
2. Enable semantic-mode with M-x semantic-mode
3. Open bugtest.scm
And emacs should enter the debugger when semantic-idle-scheduler starts
working.
Thanks,
David
On 7/8/19 9:08 PM, Lars Ingebrigtsen wrote:
> David Palma <dbpalma9@gmail.com> writes:
>
>> Semantic enters the debugger whenever it's parsing invalid scheme code with
>> matching parentheses. The error code is "A Rule must return a single
>> tag-line list!"
>>
>> To trigger this simply write
>> (define )
>>
>> with electric matching pair mode active, the ending parenthesis is
>> automatically put and semantic constantly tries to enter the debugger,
>> making it unusable.
> Do you have a recipe for how to reproduce this bug, starting with
> "emacs -Q"?
>
[-- Attachment #2: bugtest.scm --]
[-- Type: text/x-scheme, Size: 126 bytes --]
(define (accumulate op init seq)
(if (null? seq)
init
(op (car seq) (accumulate op init (cdr seq)))))
(define)
next prev parent reply other threads:[~2019-07-08 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 11:45 bug#36521: 26.2; CEDET/Semantic - Semantic constantly entering debugger with scheme David Palma
2019-07-08 20:08 ` Lars Ingebrigtsen
2019-07-08 21:50 ` David Palma [this message]
2019-07-08 22:03 ` Lars Ingebrigtsen
2019-07-13 20:24 ` David Palma
2019-07-14 11:51 ` Lars Ingebrigtsen
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=1a871d73-20d5-4020-ef60-7ba19bd2fe01@gmail.com \
--to=dbpalma9@gmail.com \
--cc=36521@debbugs.gnu.org \
--cc=larsi@gnus.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.