On specifying the wrong parameters in vpp startup.conf, VPP crashes without showing any error message to help vpp user determine the cause. For instance, if we need to bind worker to the nic interfaces and assign lcore id instead of worker thread id in conf file (as shown below) vpp crashes.

unix {
interactive
log /tmp/vpp.log
cli-listen localhost:5002
full-coredump
}
dpdk {
socket-mem 2048,2048
dev 0000:02:00.0

{workers 2,5 num-rx-queues 2}

dev 0000:02:00.1

{workers 4,3 num-rx-queues 2}

}
cpu {
main-core 0
corelist-workers 2-3, 4-5
}

error log:

EAL: PCI device 0000:02:00.1 on NUMA socket 0
EAL: probe driver: 8086:10fb rte_ixgbe_pmd
EAL: PCI memory mapped at 0x7f4b40084000
EAL: PCI memory mapped at 0x7f4b40104000
PMD: eth_ixgbe_dev_init(): >>
PMD: ixgbe_disable_intr(): >>
PMD: ixgbe_pf_host_init(): >>
PMD: eth_ixgbe_dev_init(): MAC: 2, PHY: 18, SFP+: 6
PMD: eth_ixgbe_dev_init(): port 1 vendorID=0x8086 deviceID=0x10fb
DPDK physical memory layout:
Segment 0: phys:0x400000000, len:4294967296, virt:0x7f4a40000000, socket_id:0, hugepage_sz:1073741824, nchannel:0, nrank:0
Segment 1: phys:0xc00000000, len:2147483648, virt:0x7f4780000000, socket_id:1, hugepage_sz:1073741824, nchannel:0, nrank:0
dpdk_lib_init:272: DPDK drivers found 2 ports...
/bin/sh: line 1: 206539 Segmentation fault sudo /home/fido/vpp/build-root/install-vpp_debug-native/vpp/bin/vpp -c startup.conf
Makefile:195: recipe for target 'run' failed
make: *** [run] Error 139

In this particular case and overall, better error reporting is required can help vpp user to identify the cause.
Also, documentation needs to updated in sync with the latest code base.