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

Very strange behavior with $warning #816

Closed
veripoolbot opened this issue Sep 5, 2014 · 4 comments
Closed

Very strange behavior with $warning #816

veripoolbot opened this issue Sep 5, 2014 · 4 comments

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Sep 5, 2014


Author Name: Jonathon Donaldson
Original Redmine Issue: 816 from https://www.veripool.org
Original Date: 2014-09-05
Original Assignee: Wilson Snyder (@wsnyder)


I have attached a minimal example that reproduces this issue. The issue occurs with both C++ and SystemC, however I have only provided a C++ example. It also occurs on both my windows and linux machines. I am using the very latest Git repo version: 3.863

My design is as follows:

module our;

initial begin
  assert (1==0) else begin
     $warning ("3 reals: (%f), (%f), (%f)\n", 1.0, 2.5, 5.3); // this outputs gibberish
  end
  $finish;
end

endmodule

When executed the result is this:

[4612811918334230528] %Warning: our.sv:7: Assertion failed in TOP.v: 3 reals: (5.300000), (1.000000), (0.000000)

Ummm...what is that? Haha.

Also, my sc_time_stamp() function is set to always return 0.0. So not sure where that huge number is coming from.

Additionally, if I replace $warning with $error it causes a core dump. If I use either $display or $write it executes just fine.

Any ideas? Let me know if you need any other info.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Sep 5, 2014


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-09-05T02:25:45Z


Simple enough, fixed in git towards 3.863.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Sep 5, 2014


Original Redmine Comment
Author Name: Jonathon Donaldson
Original Date: 2014-09-05T02:35:47Z


Holy cow that was fast. $warning works great now. Thanks!!

However, if you replace $warning with $error it still core dumps as mentioned. Guess the $error core dump is unrelated to the $warning issue. If you want I can create a separate bug ticket...?

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Sep 5, 2014


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-09-05T11:44:13Z


I was hoping $error was the same problem. Yes, I'll need an example and a new bug would be appreciated.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Sep 21, 2014


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-09-21T13:11:22Z


In 3.864.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.