From: Nick Roberts <nick@nick.uklinux.net>
Cc: Bruce Stephens <bruce.stephens@isode.com>, emacs-devel@gnu.org
Subject: Re: new gdb/gdba code has bug with absolute source filenames
Date: Thu, 8 Jan 2004 12:28:08 +0000 [thread overview]
Message-ID: <16381.19672.120644.757561@nick.uklinux.net> (raw)
In-Reply-To: <je3caqhha6.fsf@sykes.suse.de>
> > so I guess that running GDB command, "set width 0", on initialisation
> > will help.
>
> I don't think this is desireable, since it causes all output to not be
> wrapped, which is not nice when printing large values.
I agree. I will revert this change.
>From the e-mail to Bruce Stephens:
> Can you step through gdb-frame-handler with edebug and look at gdb's
> output in gdb-partial-output-buffer? I tried it with real long filenames
> and function names, and it didn't fail for me.
A good way to look at this output is to select gdb-partial-output-buffer and
type undo. That way you can cycle back through its history. In the past I have
found that edebug plays havoc with real time aspects of the process filter.
Nick http://www.nick.uklinux.net
next prev parent reply other threads:[~2004-01-08 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 22:43 new gdb/gdba code has bug with absolute source filenames Nick Roberts
2004-01-08 0:46 ` Bruce Stephens
2004-01-08 10:21 ` Nick Roberts
2004-01-08 11:11 ` Bruce Stephens
2004-01-08 10:27 ` Andreas Schwab
2004-01-08 11:04 ` Bruce Stephens
2004-01-08 10:21 ` Andreas Schwab
2004-01-08 12:28 ` Nick Roberts [this message]
2004-01-08 13:53 ` Bruce Stephens
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 22:04 Nick Roberts
2004-01-06 17:05 Bruce Stephens
2004-01-06 20:40 ` Andreas Schwab
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=16381.19672.120644.757561@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=bruce.stephens@isode.com \
--cc=emacs-devel@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).