Hi Jaymin, While I'd like to help you with each step, I'm usually not going to do that (unless you become a Wind River customer. :) ) To save us and anyone who might be reading this thread some time,

Via google: https://jvns.ca/blog/2018/04/28/debugging-a-segfault-on-linux/ ../Randy

Likely the server was just down for a while. Both the web site: http://git.omapzoom.org/?p=kernel/omap.git;a=summary and: $ git clone -b p-ti-lsk-linux-4.4.y-next git://git.omapzoom.org/kernel/omap.gi

Hi Jochen, No and I've never seen this particular extreme symptom. There is a known, generally rare bug: Bug 12434 - pseudo: Incorrect UID/GID in packaged files https://bugzilla.yoctoproject.org/show_

Jethro isn't officially supported by the Yocto Project. The support cycle is ~ 1 year. https://wiki.yoctoproject.org/wiki/Releases Can you reproduce the issue on master or a newer supported branch? If

What sort of occasional kernel message and do they eventually stop? No but here are some generic debugging tips. In no particular order, have you tried: 1) setting kernel boot options such as: init=/b

Hi, I presume that you mean QUIC (Quick UDP Internet Connections) as in: https://github.com/conght/quic I also couldn't find an existing recipe using: https://layers.openembedded.org/layerindex/branch

Hi Anibal, Excellent! I will send a recipe update. Thanks,

PSDKLA-3.02 seems to be a TI distro that is apparently based on oe-core: http://processors.wiki.ti.com/index.php/Category:Processor_SDK_Linux_Automotive You should contact who ever your vendor or supp

Drop unused function parameters in wait_child(). The remaining warning in the top dir code is: utils.c:25:9: warning: macro name is a reserved identifier [-Wreserved-id-macro] #define _GNU_SOURCE and

Make tests build using: clang -Weverything There are a few warnings that remain that are not variable casting or macro fixes. Signed-off-by: Randy MacLeod <Randy.MacLeod@...> --- tests/main.

Fix basic errors found when building with the clang compiler with the option -Weverything. There are a few warnings that remain that are not variable casting, macro fixes, or similarily simple changes

When running the run-execscript bash ptest as a user rather than root, a warning: bash: cannot set terminal process group (16036): Inappropriate ioctl for device bash: no job control in this shell con

Yes, I had noticed that and fixed it as well. I'll send my latest patch series once you have merged Richard's changes into master. Hopefully that will be today... :) I decided to compile with: clang -

Yes, that's likely my fault. I've taken the defect. ../Randy 'belt and suspenders' MacLeod

Hmmm, I was making the code compile cleanly under clang using -Weverything when I noticed: 1. the 'make check' tests. They still work fine. 2. The './ptest-runner -d tests/data -t 1' tests which now g

When running the run-execscript bash ptest as a user rather than root, a warning: bash: cannot set terminal process group (16036): Inappropriate ioctl for device bash: no job control in this shell con

From: Richard Purdie <richard.purdie@...> There was a race in the code where the pipes may not be read after the process has exited and data may be left behind in them. This change to

From: Richard Purdie <richard.purdie@...> Rather than just killing the process we've swawned, set the process group for spawned children and then kill the group of processes. Signed-of

From: Richard Purdie <richard.purdie@...> There is no guarantee that the data written with fwrite will be flushed to the buffer. If stdout and stderr are the same thing, this could lea