Fw: [avr-gcc-list] AVR-Insight and library debug

[Patrizio Zelotti]

> On Wed 17 Nov 2004 Theodore A. Roth wrote :
> On Tue, 16 Nov 2004 address@hidden wrote:
>
> > My experience with unix debuggers has been that the debugger needs the
> > source code files in the same directory as the object (e.g., .o) files
> > and the final executable.  So try copying all of the .c files for your
> > library back into the directory where your development applications
> > live.  It's ugly but it should work.  Alternatively, use symbolic
> > links instead of copying (ln -s instead of cp if you're using the unix
> > command line; if you're on Windows I have no clue).
>
> Although copying files may get the job done, I think it masks the
> problem and there are better ways to do it.
>
> Here's one way:
>
>   http://sources.redhat.com/gdb/current/onlinedocs/gdb_8.html#SEC53
>
> >
> >    From: "Patrizio Zelotti" <address@hidden>
> >    To: "avr-gcc-list" <address@hidden>
> >    Date: Tue, 16 Nov 2004 22:05:35 +0100
> >    Subject: [avr-gcc-list] AVR-Insight and library debug
> >
> >    Hi to all,
> >
> >    I developed 2 different applications on the same board (Atmega 128)
> >    with WinAVR20040404 using C language.  After the first working
> >    version, I decided to move the common part of the source code to a
> >    library; so I moved the source code to a different directory and
> >    built the library with avr-ar command.  Then I modified the source
> >    code to use the library.  The new version of the 2 projects compile
> >    and work correctly, but I have a problem when I debug with avarice
> >    and AVR-Insight : I can not debug and see the source code of the
> >    library, I can access only the library at assembly level.
> >
> >    I read the ar manual, but I was not able to find a solution.
> >
> >    The library and the project code are both compiled with -g option.
> >
> >    How is possible to see and debug the source code of the library ?
> >
> >    Thanks to all
> >
> >    Patrizio Zelotti
> >    _______________________________________________
> >    avr-gcc-list mailing list
> >    address@hidden
> >    http://www.avr1.org/mailman/listinfo/avr-gcc-list
> >
> > _______________________________________________
> > avr-gcc-list mailing list
> > address@hidden
> > http://www.avr1.org/mailman/listinfo/avr-gcc-list
> >
> >
>
> ---
> Ted Roth
> PGP Key ID: 0x18F846E9
> Jabber ID: address@hidden

Thank you for your reply.

Reading the documentation, I found one solutions : use of -d option from
command line.

Until now, I executed Avr-Insight clicking the desktop icon and then loading
the target file from menu.

Executing Avr-Insight from command line, specifying the option -d with the
library source code path and the target file name, I can debug the library
code at source level.

Patrizio Zelotti