From: Andreas Schwab <schwab@suse.de>
Cc: Nick Roberts <nick@nick.uklinux.net>, emacs-devel@gnu.org
Subject: Re: new gdb/gdba code has bug with absolute source filenames
Date: Thu, 08 Jan 2004 11:27:38 +0100 [thread overview]
Message-ID: <jey8sig2g5.fsf@sykes.suse.de> (raw)
In-Reply-To: <84vfnnb73l.fsf@cenderis.demon.co.uk> (Bruce Stephens's message of "Thu, 08 Jan 2004 00:46:06 +0000")
Bruce Stephens <Bruce.Stephens@isode.com> writes:
> Actually, it did seem to fix the problem for the test example. But
> didn't seem to for a real program with a much longer file name.
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.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-01-08 10:27 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 [this message]
2004-01-08 11:04 ` Bruce Stephens
2004-01-08 10:21 ` Andreas Schwab
2004-01-08 12:28 ` Nick Roberts
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=jey8sig2g5.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@gnu.org \
--cc=nick@nick.uklinux.net \
/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).