Re: VxWorks Target

Okay, thanks. That clears things up a little. I have another question,
if you (or anyone else) can help.

Is there any concept of a "bare" target? For example, just a "powerpc"
target that isn't OS specific. The targets I've seen seem like they're
OS specific ("-linux").

I was thinking of writing a stub that speaks the GDB serial protocol.
I can implement the "add breakpoint", "remove breakpoint", "read
memory", "write memory" type functionality myself, but I'm trying to
figure out how that would work with GDB. Sorry if this doesn't make
sense, I'm just beginning to learn about GDB internals.

Thanks again,

-Stephen

On Wed, Oct 19, 2016 at 11:45 AM, Yao Qi <[email protected]> wrote:
> On Wed, Oct 19, 2016 at 3:36 PM, Stephen Pape <[email protected]> wrote:
>> Wow, so it's ancient history. If that's the case, there is some
>> leftover VxWork code hanging around. I was even able to compile gdb
>> with "--target=powerpc-vxworks", and there are a few files with the
>> name still in the source:
>>
>> ./include/elf/vxworks.h
>> ./bfd/elf-vxworks.c
>> ./bfd/elf-vxworks.h
>>
>> The configure script has some VxWorks leftovers as well:
>>
>>   case "${target}" in
>>     *-*-vxworks*)
>>       # VxWorks uses the Dinkumware C++ library.
>>       noconfigdirs="$noconfigdirs target-libstdc++-v3"
>>       ;;
>>
>
> VxWorks support in GDB was removed, but its support in other
> components, like linker, are still there.  They are not leftover.
>
> However, configure should be adjusted so that gdb shouldn't
> be configured at all if target is *-*-vxworks*.
>
> --
> Yao (齐尧)