After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 604845 - gdb console access?
gdb console access?
Status: RESOLVED WONTFIX
Product: nemiver
Classification: Other
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Fabien Parent
Nemiver maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2009-12-17 17:24 UTC by Filofel
Modified: 2020-03-10 11:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Filofel 2009-12-17 17:24:19 UTC
I am using kgdb, the in-kernel debugger, to debug kernel modules. 
The debugging UI running in the dev machine is gdb, while kgbd in the target presumably implements a subset of the gdbserver. kgdb only supports an UART link connection as of today.
Once everything is set, the debugging process is just identical to that of regular app debugging, and the ability to use nemiver instead of gdb would be a *major* improvement for any kgdb user.

Unfortunately, kernel or kernel module debugging requires to pass some funky commands to set things up. Worse, some of the kgdb / gdb peculiarities are such that the sequence of commands are not always constant.
I haven't found a way to access a "gdb console" inside of nemiver, allowing me to manually drive gdb, for things like 
- resetting the UART, 
- executing a gdb command file (source gdb command), 
- executing add-symbol-file command,
- doing an up then down sequence to initially sync the code at the breakpoint with the source, 
etc... 

Or is there already a way to enter commands commands to the gdb below nemiver that  I missed?)

If such a thing is not currently possible, could it be added to the enhancements list?
I would be soooooooooo happy to use nemiver instead of that poor old crappy ddd that's so painful to use and so poorly integrated into gnome!
Comment 1 Dodji Seketeli 2010-10-14 08:57:18 UTC
Thank you for your interest in Nemiver and sorry for being late to answer. This is definitely an area where we need improvement. FWIW, some discussion is happening about this on the Nemiver mailing list at http://mail.gnome.org/archives/nemiver-list/2010-October/msg00009.html
Comment 2 Dodji Seketeli 2010-10-15 20:50:13 UTC
Commit http://git.gnome.org/browse/nemiver/commit/?id=baab44c48 should fix this in master.

Thanks for the report.
Comment 3 Dodji Seketeli 2010-10-15 20:51:40 UTC
(In reply to comment #2)
> Commit http://git.gnome.org/browse/nemiver/commit/?id=baab44c48 should fix this
> in master.

Arg! no. This comment was meant to bug https://bugzilla.gnome.org/show_bug.cgi?id=631925

Sorry for the noise.
Comment 4 Dodji Seketeli 2012-02-20 10:06:03 UTC
Fabien, as you are working on this enhancement, could you please assign the bug to yourself?

Thanks.
Comment 5 Giovanni Mascellani 2016-04-16 08:17:18 UTC
Is anything happening here? I would like to use GDB console in Nemiver as well. Thanks!
Comment 6 André Klapper 2020-03-10 11:57:21 UTC
Closing all open Nemiver tasks as this project does not seem to be maintained anymore. Please see https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/235#note_732192 for further information. Thanks!