Hello Steve
Thanks for you answer, I was starting to think nobody was going to
answer this :-)
I had already thought of the solution you propose, but the problem is
I use always the same view for compiling, and I do it every night. This
means the objects [.o files :-) ] are always overwritten in that view, so
they are lost or not reusable (sources couldn't not correspond to the
accessed .o file) to the rest of the views.
If finally it is true the Sun compilers place debug info in the .o files, I would
be searching for a way of telling those compilers to place ALL the
debug information in the libraries. I version the libraries, so I would
keep all the information for the particular version selected by each of my views.
Thanks,
Javier.
Steve Rehrauer wrote:
> Javier Perez <Javier.Perez@usa.alcatel.com> writes:
> > I am using the dbx debugger included in SunWorkShop Version 5.0.
> > I am also using ClearCase. My problem is, when I start a debugging
> > session using a view that is not the one I used for compiling, the
> > debugger complains about not having accessibility to the objects
> > of the compilation (of course, they are in a different view).
>
> If you have access to the view you used for compiling, try using the
> dbx pathmap command. E.g. (and I hope I get the argument order correct,
> from memory...), 'pathmap /vobs/app /view/my_builds_view/vobs/app'.
>
> > I don't know why the debugger needs the objects if it has the shared
> > libraries (it is supposed it should find everything it needs in them).
>
> I *think* the Sun compilers place debug info in the .o files, and
> don't aggregate it into the final libraries/executables? (Or at
> least, I think it used to work that way -- someone will correct me
> if I've got it wrong in any case.)
>
> (You _did_ mean .o files, not source files, when you said "objects"?)
> --Steve
> --
> Steve Rehrauer @ Rational Software, http://www.rational.com/
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:04:01 EDT