📸 IG Update : mchoice_artist แม็กกี้หล่อมาก! เรื่องนี้เป็นเรื่องจริงอีกเรื่องหนึ่ง!😭 ทุกคนใน Sigcode กลับบ้านอย่างปลอดภัยนะคะ ✨ #ITSSKINGrandNewPresenter #ITSSKIN_Presenter_Maxky #maxky_rp

โอเค ไม่ใช่แค่ Sigcode เท่านั้นที่ล้อเล่นกับแม็กซ์นะพ่อ 555555 หลวงพ่อแม็ก❌ : อาจจะเป็นหลวงปู่แม็กนะฮะ ✅✅✅ BBAS SHOPEE GARNIER #GarnierUVCoolingxbbasjtr #บาสเด็กอ้วนที่แท้จริง

ฮัลหลีโพ่ ฮัลโหลพี่ย์~~~~~ คำนี้เข้าใจได้ดีโดย sigcode 🤭 #แม็กกี้บาส #6CODE

Sigma.blog for sale. #DomainForSale #Sigma #SigChain #SigAI #SigBot #SigNet #SigVerse #SigData #SigCore #SigPay #SigX #SigLab #SigTech #SigOne #SigIQ #SigWare #SigMeta #SigNode #SigEdge #SigLink #SigCode

Your C/C code suddenly started failing with SIGILL (illegal instruction) signal? @ziglang's zig cc compiler enables sanitizers by default. In x86-64, it sprays ud1 and ud2 instructions here and there, and those instructions are responsible for SIGILL. To make my life easier when debugging those issues, I wrote a simple script to de-sanitize an executable: $./failing SIGILL: illegal instruction PC=0x3725509 m=0 sigcode=2 $ xxd -p -c99999999 failing | sed -E 's/670fb940../9090909090/g' | xxd -p -r > fixed && chmod x fixed $ ./fixed PASS What the script does is replacing the ud1 instruction and its parameters with nop instructions. Why does it work? The way zig cc spits out those checks is as follows: 33b47ac: cmp $0x0,%rax ; test for UB 33b47b0: jne 33b47bb ; if ok, jump to 33b47bb 33b47b6: ud1 0x16(�x),�x ; trip SIGILL signal 33b47bb: mov -0x20(%rbp),%rax ; continue , so the instruction pointer will "jump over" the instruction which triggers SIGILL signal if the condition is ok, but it will execute it if the condition failed. If we instead patch ud1 with nops: 33b47ac: cmp $0x0,%rax 33b47b0: jne 33b47bb 33b47b6: nop 33b47b7: nop 33b47b8: nop 33b47b9: nop 33b47ba: nop 33b47bb: mov -0x20(%rbp),%rax ... we just harmlessly slide through nops and continue operating normally, even if the condition failed. This ops layout doesn't sound like a coincidence. Pretty sure it's compiled like that exactly for the purpose of being able to "turn off" SIGILL, but maybe it's just a fluke. How to fix the issue properly? Actually fix the undefined behavior! Usually boils down to reading uninitialized variables or trying to cast unaligned memory to integers. Happy hacking!

runtime/cgo: pthread_create failed: Operation not permitted SIGABRT: abort PC=0x7fc4c7f2da7c m=0 sigcode=18446744073709551610 goroutine 0 [idle]: runtime: unknown pc 0x7fc4c7f2da7c stack: frame={sp:0x7fff85c8a150, fp:0x0} stack=[0x7fff8548b6a8,0x7fff85c8a6e0) 0x00007fff85c8a050:

runtime/cgo: pthread_create failed: Operation not permitted SIGABRT: abort PC=0x7faf529eea7c m=0 sigcode=18446744073709551610 goroutine 0 [idle]: runtime: unknown pc 0x7faf529eea7c stack: frame={sp:0x7ffcf035cf40, fp:0x0} stack=[0x7ffcefb5e498,0x7ffcf035d4d0) 0x00007ffcf035ce40:

docker build -t myimage . double free or corruption (out) SIGABRT: abort PC=0x7f0e239b9ed7 m=0 sigcode=18446744073709551610

uncompromised WL can prove anything, a compromised WL can't even take a pic of its lead with current paper& sigcode

yes-want to know why it's nec to have a team of bots defending @wikileaks &claiming alive but JA won't sigcode

@sigcode That's a slick looking driver. Play well!

@sigcode Nice! Which irons did you go with?

@sigcode Now that's what we like to hear!