Re: [avr-gcc-list] Cygwin paths causes problems for AVR Studio

[Andrew M. Cullen]

Thanks Torleif,

Switching to the latest version of AVR Studio, and changing the debug option 
to DWARF-2 has allows me to at least start debugging. The path issue is 
still a problem as when I load the ELF into AVR studio, it prompts me for 
the location of main.c as the object files still have the cygwin paths 
embedded in them. For some reason AVR studio can still figure out where the 
source files are as if you look at the disassembly listing it shows the 
correct Windows paths for the source files but put "(Alternate Location)" at 
the end. The only thing that isn't working is in the "Workspace" window, you 
can't click on a source file and have it pop up as it doesn't seem to know 
where to find it.

I tried making relative paths in my Makefile as per your suggestion but 
avr-gcc still seems to embed the full path names in the debug.

Andrew


----- Original Message ----- 
From: "Torleif Sandnes" <address@hidden>
To: "Andrew M. Cullen" <address@hidden>; <address@hidden>
Sent: Monday, July 04, 2005 3:02 AM
Subject: Re: [avr-gcc-list] Cygwin paths causes problems for AVR Studio


> > I've had to switch from WinAVR to Cygwin built tools as I need to compile 
> > for the ATMega325 which isn't support under the current windows toolset. 
> > My problem is that I would like to continue using AVR Studio for 
> > debugging but cygwin inserts its path names (/cygdrive/c/..... ) into the 
> > ELF and subsequently my extended COFF has these paths which AVR Studio 
> > can't decipher.
>
> One more thing:
> It may seem like you are converting from elf to coff before you feed the 
> object files to AVR Studio.
> You should not use the elf2coff conversion tool anymore. AVR Studio now, 
> (4.11) has a parser to handle elf/dwarf files directly. Remember to use 
> the -gdwarf-2 flag.
>
> Try to use the elf/dwarf files directly and let me know if you still have 
> problems then.
>
> Torleif