From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: a.soroa@ehu.eus, 34489@debbugs.gnu.org
Subject: bug#34489: 25.2; pdb fails if directory contains '++'
Date: Sun, 30 Jun 2019 19:33:46 +0300 [thread overview]
Message-ID: <835zonf2xh.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=BA7dm0f2TwM7qKP1=GMcksgvVbEGw9QT6oS2_-ek-5w@mail.gmail.com> (message from Stefan Kangas on Sun, 30 Jun 2019 18:13:19 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sun, 30 Jun 2019 18:13:19 +0200
> Cc: 34489@debbugs.gnu.org
>
> The expected behaviour is to see TWO buffers in separate windows,
> first "*gud-pp.py" with the following content:
>
> Current directory is /tmp/foo++/
> > /tmp/foo++/pp.py(1)<module>()
> -> print(10)
> (Pdb)
>
> And the second a buffer visiting "pp.py".
>
> The symptom is that you only see ONE buffer "*gud-pp.py*" with the
> following content:
>
> Current directory is /tmp/foo++/
>
> The bug (half) goes away as soon as I try to debug `gud-common-init'
> using M-x edebug-defun, but only when stepping through manually using
> "n" (and not when hitting "c"). Without this instrumentation, I get
> the bug as above. With it, I see the expected output in the
> "*gud-pp.py*" buffer (but *not* the expected "pp.py" buffer).
>
> I tried adding strategic calls to sit-for in gud-common-init and could
> get the same result as with M-x edebug-defun.
>
> Does anyone have any ideas what could cause this?
A stab in the dark: gud-pdb-marker-regexp?
next prev parent reply other threads:[~2019-06-30 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 8:32 bug#34489: 25.2; pdb fails if directory contains '++' a.soroa
2019-06-30 16:13 ` Stefan Kangas
2019-06-30 16:33 ` Eli Zaretskii [this message]
2019-06-30 17:24 ` Stefan Kangas
2019-07-02 16:35 ` Eli Zaretskii
2019-07-02 19:42 ` Stefan Kangas
2019-07-03 5:39 ` Eli Zaretskii
2019-07-05 15:51 ` Stefan Kangas
2019-07-06 9:10 ` 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=835zonf2xh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34489@debbugs.gnu.org \
--cc=a.soroa@ehu.eus \
--cc=stefan@marxist.se \
/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.