[ntp:questions] Unresolved Symbol

Aggie c.kevin.lam at gmail.com
Mon Aug 20 23:49:24 UTC 2007

On Aug 10, 12:15 pm, p... at hedeland.org (Per Hedeland) wrote:
> In article <T1186727... at ex.djwhome.demon.co.uk.invalid>
> da... at ed.djwhome.demon.co.uk.invalid (David Woolley) writes:
> >In article <1186703380.966947.229... at i38g2000prf.googlegroups.com>,
> >Aggie <c.kevin.... at gmail.com> wrote:
> >> Machine Check
> >Machine check should never be the result of software problems (except
> >kernel ones which leave the hardware in a diagnostic mode).  It means
> >you have a broken CPU, memory, or other core part of the hardware.
> Are you knowledgeable enough about VxWorks to know exactly what
> conditions it would report as "Machine Check"?

No, I don't know much things on VxWorks.

> You may well be right (in
> principle and/or in practice), but from my experience with VxWorks
> (several years old, muddled by less than perfect memory), that's the
> kind of message you would get whenever you did something that would
> result in "segmentation fault" or "bus error" on Unix - basically any
> kind of invalid memory access. Most commonly dereferencing a NULL
> pointer.

Yes, I think you are right on the dereferncing a NULL part. Is there a
NUL?? is it the same as NULL??
Here's the line that gave me error:
    if ((pOpts->pzCurOpt != NULL) && (*pOpts->pzCurOpt != NUL))


More information about the questions mailing list