--gdb flag does not work #454
Comments
|
Original Redmine Comment Yup, need some more documentation here, thanks for the patch. The --gdb flag presumes a script which starts gdb. Note --gdb on a test invocation (test_regress/t/t_FOO.pl --gdb) presumes that script "gdbrun" by default. --args intentionally isn't there because some non-gdb debuggers do not support that switch. I can put the gdbrun script into the distribution but that doesn't feel right as it has personal preferences and is another layer that people shouldn't have to be burdened with. My inclination then is to make --gdb behave like --gdbbt without the automatic exit. If VERILATOR_GDB environment variable is set it will override this behavior and allow an arbitrary script to be called (for other debuggers). Make sense? |
|
Original Redmine Comment Actually that will make running ddd a pain. I think VERILATOR_GDB should presume gdb-like behavior. |
|
Original Redmine Comment That all seems reasonable. We have to assume that anyone playing with --gdb is technically reasonably competent, so we really just need to update the documentation to explain how it is supposed to work. Would you like me to update the documentation? |
|
Original Redmine Comment Fixed in git towards 3.833. |
|
Original Redmine Comment In 3.833. |
veripoolbot
added
area: invoking/options
Author Name: Jeremy Bennett (@jeremybennett)
Original Redmine Issue: 454 from https://www.veripool.org
Original Date: 2012-03-09
Original Assignee: Jeremy Bennett (@jeremybennett)
Although not documented in the main manual, the internals guide notes the use of --gdb to start Verilator tests under the GNU debugger.
The internals document is slightly in error, since the usage is not --gdb, but --gdb , thus giving the user the option of using another debugger (for example ddd).
The other problem is that the invocation of gdb is constructed as:
GDB does not pass arguments to the inferior (i.e. the program being debugged) in this way, it expects them to be preceded by --args:
This requires a small modification to the verilator PERL script, which in turn requires that any debugger used with the --gdb option to Verilator follow this convention.
I attach a patch against current git HEAD (commit 0ae00fc) for these changes.
The text was updated successfully, but these errors were encountered: