Skip to content

Toggle Routing Cong Cost seg faulting #2373

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

Closed
alanbu1 opened this issue Aug 21, 2023 · 4 comments
Closed

Toggle Routing Cong Cost seg faulting #2373

alanbu1 opened this issue Aug 21, 2023 · 4 comments
Assignees
Labels
bug Incorrect behaviour

Comments

@alanbu1
Copy link
Contributor

alanbu1 commented Aug 21, 2023

Clicking an option under the "toggle routing cong cost" under the routing menu results in a segmentation fault.

@alanbu1 alanbu1 added the bug Incorrect behaviour label Aug 21, 2023
@vaughnbetz
Copy link
Contributor

@nedsels When you move on to graphics please test this (with and without flat routing) and see if there is still a problem. I think it is gone but am not sure.

@vaughnbetz
Copy link
Contributor

@AmirhosseinPoolad : since you're playing with the graphics, can you try this option and see if there is a problem? You can try it with a successful routing (shouldn't show any congestion) and with a failed one; you can run with
--route_chan_width 100 --max_router_iterations 10 (or some other related numbers) to get the router to fail on a not-too-big circuit.

@AmirhosseinPoolad
Copy link
Contributor

I think the PR I just sent fixes this, but maybe we should use at() instead of operator[] to access vectors to avoid this type of issue in the future. At least in places where performance is not as important.

@vaughnbetz
Copy link
Contributor

Thanks; fixed by #2865.
We could use at() more in non-performance critical code, but running the sanitized build (or valgrind) provides equivalent checking with no runtime penalty in release build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect behaviour
Projects
None yet
Development

No branches or pull requests

5 participants