From: Bruce Stephens <Bruce.Stephens@isode.com>
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:04:45 +0000 [thread overview]
Message-ID: <84y8siaegi.fsf@cenderis.demon.co.uk> (raw)
In-Reply-To: <jey8sig2g5.fsf@sykes.suse.de> (Andreas Schwab's message of "Thu, 08 Jan 2004 11:27:38 +0100")
Andreas Schwab <schwab@suse.de> writes:
> 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 don't need to. The problem is right at the beginning. As Nick
pointed out, for the broken case, gdb doesn't report the compilation
directory, so the first test fails, and gdb-view-source is set to nil.
> I tried it with real long filenames and function names, and it
> didn't fail for me.
I no longer think that it's length. I think it's that absolute and
relative filenames end up different, for some reason. I guess this is
the kind of thing that may well vary depending on debugging format,
compiler, and platform.
[...]
next prev parent reply other threads:[~2004-01-08 11:04 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84y8siaegi.fsf@cenderis.demon.co.uk \
--to=bruce.stephens@isode.com \
--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 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.