Erdas Imagine 2020 Currupt Sibling warning - image-processing

I am consistently getting warnings/errors about Corrupt Sibling or Corrupt Child when recoding data or just saving layers that heave been recoded. What does this warning mean? How can I resolve these issues?

Related

std::length error when using PCL Ground_based RGBD detection

I am facing an issue with Ground-based RGBD people detection (https://pcl.readthedocs.io/projects/tutorials/en/latest/ground_based_rgbd_people_detection.html). The error is inconsistent and hence has been pretty difficult to narrow down.
When I am running the detection, sometimes it throws a std::length error, and what() says vector_M_fill_insert.
Initially, I assumed it happened when people were detected (because it ran fine and the moment a person entered the frame, it stopped), and it was probably associated with the clustering, but in a few cases, it threw the error just after I launched the node.
I passed a processed point cloud to it and then passed the direct camera point cloud as well just to try to check if the issue was with the processed point cloud, but in both cases, it threw the error unpredictably.
I am confused as to how to go about debugging the error or what might be causing it. Any help is appreciated thank you!
You need to build your nodes with debug flags enabled and that can be achieved in some ways ...
Adding to your CMakelists.txt
set(CMAKE_BUILD_TYPE Debug)
Or
compiling with -DCMAKE_BUILD_TYPE=Debug.
Then you should attach the gdb debugger to whatever node you want. If you are using VS Code as IDE, there is already an extension for it with tutorials, otherwise, you can also add it to your launch file as described here

Xcode 9 Compiler Hangs On File With No Warnings Or Errors

Background:
Attempting to upgrade large 100k codebase from Swift 2.3 to Swift 4. Was making good progress, fixed ~1000 error. Then, after changing one of our DTO objects to use Any instead of AnyObject (because we had to), the compiler started hanging.
Problem:
When compiling the application will get to a certain file and just get stuck (even after 24 hours). It is not frozen just stuck compiling. I have tried temp removing the file but then it just gets stuck on another file and so on and so on.
Research & Attempts
I've read up on the compiler and how to turn on warnings and flags. I tried looking at -Xfrontend -debug-time-function-bodies and -Xfrontend Xfrontend -warn-long-expression-type-checking but nothing comes up. When I look at the build transcript for the file its stuck on there is no info in the expanded transcript.
Do you know what else I can check? I suspect it has something to do with its inability to infer type given how many Any filled dictionaries we have but without getting better information I have no clue where to go from here.
Do you know how I can get info as to why it's getting stuck on this file and no warnings given?
To followup, it took several days, but by first converting to Swift 3.2 and then Swift 4 (commenting out most code to solve later) I was able to get it to compile in Xcode 9.

MapBox iOS SDK 10.0.1 Error when touching a map pin

I'm getting the following error when I click on a map pin. This is occurring in the simulators and a real devices iOS 7 and iOS 7 64 bit.
I have a map with a series of pins in it. Since updating to 1.0.1 in an attempt to support 64 bit iPhones I get the following error:
: CGContextPathContainsPoint: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
I've seen questions about this but they seem to involve TextBoxes and this has no TextBoxes.
I do not get this error with the previous versions of the MapBox SDK.
So I have 2 questions.
First; What can I do to find the cause of this? Anybody encounter this?
Second; Is this a show stopper? The error message does politely state this could be an error in a future update. Is it safe to release with this?
Thanks in advance!
I don't know whether to answer my own question or do this edit. Looks like having an empty track may have caused this somehow. When the map has track a RMAnnotation * and a track everything was fine. When I load a map with an empty track, that is with no points in it the trouble and errors show up. If there are no points I don't add the annotation and I no longer get the errors.
I believe that is an exception. Add a breakpoint for exceptions and send in the stack track to either support#mapbox.com or (preferably) the GitHub project:
http://github.com/mapbox/mapbox-ios-sdk

Core Data info & error in console at runtime

I have met the following messages in the console at runtime, and i have no idea why. I have searched everywhere and nobody seems to meet this:
INFO: fetch-response is unable to open the file /Users/userName/Library/Application Support/iPhone Simulator/7.0.3/Applications/964A590B-7131-4BAE-958B-1783BEC193EF/Library/Caches/userName.AppName/fsCachedData/2F1A8708-35A9-491E-9C21-154BA428CA10. Errno: 2
ERROR: failed to mmap cache data from FS: /Users/userName/Library/Application Support/iPhone Simulator/7.0.3/Applications/964A590B-7131-4BAE-958B-1783BEC193EF/Library/Caches/userName.AppName/fsCachedData/83A968D1-0A2B-4D20-97D5-487A876649DC, errno:22
It does not seem to affect the execution though, but I suppose it is not a good sign. I am using Core Data with a timer which frequently updates the database from a server. These messages appear synchronously with the updates, but not systematically. Only one at the time, the "INFO" or the "ERROR". Reset Content and Settings in the Simulator did not solve the problem.
Does anyone have any idea about the meaning of these messages?
I experienced this when running on my device with an app I am building. It has worked perfect for weeks and then all of a sudden this error. I figured out that it is due to a lack of memory available on the device. I use a little app call "System Status" that allows you to view the memory stats and release any old unused memory. I only get this error in Xcode when I have less than 5% available memory on my device. Therefore it cannot load the cache file the app is request, hence the error. Either close all your multitasking apps and restart your device or get the app and free you memory.
After some testing/debugging (sorry for the delay), I have at least a temporary solution.
Because of the multi-threaded saving process of Core Data, I found it a little tricky to identify the exact error location, but it definitely appears that the error occurs when Core Data is trying to save one of the context in the stack (probably the last "root" one).
As each save take a few seconds (without freezing the UI :p) , I figured the error could be generated by a "save overlap".
So even if I do not have enough to be sure, reducing the save frequency effectively solved my problem: no message anymore in the output.
Now there still is a hitch, and any expert answer would be much appreciated!
Uninstalling the app from the device and installing it again removes this error message.
Note that that doesn't fix the problem if you can see this log from earlier versions of your app that is already on your users' devices. It's generally okay to uninstall-install, though, if you're only seeing this during the development phase.
For me this happened when my phone ran out of batteries and died as a result. Deleting the app, then restarting my phone, then rebuilding/installing solved the problem.
I ran into this error because my app was stuck in an infinite loop, doing network requests multiple times a second, causing the file to be overwritten before it could be read.
In the situation described in the original post, this might very well be the case.

Compilation failed for data model at path after upgrading Xcode

After upgrading to Xcode 4.3.2 I have started getting the following error when i do a build:
Compilation failed for data model at path '/Users/Administrator/Library/Developer/Xcode/DerivedData/AppName-ffeggcadwojrwacrwosvadafamrk/Build/Products/Debug-iphoneos/Data.momd/Data.mom'
This was not happening before the upgrade and if i check out the same project on machine running the previous version of Xcode it works fine. No Errors.
I have found a couple of similar posts here and here but none of the answers have helped at all. From the error message the file path it gives doesn't contain a file so i'm guessing its a property somewhere that i need to change but i just can't find it.
Please help, thanks.
EDIT: On further investigation, i can stop it from erroring if i remove certain entities from the data model file, we are currently using a large pre created sqlite file to load data so i could recreate the data model file but that would mean recreating the sqlite which would be a bit of a pain. Anyone know why certain entities cause this?

Resources