Thank you everybody for your hints and suggestions. It helped me a lot!
I have found the source of the crash I’ve been facing recently.
I run a program by passing argc=1 and argv=[“foo”]. For some reason the
'program under JIT’ was getting argc=2.
Based on this number it creates an array of strin
What exactly does your code that 'passes argc=1 and argv=["foo"]' look like?
Did you null-terminate argv as is required?
> On Mar 10, 2017, at 1:45 AM, Alex Denisov via swift-dev
> wrote:
>
> Thank you everybody for your hints and suggestions. It helped me a lot!
> I have found the source of
I just noticed that CGFloat conforms to CustomStringConvertible, but it should
probably conform to LosslessStringConvertible. (Both of its underlying types
support the protocol.) Is this something I can submit a PR for, or does it have
to come out of the Core Graphics team?
--
Brent Royal-Gord
> What exactly does your code that 'passes argc=1 and argv=["foo"]' look like?
> Did you null-terminate argv as is required?
This is exact code I had initially:
auto main = ((int (*)(int, const char **))(intptr_t)mainPointer);
const int argc = 1;
const char *argv[] = { "some-name", NULL };
auto
