Why does the GDB debugger constantly freeze Xcode 4?

This is a really weird mistake ...

I am working on an iPhone project using a camera channel and running it through an OpenGL shader to apply effects to it. However, every time I just create new GLfloat code in the code, the debugger freezes at startup ... I cannot copy and paste the text because the whole Xcode hangs, but I put it together with one of the log files:

GNU gdb 6.3.50-20050815 (Apple version gdb-1518) (Sat Feb 12 02:56:02 UTC 2011) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=x86_64-apple-darwin --target=arm-apple-darwin".2#b2a16f854957b341^ 2@43 "Xcode.IDEFoundation.ConsoleAdaptor.Debugger17"tty /dev/ttys000 (gdb) 

The phone did not freeze, because I can press the home button and continue to do other things. However, Xcode 4 is completely frozen with a beach ball running on 99% of the CPU, and I need to force exit and restart it.

However ... It is really strange that I have an iPhone 3GS, and when I take someone on an iPhone 4, it compiles and works fine. When I get back to the iPhone 3GS, it will be perfect for the first time ... After that, it will hang again again.

Perhaps this is what I'm doing, or is this another Xcode 4 error? I wanted to try switching the debugger to LLDB, but this does not appear in my drop-down list in the Scheme window ... Despite the fact that the Xcode user manual indicates that both GDB and LLDB are available:

http://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/Debugging/Debugging.html

Thanks!

+4
source share
5 answers

Try to open the terminal, AND BE IN RELATION (ON XCODE VERSION) when the program starts working and starts working.

Also, if possible, try downloading xcode 4.1. This seems to fix this annoying problem forever, and I can really use the debugger again!

+1
source

I am also working on a video processing application, and these are exactly the symptoms that I have. he works in the waves. I don’t know why this is the reason, but I am slowly collecting facts to solve this problem:

  • Disabling GDB in the schema settings fixes the problem
  • with GDB ON, “wait for the application to start” seems to solve the problem (more testing is needed).
  • after switching to “stable freeze” mode, which means that the beach ball starts every time, Committing to repository removes the problem (??)
  • restoring the device as a new device for the latest iOS via iTunes solves the problem

all of the above, except disabling GDB, only solves the problem temporarily - it returns after several runs ...

+2
source

I had this problem before and it started to repeat all day today. I tried everything from cleaning the project to restart both the iPad and MacBook Pro and even replace another cable.

What worked, it happened twice: I cleaned up the project, changed the build goal and ran it on the iPhone simulator, the iPad simulator. Then she returned to the original (main) build target (actual application) and launched it on the iPhone and iPad. They all worked correctly, so I finally ran the original application on the iPad, and it worked and continued to work.

It seems that the combination of cleaning up the project, changing build goals and running on the simulator is what previously caused Xcode and my iPad to hang and hang.

Good luck.

+1
source

In my case, it was a wrong code signature identification

0
source

Minimizing NSLog statements in a loop helps applications using OpenGL ES, OpenCV, etc.

0
source

Source: https://habr.com/ru/post/1348128/


All Articles