Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

p4test segfaults when provided with two -v flags #838

Closed
hanw opened this issue Aug 10, 2017 · 5 comments
Closed

p4test segfaults when provided with two -v flags #838

hanw opened this issue Aug 10, 2017 · 5 comments
Labels
wontfix This is a problem that will not be fixed.

Comments

@hanw
Copy link
Contributor

hanw commented Aug 10, 2017

happens with any p4-16 problem.

./p4test -I p4include --p4v=16 ~/p4-tests/mint.p4 -v -v
Invoking preprocessor
cc -E -x c -Wno-comment -C -undef -nostdinc  -Ip4include -I/Users/hanwang/bf-p4c-compilers/build/p4c/./p4include /Users/hanwang/p4-tests/mint.p4
Parsing P4-16 program /Users/hanwang/p4-tests/mint.p4
Segmentation fault: 11
@mihaibudiu
Copy link
Contributor

I cannot reproduce this problem; I have run successfully p4test with two -v flags using test programs from the testdata/p4_16_samples folder.

@hanw
Copy link
Contributor Author

hanw commented Aug 15, 2017

With two -v flags, I had the issue with a program that is using another architecture definition (not v1model).

With three -v flags, following error happens on

./p4test --p4v=16 ~/bf-p4c-compilers/p4-tests/p4_16/apply_if.p4 -v -v -v

518655.588:gc:1:****** GC called ****** (heap size 479232)
518655.588:gc:1:****** GC called ****** (heap size 479232)
518655.588:gc:1:****** GC called ****** (heap size 479232)
518655.588:gc:1:****** GC called ****** (heap size 479232)
518655.588:gc:1:****** GC called ****** (heap size 479232)
Segmentation fault: 11

@mihaibudiu
Copy link
Contributor

Can you please supply a program that reproduces this problem? apply_if is not part of the testsuite.
I have tried several of the tests and none has failed yet.

@sethfowler
Copy link
Contributor

Han, can you still reproduce now that #852 has landed?

@mihaibudiu
Copy link
Contributor

If this is fixed perhaps we can close it.

@fruffy fruffy added wontfix This is a problem that will not be fixed. and removed invalid labels Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This is a problem that will not be fixed.
Projects
None yet
Development

No branches or pull requests

4 participants