unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Marshall, Simon" <Simon.Marshall@misys.com>
To: <emacs-pretest-bug@gnu.org>
Subject: [22.1.90]: Barf in left margin in *stack frames of emacs*
Date: Wed, 20 Feb 2008 11:09:01 -0000	[thread overview]
Message-ID: <6EE216E1AA959543A555C60FF34FB7670305BEEE@maileube01.misys.global.ad> (raw)

In *stack frames of emacs*, I can left-click in the right margin to
horizontally scroll the window.  Gud is good.  However, when I
left-click in the left margin to horizontally scroll back, I get an
error.

emacs -Q
M-x gdb RET RET	; for me, running gdb on emacs
In *gud-emacs*, put a breakpoint somewhere that will get hit and "r -Q"

When the breakpoint hits, select "Options | Enter Debugger on Error" and
"Gud | GDB-Frames | Stack" to popup the *stack frames of emacs* frame.
Left-click in the right margin to horizontally scroll the *stack frames
of emacs* window, then left-click in the left margin to scroll back.  I
get:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  file-name-nondirectory(nil)
  gud-format-command("break %f:%l" nil)
  gud-call("break %f:%l" nil)
  gud-break(nil)
  gdb-mouse-set-clear-breakpoint((mouse-1 (#<window 27 on *stack frames
of emacs*> left-fringe (2 . 32) 178127836 nil 250 (0 . 2) nil (2 . 6) (8
. 13))))
  call-interactively(gdb-mouse-set-clear-breakpoint)

It shouldn't signal an error, but it appears to be trying to do
something which is not what I would expect it to do.  I would not expect
to be setting breakpoints from the stack frame window in any case.


 "Misys" is the trade name for Misys plc (registered in England and Wales). Registration Number: 01360027. Registered office: Burleigh House, Chapel Oak, Salford Priors, Evesham WR11 8SP. For a list of Misys group operating companies please go to http://www.misys.com/html/about_us/group_operating_companies/. This email and any attachments have been scanned for known viruses using multiple scanners. 
 
We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys plc. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing. 




             reply	other threads:[~2008-02-20 11:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 11:09 Marshall, Simon [this message]
2008-02-20 11:51 ` [22.1.90]: Barf in left margin in *stack frames of emacs* Nick Roberts
2008-02-20 13:48   ` Marshall, Simon

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=6EE216E1AA959543A555C60FF34FB7670305BEEE@maileube01.misys.global.ad \
    --to=simon.marshall@misys.com \
    --cc=emacs-pretest-bug@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 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).