From: Keith Seitz <keiths@redhat.com>
To: Kristian Otnes <kristian.otnes@tevero.no>
Cc: "'insight'" <insight@sources.redhat.com>
Subject: RE: Problem with source paths with new Cygwin release
Date: Thu, 04 Sep 2003 22:02:00 -0000 [thread overview]
Message-ID: <1062713103.1585.33.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <002101c3732f$6773df10$770a2f0a@zinfandel>
On Thu, 2003-09-04 at 14:56, Kristian Otnes wrote:
> It must be a GDB/Cygwin related problem as you suggest. I am using
> a cross target compiler for PowerPC/ELF.
I'm betting that's its more a generic gdb problem. I don't think cygwin
is really the issue: gdb has "worked" for a long time on cygwin.
> Maybe related to somehow Cygwin handles paths? I see the paths in the
> ELF file. Might be an API change somewhere?!
Doesn't seem likely that this should suddenly fail. I'm putting my money
on the symbol readers.
> Since Insight includes GDB when compiling, I am not sure how closely
> the Insight snapshots follow GDB updates. And I don't know how closely
> GDB follows Cygwin or vice versa. In other words, it can be a number of
> causes.
Insight snapshots are taken at the same time as gdb. In fact, I don't
even do anything related to releases -- the (very) kind gdb folk do it
for me. (Thanks, Andrew! :-)
Nonetheless, you're right: the best approach is to build something new.
Since 6.0 is due out "any day now" (so that means anytime in the next
month or two or three), I would encourage you to try this on 6.0. If
problems exist with 6.0, gdb developers will certainly want to know
about it.
Good luck,
Keith
next prev parent reply other threads:[~2003-09-04 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 21:12 Kristian Otnes
2003-09-04 21:29 ` Keith Seitz
2003-09-04 21:56 ` Kristian Otnes
2003-09-04 22:02 ` Keith Seitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 20:45 Kristian Otnes
2003-09-05 9:38 Kristian Otnes
2003-09-04 20:47 Kristian Otnes
2003-09-04 20:52 ` Keith Seitz
2003-09-04 19:57 Kristian Otnes
2003-09-04 20:11 ` Keith Seitz
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=1062713103.1585.33.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=kristian.otnes@tevero.no \
/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.
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).