My apologies for the delay in responding, I have been swamped with work over this past 10 days and haven't had much time to peruse the forum. its not because I don't love you guys
@vt100 I followed your instruction to the letter. I can launch sds100.app under busybox, I seem to be able to enable crash core dumps with ulimit -c unlimited, but when I kill sds1000.app with ABRT signal, no core dump is generated, the app is just killed. ulimit -c shows unlimited so core dumps should be enabled. My firmware is .25R2. Any other way to trigger a core dump? Is it possible core dumps are disabled on this particular version of Busybox?
Core dump appears to be disabled on the "stock" version included with the scope. If you kill -ABRT the pid and you do not get a core dump, then
a. make sure you're in a directory which is writable (e.g. /tmp) when you launch the scope app and then kill the pid. Otherwise the core dump can't be written.
b. make sure you're running the /tmp version of busybox, common error is to just type busybox ash which would launch the version in bin from the search path
The same thing happened to me, but after I tried a few times I managed to get a core dump. Maybe you have to wait a bit longer for the dump to be generated?
The core file is somewhat large, but its never taken more than, say, 5-10 seconds in all my tests. Once you see the (core dump) message, the core file should be there.
Finally I was able to setup the proper linux toolchain for the arm cortex A7 and cross compile Busybox.
The new Busybox worked flawlessly and I was able to get a core dump and retrieve the licenses.
It's possible the pre-compiled version at the link posted (which is an auto-build updated regularly) might be incorrectly compiled with core dumps disabled at some point. I am not sure how often the busybox at the link provided is updated. for best results obviously compile your own
Home
Help
Search
Login
Register
