Use latest pfff not generating NO_FILE_INFO_YET when parsing invalid …

…C code

Fixes #1925

test plan:
$ /home/pad/semgrep/_build/default/cli/Main.exe -dump_ast foo.c
foo.c:3:0: Lexical error: unrecognised symbol, in token rule:#
Raised at file "parsing/Parse_code.ml", line 144, characters 24-27
Called from file "parsing/Parse_code.ml", line 236, characters 18-48

no more NO_FILE_INFO_YET error (which causes the python wrapper
to crash).

Also:
$ semgrep -l c -e 'FOO' tests/OTHER/parsing_errors/foo.c
ran 1 rules on 1 files: 0 findings
1 files could not be analyzed; run with --verbose for details or run with --strict to exit non-zero if any file cannot be analyzed

semgrep-core/cli/Main.ml

@@ -850,13 +850,15 @@ let dump_pattern (file: Common.filename) =
 let dump_ast file =
   match Lang.langs_of_filename file with
   | lang::_ ->
+   E.try_with_print_exn_and_reraise file (fun () ->
     let (x, errs) =
       Parse_code.parse_and_resolve_name_use_pfff_or_treesitter lang file in
     if errs <> []
     then failwith (spf "fail to fully parse %s" file);
     let v = Meta_AST.vof_any (AST_generic.Pr x) in
     let s = dump_v_to_format v in
     pr s
+   )
   | [] -> failwith (spf "unsupported language for %s" file)
 (*e: function [[Main_semgrep_core.dump_ast]] *)
 

semgrep-core/tests/OTHER/parsing_errors/foo.c

@@ -0,0 +1,4 @@
+
+
+# this is invalid code
+int x = 1