From: Kristian Otnes <kristian.otnes@tevero.no>
To: insight@sources.redhat.com
Cc: craig@digitalxfer.com, keiths@redhat.com
Subject: RE: Problem with source paths with new Cygwin release
Date: Fri, 05 Sep 2003 09:38:00 -0000 [thread overview]
Message-ID: <3F586F42@webmail.aktivepost.no> (raw)
To sum up a bit:
I rebuilt the original snapshot from August 8 2003 with updated
cygwin environment, and the problem with missing source paths
persisted.
I then fetched an Insight snapshot from September 5 and built
it with updated cygwin environment, and got the same error
as already reported by Craig:
gdbtk/generic/gdbtk-cmds.c:2891: warning: implicit declaration of function
`cygwin32_conv_to_full_win32_path'
make[1]: *** [gdbtk-cmds.o] Error 1
OK, so there has been something changed with conversion to full paths,
it looks like some API change somewhere in Cygwin if you ask me....
I don't have any solution for this right now except going back
to older version of at least the following modules:
cygutils: 1.2.1-2 -> 1.1.4-2
cygwin: 1.5.3-1 -> 1.3.22-1
Then Insight works with respect to source paths, but the bash
shell doesn't even start. If I go back on bash:
bash: 2.05b-13 -> 2.05b-9
I can start the bash shell, but I get lots of errors. Probably
in a quite useless state...
And that is how far I am right now...
Kristian
------
Today after updating the Cygwin environment, Insight started
having problems with source paths when doing high level debugging.
Most source files are shown only in assembly code, and when
using the Insight function browser, the source paths seem to have
been stripped away from almost all source files. Thus, only
assembly code is shown.
The new Cygwin package was 1.5.3-1. I used the Cygwin setup tool
and went back to 1.3.22-1, and everything worked fine again.
I have been working with Insight in Windows environment
using Cygwin. I built Insight based on a snapshot from August
8 2003 probably using Cygwin 1.3.22-1 release. It was built
for PowerPC/ELF architecture.
Anyone happen to know the reason?
Is it likely that rebuilding Insight after an upgrade would also
solve the problem?
Best regards
Kristian Otnes
next reply other threads:[~2003-09-05 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 9:38 Kristian Otnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 20:45 Kristian Otnes
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
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=3F586F42@webmail.aktivepost.no \
--to=kristian.otnes@tevero.no \
--cc=craig@digitalxfer.com \
--cc=insight@sources.redhat.com \
--cc=keiths@redhat.com \
/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).