Hello,
On Sun, 17 Mar 2019, Pascal Cuoq wrote:
The attached patch makes the program above rejected without crash, does
not seem to break “make test” (I think I know what it looks like when
the tests are broken because my first fix did break them), and it makes
the following program accepted
Hello again,
On 17 Mar 2019, at 13:56, Pascal Cuoq
mailto:c...@trust-in-soft.com>> wrote:
2) I noticed that a variant of the input I initially reported in this thread is
still crashing TCC.
The variant that still crashes TCC as of commit d72b877 is:
void f(char *);
void g(void) {
Hello,
Thanks again Matthias, and also to Michael who fixed the other crashes I had
posted. I was going over the “interesting” inputs generated by fuzzing again,
and:
1) I found a bug in the tool I was using TCC as a reference implementation for,
so the bugs in TCC being fixed is really
Hello,
> On 06 Mar 2019, at 18:56, uso ewin wrote:
>
> I've just push a patch that should fix this issue,
Many thanks for looking into this!
> I hope I didn't add a now bug
All the bugs I have so far are in syntactically incorrect inputs, so it would
be a valid choice not to risk
On Thu, Feb 7, 2019 at 2:45 PM Vad Rulezz wrote:
>
> Hi,
>
> On 06.02.2019 15:59, Pascal Cuoq wrote:
> > as a side-product of working on something else, I found that TCC 0.9.27
> > (x86_64 Linux) crashes for me on the following program:
> [...]
> > However crash.i is close enough to a program
Hi,
On 06.02.2019 15:59, Pascal Cuoq wrote:
> as a side-product of working on something else, I found that TCC 0.9.27
> (x86_64 Linux) crashes for me on the following program:
[...]
> However crash.i is close enough to a program that someone may accidentally
> write that TCC developers may be
Hello,
as a side-product of working on something else, I found that TCC 0.9.27 (x86_64
Linux) crashes for me on the following program:
pascal@TrustInSoft-Box-VII:~/tcc-bin$ cat crash.i
void f(char*);
void g(void) {
f((char[]){,});
}
pascal@TrustInSoft-Box-VII:~/tcc-bin$ bin/tcc crash.i
