Re: [anjuta-devel] Sharing code between Nemiver and Anjuta
- From: Johannes Schmid <jhs jsschmid de>
- To: Jens Georg <mail jensge org>
- Cc: anjuta-devel-list <anjuta-devel-list gnome org>, nemiver-list gnome org
- Subject: Re: [anjuta-devel] Sharing code between Nemiver and Anjuta
- Date: Sun, 09 Jun 2013 20:53:10 +0200
Hi all!
How about doing it the Unix way™ and use Nemiver as THE Anjuta debugger,
probably by providing some means of communication (D-Bus, ...) between
them?
I though about this a while and indeed it could work in some way:
* Anjuta would start a nemiver instance with some kind of --no-gui
option that would provide the backend for gdb and the dbus interface
* The dbus interface would work in two ways:
- Anjuta would sent commands to nemiver like it does to gdb at the
moment. It would also very for certain information (Info about
variables, breakpoints etc.)
- Nemiver would itself sent some command to anjuta like the current
line that we are at or things like that.
I am afraid though that the dbus interface might become kinda complex
especially when it comes to transfering data in the sense of
breakpoints, watchpoints, variables. But I don't know enough about dbus
to be sure. And it would require additions to the nemiver codebase but
those might be useful for other tools, too, for example a new way of
remote debugging.
I definitly agree with Sébastian that reading the Nemiver code could
help us understand certain problems of the anjuta debugger better.
Regards,
Johannes
Regards,
Johannes
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]