Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Stephen Pape <srpape@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: VxWorks Target
Date: Wed, 19 Oct 2016 08:17:00 -0000	[thread overview]
Message-ID: <CAH=s-PM3+b_GDEs=J-qoLyWLSv46+es6tjU-LADiSFRV=53y_w@mail.gmail.com> (raw)
In-Reply-To: <CADdUxCx2shQYwwL0_NgAg9xVNVJU7sG+e6_WZKj2+Z_1yAYx0w@mail.gmail.com>

On Tue, Oct 18, 2016 at 10:09 PM, Stephen Pape <srpape@gmail.com> wrote:
> Hello all,
>
> Can anyone tell me the state of the VxWorks support in GDB? While
> compiling, I see --configure can take a "-vxworks" target, but I can't
> find much more information beyond that. Most of what I see is very
> old, and doesn't seem to apply. For example, "target vxworks <host>"
> does not work ("Undefined target command").
>
> Is there documentation on the VxWorks implementation, or how to use it?
>

VxWorks support was removed in 2004.

commit e84ecc995d6a5e4e9114d3cea61717b8a573afb6
Author: Andrew Cagney <cagney@redhat.com>
Date:   Sat Nov 13 23:10:02 2004 +0000

    2004-11-13  Andrew Cagney  <cagney@gnu.org>

        * configure.tgt: Delete i[34567]86-*-vxworks*, m68*-netx-*,
        m68*-*-vxworks*, mips*-*-vxworks*, powerpc-*-vxworks*, and
        sparc-*-vxworks*.
        * NEWS: Mention that vxworks was deleted.
.....

-- 
Yao (齐尧)


  reply	other threads:[~2016-10-19  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 21:09 Stephen Pape
2016-10-19  8:17 ` Yao Qi [this message]
2016-10-19 14:36   ` Stephen Pape
2016-10-19 15:45     ` Yao Qi
2016-10-20 18:09       ` Stephen Pape
2016-10-20 18:47         ` Yao Qi
2016-10-21 15:30         ` Joel Brobecker
2016-10-26 15:51           ` Stephen Pape

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH=s-PM3+b_GDEs=J-qoLyWLSv46+es6tjU-LADiSFRV=53y_w@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=srpape@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox