-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
请问这个教程适应于mac M3芯片吗? #84
Comments
不清楚 |
好滴,回头我试一下 |
报错信息如下:Translated Report (Full Report Below)Process: Fiddler Everywhere [817] Date/Time: 2024-11-29 00:38:38.5851 +0800 Time Awake Since Boot: 25 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Application Specific Information: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1: Thread 2: Thread 3: Thread 4:: ThreadPoolServiceThread Thread 5:: ThreadPoolForegroundWorker Thread 6:: ThreadPoolBackgroundWorker Thread 7:: ThreadPoolForegroundWorker Thread 8:: Chrome_IOThread Thread 9:: MemoryInfra Thread 10: Thread 11: Thread 12: Thread 13: Thread 14: Thread 15: Thread 16: Thread 17: Thread 18: Thread 0 crashed with ARM Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary:
REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"Fiddler Everywhere","timestamp":"2024-11-29 00:38:41.00 +0800","app_version":"5.21.0","slice_uuid":"4c4c4433-5555-3144-a110-ce98d2c2ef4f","build_version":"5.21.0","platform":1,"bundleID":"com.progress-telerik.fiddler","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 15.1.1 (24B2091)","roots_installed":0,"name":"Fiddler Everywhere","incident_id":"9D2DD13B-FBC9-4AA9-B1DF-A20D89BCEB90"}
], ] Model: Mac16,1, BootROM 11881.41.5, proc 10:4:6 processors, 16 GB, SMC |
兄弟,你有没有成功啊, 我搞了5次都没成功, 真的要被搞崩溃了 |
没成功,后面用charles了 |
好吧 @msojocs 建议作者观察下mac m系列有没有成功案例 如果没有的话 可以适当标记出来 我这这个楼主都没成功 |
我没mac,测试不了( 之后我会标记一下未测试 |
如题
The text was updated successfully, but these errors were encountered: