How to Solve This Exc_Bad_Access(Code=Exc_I386_Gpflt )In Swift Programming

Getting Thread 10: EXC_BAD_ACCESS (code=EXC_I386_GPFLT) after adding property to my struct

I have exactly the same error.
If I add one more field to codable struct it crashes.
In my case I have two concurrent network requests:

async let req1 = await someManager.fetch()
async let req2 = await someManager.get(id: uid)

let (result1, result2) = await (req1, req2)

I split it to sync network requests:

let result1 = await someManager.fetch()
let result2 = await someManager.get(id: uid)

And it started to working.

I believe there is some issue on iOS side.
I use Xcode 13.4.

Getting error Thread 1: EXC_BAD_ACCESS (code=EXC_I386_GPFLT) when loading AVPlayer

I've made a guide that hopefully shows what you've been misunderstanding.

I apologize to other readers for not using MARKDOWN text format, but please do consider this as my upmost attempt for the original poster. We've already went through sufficient discussions in the previous post.

So, how do you fix this?
I guess there's nothing good to give you codes directly, please try to fix the code based on this information.

And if you have more questions, I'll try my best to help you :)

EXC_BAD_ACCESS (code=EXC_I386_GPFLT) when indexing accessor

Your code is fine apart from one small issue:

cgh.parallel_for(cl::sycl::range<2>(256, 240), [&](cl::sycl::id<2> index) {...}

Here you are capturing variables by reference in your kernel. Don't ever do this.
If you are targeting an accelerator (e.g. GPU), the captured variables will reference host memory and crash when accessed on device. If you only target CPU, it's still undefined behavior since the kernel is executed asynchronously and the captured variables might not exist anymore when the kernel is run.

Therefore, always capture by value in kernel lambdas:

cgh.parallel_for(cl::sycl::range<2>(256, 240), [=](cl::sycl::id<2> index) {...}

In the lambda for command group scope queue.submit([&](sycl::handler& cgh){...}) it is always fine to capture by reference since the command group scope is always evaluated on the host synchronously.

I don't have a triSYCL install at hand, but after this small modification your code ran fine with hipSYCL (which also runs on Mac by the way, in case you'd like to double-check your code with two implementations which can be helpful sometimes).
If changing the lambda capture doesn't solve your problem you might want to open an issue on triSYCL's github repository.

error: Thread 1: EXC_BAD_ACCESS(Code=EXC_I386_GPFLT)

it's really simple:

if You write:

myHood.setMyHoodImg(addHoodImg.image!)

you are supposing addHoodImg.image DOES exist, but on first run, is NIL, if You did not choose an image.
so 2 ways:

1) simply write:

if let hoodDescription = hooddesc.text where hoodDescription  != "" , let img = addHoodImg.image {

2) disable button on start AND enable after choosing and image.

Hope this help.

ps I have a fully functional proto here with (reduced!) classes you use.

EXC_I386_GPFLT in Swift code using Xcode Playground

Process.arguments holds the value that is passed as arguments for a command-line application.

But you're using it in a Playground: there's no access to command line input from a Playground (they are Sandboxed), so Process.arguments is nil and your app crashes when you're doing Process.arguments[1].

The solution is to use this in an actual application, not in a Playground.

---

Related Topics