Steve Underwood wrote:
Andreas Schwarz wrote:
Steve Underwood wrote:
Andreas Schwarz wrote:
Friday, November 22, 2002, 3:15:25 PM, you wrote:
Unfortunately I couldn't see the c-source files in Insight. The
only way to
see the C-source is to use the MIXED mode of the source window.
So I'm only
able to debug on assembly instruction level. Is there a way to
get debugging
on C-source level to work? Am I missing something? I also tried
to replace
the -g option with -ggdb. But no changes.
Its a bug when Insight is built on Windows for the MSP430. It
works fine on Linux, but does odd things on Windows. Insight built
without MSp430 support doesn't have this problem. I only realised
this problem existed today - sheer coincidence you posted this!
Now I need to fix it!
I don't have that problem with Insight, but there are a few other
small problems (like unreproducable crashes). It doesn't (yet?)
run very smooth on windows.
Would it help to port the msp430-patch to a more recent version of
GDB?
5.1.1 is quite old, maybe there have been a few improvements.
Are you sure, Andreas? When I run the Insight package from your site
on either XP or Me I get this problem.
Yes, I'm sure. As soon as I open my elf-file, the C source is
displayed. Are you sure the path of your file doesn't contain any
spaces? If you move it to c:\ it should work. Took me a few hours to
find out...
Well, based on what you said I tried again. If my binary is in c:\
then things work. If it is in *any* sub-directory it fails. It doesn't
matter if the subdirectory contains spaces or not. I tried it in
c:\msp430, for example, and insight does not behave correctly. Putting
the binary in the root directory is a nuisance, but at least it gets
things working until a proper fix is found.
I have looked into this issue, and it seems to be a contention between
the way Cygwin works and the way MinGW works. A MinGW built binary
contains file names like "c:\a\b\c\d.c", while a Cygwin binary contains
file names like "/cygdrive/c/a/b/c/d.c". Andreas' packages have most of
the tools built with MinGW, but Insight is built with Cygwin. That's
because we don't seem to have a usable set of patches to make Insight
build cleanly with MinGW. So..... when you build with the MinGW built
gcc, and try to debug with the Cygwin built Insight you get trouble.
Insight doesn't handle the file names in the binary properly. It partly
works, so a mixed source/assembly listing comes out OK. It just doesn't
work 100%.
Now.... it the best solution to fix Insight so it consistently handles
the MinGW style filenames correctly at all times, or use Cygwin to build
everything? Oh, these difficult decisions. :-)
Regards,
Steve
