at least some versions of LLDB are like the buggiest ever.
(consider example of lldb erratic behavior, provided by someone else, here both vars are int32_t:
(lldb) print _newestSentSequenceNumber< _newestSeenAckSequenceNumber (_Bool) $19 = true (lldb) print _newestSentSequenceNumber- _newestSeenAckSequenceNumber (int) $20 = 0 (lldb) print _newestSentSequenceNumber (EmiPacketSequenceNumber) $21 = 4456448 (lldb) print _newestSeenAckSequenceNumber (EmiPacketSequenceNumber) $22 = 4456448 (lldb)
)
2012/6/11 Kirill Zorin k.zorin@me.com
I did more testing, and looks like things are fine when using GDB instead of LLDB(= the default in latest Xcode). Maybe this should be added to a wiki page somewhere?
On 2012-06-08, at 3:48 PM, mikel evins wrote:
On Jun 8, 2012, at 11:21 AM, Kirill Zorin wrote:
Is it possible that something that Gambit does to the process' state interferes with Apple's iOS debugger, and/or is there some assumption made by ___setup() about initial process state that's invalidated by something the Xcode debugger does? Or am I barking up the wrong tree here altogether?
Hrm. It's not in any way conclusive, and I may be reinfocing a mistaken hypothesis, but I do recall seeing several debugger-related warnings in the console log when I was reading through them.
Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list