The VxWorks taskSpawn command has great flexibility, but on the down-side, it gives you plenty power to shoot yourself in the foot.
I looked up the error code and didn't quite find it.
http://www.vxdev.com/docs/vx55man/vx...noNumList.html has memlib errors that go up to 1114117, but no ...8. All of those are related to a bad pointer or access to memory you aren't supposed to access. I don't have vxworks dev tools at home. Try searching for the error code. I suspect you'll find it in the memlib header file and it will give a hint as to the issue.
Meanwhile, the easiest problems to have with spawning a task are to make the stack too small or to leave floating point registers out of the stack frame which will lead to a corruption once you accidentally use floats. Try adding a zero to the stack size and reviewing all of the other jillion parameters to spawn to see if any of them sound necessary.
Greg McKaskle