Hot Door CORE Forum
EXC_BAD_ACCESS Error on Crash Report - Printable Version

+- Hot Door CORE Forum (http://hotdoorcore.com/forum)
+-- Forum: All forums (http://hotdoorcore.com/forum/forumdisplay.php?fid=1)
+--- Forum: General discussion (http://hotdoorcore.com/forum/forumdisplay.php?fid=3)
+--- Thread: EXC_BAD_ACCESS Error on Crash Report (/showthread.php?tid=311)



EXC_BAD_ACCESS Error on Crash Report - zero - 04-07-2022

Hey guys, have been working with hotdoorcore for about 3 weeks now (due to another users suggestions - Rick Smile ) and have been absolutely loving this framework. Really helping me along the path as i get more comfortable in both xCode and C++ as i am a new developer in this language.

I keep getting this Crash report once i close adobe illustrator in my mac environment, but not until after i long click and close the application altogether so it is not running in the background.

I will attach some of the things that (from my limited knowledge) are the proper sections to be looking at, and any help here would be fantastic if anyone has had these errors before. 


Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000beadddde1d40  rbx: 0x00006000003aacc0  rcx: 0x0000000000000002  rdx: 0x000000001ee3a83e
  rdi: 0x0000600003731d40  rsi: 0x0000600000e50b70  rbp: 0x00007ff7bfefd800  rsp: 0x00007ff7bfefd7f0
   r8: 0x0000000000000b70   r9: 0x0000000000000030  r10: 0x00000000000007fb  r11: 0x0000000000000154
  r12: 0x00007ff7bfefdb00  r13: 0x000060000004fb70  r14: 0x00006000003aacc0  r15: 0x000060000004fb90
  rip: 0x000000016f17d33f  rfl: 0x0000000000010202  cr2: 0x000000016f2ecf40

-------------------------------------

Translated Report (Full Report Below)

-------------------------------------



Process:               Adobe Illustrator [34241]

Path:                  /Applications/Adobe Illustrator 2022/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator

Identifier:            com.adobe.illustrator

Version:               26.0.3 (26.0.3)

Code Type:             X86-64 (Native)

Parent Process:        launchd [1]

User ID:               501



Date/Time:             2022-04-07 10:42:44.0188 -0400

OS Version:            macOS 12.3 (21E230)

Report Version:        12

Bridge OS Version:     6.4 (19P4242)

Anonymous UUID:        79B85D9E-B0C2-F1E6-D3A7-E58CBFD289A1



Sleep/Wake UUID:       00943B09-A1A4-43A7-A6C1-F5EE02D236D3



Time Awake Since Boot: 79000 seconds

Time Since Wake:       6391 seconds



System Integrity Protection: enabled



Crashed Thread:        0  Dispatch queue: com.apple.main-thread



Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       UNKNOWN_0xD at 0x0000000000000000

Exception Codes:       0x000000000000000d, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY



Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11

Terminating Process:   exc handler [34241]



VM Region Info: 0 is not in any region.  Bytes before following region: 4294967296

      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL

      UNUSED SPACE AT START

--->  
      __TEXT                      100000000-101254000    [ 18.3M] r-x/r-x SM=COW  ...e Illustrator



Using this link : https://developer.apple.com/documentation/xcode/understanding-the-exception-types-in-a-crash-report
I tried to better understand what is taking place here - but still am not sure.

- zero


RE: EXC_BAD_ACCESS Error on Crash Report - zero - 04-08-2022

Okay so i wanted to reply back to this thread, after spending some time researching this and reading through all of the report - which was 77 pages front and back by the way - i found out that i was really showing my inexperience with c++. 

Seems that when this error is being thrown, it normally means that somewhere you have data that has not been destroyed or deconstructed. I made the mistake of adding a hdi::core::Tool alongside my hdi::core:Tongueanel, and did not add it to the destroy() so that it was properly disposed of. 

As i learn more i want to look into error codes and how specific issues like this one above can be translated into an error code that can be created by hand, but we will see. it may not be possible to do this. 

anyways, back to the research !!