Open mik1234mc opened 2 years ago
Hi Michael,
It's not intended but it is expected. There's some combination of Verilator+OS that results in this segfault upon exit. The simulation itself appears to have been successful.
Copying a conversation from our Gitter for tracking:
I did try running it under gdb and it seems like the error is during a call to fdClose in iofclose.c: (gdb) where
0 _IO_new_fclose (fp=0x0) at iofclose.c:48
1 0x000055555556715d in VerilatedContextImp::fdClose(unsigned int) ()
2 0x0000555555757f45 in Vtestbench024rootfinal_TOP(Vtestbench024root*) ()
3 0x00005555556aa0a8 in Vtestbench024rootfinal(Vtestbench024root*) ()
4 0x000055555555abcb in main ()
(gdb) looks like a 0x0 argument is passed which is then dereferenced later in the code.
Perhaps Michael can say what version of Verilator and what OS he is running.
On Thu, Jul 14, 2022 at 1:56 PM Dan Petrisko @.***> wrote:
Hi Michael,
It's not intended but it is expected. There's some combination of Verilator+OS that results in this segfault upon exit. The simulation itself appears to have been successful.
Copying a conversation from our Gitter for tracking:
I did try running it under gdb and it seems like the error is during a call to fdClose in iofclose.c: (gdb) where
0 _IO_new_fclose (fp=0x0) at iofclose.c:48
1 https://github.com/black-parrot/black-parrot-sim/issues/1
0x000055555556715d in VerilatedContextImp::fdClose(unsigned int) ()
2 https://github.com/black-parrot/black-parrot-sim/issues/2
0x0000555555757f45 in Vtestbench024rootfinal_TOP(Vtestbench024root*) ()
3 https://github.com/black-parrot/black-parrot-sim/issues/3
0x00005555556aa0a8 in Vtestbench024rootfinal(Vtestbench024root*) ()
4 https://github.com/black-parrot/black-parrot-sim/issues/4
0x000055555555abcb in main () (gdb) looks like a 0x0 argument is passed which is then dereferenced later in the code.
— Reply to this email directly, view it on GitHub https://github.com/black-parrot/black-parrot-sim/issues/10#issuecomment-1184889508, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKK2XQBU67UYH3V4PY6JGYLVUB5ILANCNFSM53TPOAAA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I have Verilator 4.216 and Debian11. I see that you have tagged a specific Verilator version in tools subdir. Should I add this binary version into system $PATH?
Wouldn't hurt to give it a shot but that tag is just the latest we've tried out on CentOS, so the Debian issue is likely to exist
Sounds like Verilator/Debian incompatibility?
On Fri, Jul 15, 2022 at 12:35 AM Dan Petrisko @.***> wrote:
Wouldn't hurt to give it a shot but that tag is just the latest we've tried out on CentOS, so the Debian issue is likely to exist
— Reply to this email directly, view it on GitHub https://github.com/black-parrot/black-parrot-sim/issues/10#issuecomment-1185265336, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKK2XQCLIM55GJW4DOX4LADVUEIEPANCNFSM53TPOAAA . You are receiving this because you commented.Message ID: @.***>
Verilator is tested with Debian by itself, so it's likely a combination of that with Unix pipes
I would to check that the
Segmentation Fault
message in themake -C bp_top/syn tire_kick
output is intended or I have something wrong in my setup.Thanks for confirmation, Michael