File: debug-bad-binary.test

package info (click to toggle)
binaryen 120-4
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 41,284 kB
  • sloc: cpp: 189,449; javascript: 62,189; ansic: 14,087; python: 5,379; pascal: 441; sh: 77; makefile: 30; asm: 27
file content (41 lines) | stat: -rw-r--r-- 964 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
;; Verify --debug mode prints partial results even after an error.
;;
;; debug-bad-binary.test.wasm contains:
;;
;; (module
;;   (global $A (mut i32) (i32.const 10))
;;
;;   (func $a
;;     (drop
;;       (i32.const 10)
;;     )
;;   )
;;
;;   (func $b
;;     ;; bad opcodes here!
;;   )
;;
;;   (func $c
;;     (drop
;;       (i32.const 30)
;;     )
;;   )
;; )
;;
;; We will error when we get to the bad opcodes. In --debug mode, this test
;; shows that we at least print what we read so far up to that point, which will
;; include both the global and the first function.
;;

RUN: not wasm-opt --debug %s.wasm 2>&1 | filecheck %s

;; CHECK:      Fatal: error parsing wasm. here is what we read up to the error:
;; CHECK-NEXT: (module
;; CHECK-NEXT:  (type $0 (func))
;; CHECK-NEXT:  (global $global$0 (mut i32) (i32.const 10))
;; CHECK-NEXT:  (func $0
;; CHECK-NEXT:   (drop
;; CHECK-NEXT:    (i32.const 10)
;; CHECK-NEXT:   )
;; CHECK-NEXT:  )
;; CHECK-NEXT: )