-
Notifications
You must be signed in to change notification settings - Fork 117
SIGSEGV extresist ResNewSDDevice() #353
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
Comments
By the way, I will eventually get back to checking and merging your pull requests. I have not had the time to work on it recently. I don't think any of the traces prior to the segfault are meaningful. The location is being used to store client data for a tile record. The j->deviceList in ResNewSDDevice() is just some random number that happens to be at that location. Usually "Bad Device location" means that magic got confused during the resistance extraction. |
It is the value of Which works out (for MINFINITY in the negative form) like The traces show the specific memory location (of a Tile*) having its |
Sorry, I don't have enough time to look at this in enough detail to make decently informed statements about it. But the basic underlying issue appears to be that |
Thanks Tim for the feedback. The following patch allows the If a version of this patch was to be used, should the This is just so scripts by default will continue to fail. Previously they failed via SIGSEGV now they will fail gracefully via proc error status.
|
I applied this patch to magic version 8.3.509. I suggest leaving the issue open until the underlying "Bad Device" error is resolved. |
error in "extresist". The underlying error still exists and causes a "Bad Device" error but no longer crashes magic. See github Issue #353.
tileJunk==NULL but also design triggers tg_Tdi=-1 which has an ASSERT at the top of ResWriteExtFile(), this log output logs the ASSERT was triggered but continues as if asserts disabled Bad Device diagnostics:
|
Uh oh!
There was an error while loading. Please reload this page.
Please check the script algofoogle/tt09-ring-osc@9971449#diff-521581d2cd10f21d7e928d1436d258208e077a050709787a451bb3c59cab5c75 for any obvious errors in usage
Project and version algofoogle/tt09-ring-osc@9971449
cd sim
cat ext.sh
gdb --args /usr/local/lib/magic/tcl/magicdnull -noconsole -dnull tcl/extract_for_sim.tcl tt_um_algofoogle_tt09_ring_osc
The issue is deref of an invalid memory location
0xc000000000000004
as in CLIENTDEFAULT or MINFINITY:The build up to this SIGSEGV...
The text was updated successfully, but these errors were encountered: