#1 Unable to create new Project on Mac OS
Unable to create new Project on Mac OS 10.13 / Mac Intel Workstation (24 Cores) 2012 Model
peda v 0.90
Action: File Menu ---> New Project = Result (File Not Found Error)
Action: File Menu ---> New (+N) = Result (See attached Screenshot)
Action: File Menu ----> Quit (+Q) = Result (Crashed/Aborted)
Process: peda [8181]
Path: /Applications/peda.app/Contents/MacOS/peda
Identifier: com.yourcompany.peda
Version: 0
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: peda [8181]
User ID: 502
Date/Time: 2020-12-16 20:37:36.241 -0800
OS Version: Mac OS X 10.13.6 (17G14042)
Report Version: 12
Anonymous UUID: ¡™£¢∞§¶•ªe-∞•¶-882A-5D57-XXXXXXXXXXXX
Time Awake Since Boot: 38000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
*** error for object 0x7ffceca3cad0: pointer being freed was not allocated
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff782d9b66 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff784a4080 pthread_kill + 333
2 libsystem_c.dylib 0x00007fff782351ae abort + 127
3 libsystem_malloc.dylib 0x00007fff783338a6 free + 521
4 org.qt-project.QtCore 0x000000010950f588 AppleUnifiedLogger::messageHandler(QtMsgType, QMessageLogContext const&, QString const&, QString const&) + 376
5 org.qt-project.QtCore 0x00000001092e29fe 0x1092c4000 + 125438
6 org.qt-project.QtCore 0x00000001092e23c0 0x1092c4000 + 123840
7 org.qt-project.QtCore 0x00000001092e22cd qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) + 13
8 org.qt-project.QtCore 0x00000001093ec238 QDebug::~QDebug() + 104
9 org.qt-project.QtCore 0x0000000109404dbc 0x1092c4000 + 1314236
10 org.qt-project.QtCore 0x000000010940726b QIODevice::write(char const*, long long) + 155
11 org.qt-project.QtCore 0x000000010954b09a 0x1092c4000 + 2650266
12 org.qt-project.QtCore 0x000000010954c4fd QTextStream::~QTextStream() + 45
13 com.yourcompany.peda 0x000000010860b196 Errors::~Errors() + 86
14 libsystem_c.dylib 0x00007fff78235eed __cxa_finalize_ranges + 351
15 libsystem_c.dylib 0x00007fff782361fe exit + 55
16 libdyld.dylib 0x00007fff7818901c start + 8
Thread 1:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff782d01fa mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff782cf714 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff50191dc5 __CFRunLoopServiceMachPort + 341
3 com.apple.CoreFoundation 0x00007fff50191117 __CFRunLoopRun + 1783
4 com.apple.CoreFoundation 0x00007fff50190787 CFRunLoopRunSpecific + 487
5 com.apple.AppKit 0x00007fff4d85afc4 _NSEventThread + 184
6 libsystem_pthread.dylib 0x00007fff784a1661 _pthread_body + 340
7 libsystem_pthread.dylib 0x00007fff784a150d _pthread_start + 377
8 libsystem_pthread.dylib 0x00007fff784a0bf9 thread_start + 13
Thread 2:
0 libsystem_kernel.dylib 0x00007fff782da28a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff784a120e _pthread_wqthread + 1552
2 libsystem_pthread.dylib 0x00007fff784a0be9 start_wqthread + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff782da28a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff784a1009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff784a0be9 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff782da28a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff784a1009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff784a0be9 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fffb0890380 rcx: 0x00007ffee761c518 rdx: 0x0000000000000000
rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007ffee761c550 rsp: 0x00007ffee761c518
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000206
r12: 0x0000000000000307 r13: 0x0000000000000005 r14: 0x0000000000000006 r15: 0x000000000000002d
rip: 0x00007fff782d9b66 rfl: 0x0000000000000206 cr2: 0x00007fffb086d168
Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133
Hello Sea Mac,
I have activated Tickets SF service for PEDA to provide platform to manage problems, please copy the report there
https://sourceforge.net/p/peda/tickets/
I have created mailing list as well
https://sourceforge.net/p/peda/mailman/
As for the MAC, problem is that I and Peter do not use/own MAC. I have lent one at the university for week some time ago to prepare MAC OS build. I would need to ask somebody again to prepare peda-0.95 MAC OS build. That version provides significant enhancements which allows to include components directly in the single file together with schematic design and PCB design data.
The packaging is far from being perfect even for Linux (our main and in the fact only host system platform at PiKRON.com) for now. But feedback is welcomed and we try slowly iterate to more fluent user experience.
To test the software in actual version, I suggest to download peda-examples.tar.gz from https://sourceforge.net/projects/peda/files/peda-examples/ . Then start peda executable from some of examples directory, i.e. mx_cpu https://sourceforge.net/p/peda/peda-examples/ci/master/tree/data/mx_cpu/ . The PEDA loads libraries paths from .pedarc-libs file from the actual startu directory. So you should be able to open mx_cpu2.tdb design file now. The templates fro new designs are located in the examples archive as well. In the theory, they are not strictly tied to the program binary.
As for the crash at the end, I am not sure, may it be some MAC OS build specific problem.
I see Mac OS 10.13 / Powermac5,1 in your bug report, that is really PowerPC based MAC? Have you build the application yourselves or by some setups ( unintended by me) the build on older Intel based MAC buld Qt based application as combined x86+PowerPC binary? It is interesting, because code has never been tested on big-endian system, at least I expect that this should be PowerPC G4 , 32-bit big-endian PowerPC system?
Best wishes,
Pavel
Sorry, I meant "MacPro5,1" - https://everymac.com/ultimate-mac-lookup/?search_keywords=MacPro5%2C1
https://everymac.com/systems/apple/mac_pro/specs/mac-pro-twelve-core-3.06-mid-2012-westmere-specs.html
Last edit: Sea Mac 2020-12-17
Copied your reply from Wiki
Power PC Macs are incapable of running systems past Leopard (10.5) - any OS 10.7 and up is NOT running on a Power PC (G4/G5) Mac.
I might be able to help with building and packaging a Mac build ... maybe. I don't have certain skills ... with compilers and linkers and such. I flowchart well ... but for coding I still tend to think in B.A.S.I.C. Interpreter, or FORTRAN IV (Commodore P.E.T. 2001 ... anyone?)
MacPro5,1 refers to an Apple SERIES of Systems (In this case it does NOT mean a Power PC Machine) - I recommend Mactracker http://www.mactracker.ca/ as a free app to get specs on an Apple systems.
Here is theMacPro5,1 family of workstations: https://everymac.com/ultimate-mac-lookup/?search_keywords=MacPro5,1
Here is my Model: https://everymac.com/systems/apple/mac_pro/specs/mac-pro-twelve-core-3.06-mid-2012-westmere-specs.html Old but still working.
NOTE that I cannot Upgrade this to Any system later than 10.13.6 - Apple no longer supports this system (as of a month or so ago) and I'm NEVER buying Apple Products Again. So Any builds you could get from me might not work on the newest systems.
(I don't have Xcode I'd probably opt for CodeBlocks or some other compiler If I can.)
Last edit: Pavel Pisa 2021-01-17
The PEDA 0.95 version packaged to contain templates and libraries. It is far from ideal but works on MaxOS Catalina 10.15.6 on old Mac from 2010 model.
It is changed to switch working directory to the location where peda/bin/peda.app is located. This allows to specify there configuration. Default paths then point to the libraries one directory above executable file.
The example design peda/examples/teensy_bb/teensy_bb-1.tdb demonstrates new feature of 0.95 version where component schematics marks and modules definition can be optionally included in the design TDB file for full standalone/archival purposes.
No crash or other real problem has been experienced on this MacOS port during short testing. If there are experienced problems by you or others, please report them under this or new issue.