GDB 5.0 for Tornado/VxWorks on PPC604e ?

[Alexander Povolotsky <APovolotsky at nexabit dot com>]

> Hello GDB experts,
> 
> What about GDB 5.0 for Tornado/VxWorks on PPC604e and other architectures
> ?
> Is WRS opposing to it or does someone from WRS is working on it ?
> 
> Also I would like to ask you the question on GDB v 4.12 (Actually WRS's
> incarnation called CrossWind).
> It has to do with "source directories" settings .
> >According to the documentation
> >(gdb) dir "/some/fully/qualified/source/path"
> >should set the source path to access the needed source file.
> >It does sets it, as indicated by
> >
> >(gdb) show dir 
> (it shows this directory prepended in front of $cdir and $cwd
> >
> >but, apparently, commmands
> >
> >(gdb) list filename.c:lineNumber
> >  or
> >(gdb) list filename:functionName
> >
> >still fail for most of such directories and source files in those ....
> >
> >changing directory to the one of interest prior to executing "list"
> commands as above 
> >
> >(gdb) cd "/some/fully/qualified/source/path"
> >
> >did not help either ...
> >
> >so using commands
> >
> >(gdb) info source
> >
> >and
> >
> >(gdb) info sources
> >
> >showed that the source visibility is ACTUALLY defined by the content
> "compilation directory" $cdir ONLY !
> >
> >We are using "Clearmake" in our multinested directories recursive "total"
> 
> >build process ....
> >The shell we are using is "bash" ....
> >
> >How could I change setting of "cdir"  - could I do it in .gdbinit ?
> >(and if yes, what would be the correct syntax) ?
> >Any way, what is the solution for this problem (we are using Tornado
> 1.0.1 
> >on Solaris 2.7 ) ?
> >
> >
> >Best Regards,
> >Alex Povolotsky
>