Hello, everybody.
My name is Alexander, i'm a software developer from St.Petersburg, Russia. I started to use Geany at my job, mostly for C++ development, and only feature I was not satisfied with was debuggers support. I looked at the existing GDB plugin but it's seemed a little bit unusual for me, and next I thought about multiple debuggers support in one plugin. So I started to develop my own plugin with the foregoing in mind: - more VS, Netbeans,... likely GUI - multiple debuggers support
Now i have GDB working more or less enough for using, and feel like I need some feedback. (I started to work on bashbd backend, but faced some problems and decided to postpone it, until GDB and general features will work well).
So, project adress at SF is https://sourceforge.net/projects/geanydbg/ Also I've prepared a little page with a description - http://geanydbg.sourceforge.net/walkthrough.htm
Waiting four your opinions and feedbacks.
Am 07.01.2011 15:17, schrieb Alexander Petukhov:
Hello, everybody.
My name is Alexander, i'm a software developer from St.Petersburg, Russia. I started to use Geany at my job, mostly for C++ development, and only feature I was not satisfied with was debuggers support. I looked at the existing GDB plugin but it's seemed a little bit unusual for me, and next I thought about multiple debuggers support in one plugin. So I started to develop my own plugin with the foregoing in mind:
- more VS, Netbeans,... likely GUI
- multiple debuggers support
Now i have GDB working more or less enough for using, and feel like I need some feedback. (I started to work on bashbd backend, but faced some problems and decided to postpone it, until GDB and general features will work well).
So, project adress at SF is https://sourceforge.net/projects/geanydbg/ Also I've prepared a little page with a description - http://geanydbg.sourceforge.net/walkthrough.htm
Waiting four your opinions and feedbacks.
Just a general: Maybe we should think about renaming as the 'original' one already is called geanydbg[1]
Cheers, Frank
Le 07/01/2011 16:41, Frank Lanitz a écrit :
Am 07.01.2011 15:17, schrieb Alexander Petukhov:
Hello, everybody.
My name is Alexander, i'm a software developer from St.Petersburg, Russia. I started to use Geany at my job, mostly for C++ development, and only feature I was not satisfied with was debuggers support. I looked at the existing GDB plugin but it's seemed a little bit unusual for me, and next I thought about multiple debuggers support in one plugin. So I started to develop my own plugin with the foregoing in mind:
- more VS, Netbeans,... likely GUI
- multiple debuggers support
Now i have GDB working more or less enough for using, and feel like I need some feedback. (I started to work on bashbd backend, but faced some problems and decided to postpone it, until GDB and general features will work well).
So, project adress at SF is https://sourceforge.net/projects/geanydbg/ Also I've prepared a little page with a description - http://geanydbg.sourceforge.net/walkthrough.htm
Waiting four your opinions and feedbacks.
Just a general: Maybe we should think about renaming as the 'original' one already is called geanydbg[1]
AFAIK (and as far as I can see) the original is geanygdb and Alexander's one is geanydbg. OK, it's a bit confusing, but it's at least not the same ^^ But I agree, changing the name to something more different would be better I think.
On the plugin itself, I haven't tested it yet but it seems interesting (though, I'm used to gdb on CLI...), and the UI seems more comfortable to me than geangdb's one (but again, I never tested it...).
Regards, Colomban
Am 07.01.2011 17:02, schrieb Colomban Wendling:
Le 07/01/2011 16:41, Frank Lanitz a écrit :
Am 07.01.2011 15:17, schrieb Alexander Petukhov:
Hello, everybody.
My name is Alexander, i'm a software developer from St.Petersburg, Russia. I started to use Geany at my job, mostly for C++ development, and only feature I was not satisfied with was debuggers support. I looked at the existing GDB plugin but it's seemed a little bit unusual for me, and next I thought about multiple debuggers support in one plugin. So I started to develop my own plugin with the foregoing in mind:
- more VS, Netbeans,... likely GUI
- multiple debuggers support
Now i have GDB working more or less enough for using, and feel like I need some feedback. (I started to work on bashbd backend, but faced some problems and decided to postpone it, until GDB and general features will work well).
So, project adress at SF is https://sourceforge.net/projects/geanydbg/ Also I've prepared a little page with a description - http://geanydbg.sourceforge.net/walkthrough.htm
Waiting four your opinions and feedbacks.
Just a general: Maybe we should think about renaming as the 'original' one already is called geanydbg[1]
AFAIK (and as far as I can see) the original is geanygdb and Alexander's one is geanydbg. OK, it's a bit confusing, but it's at least not the same ^^ But I agree, changing the name to something more different would be better I think.
Oh.... You are right. I'm sorry. But obviously its a good sign for changing :D
Cheers, Frank
Am Freitag, den 07.01.2011, 17:24 +0100 schrieb Frank Lanitz:
Am 07.01.2011 17:02, schrieb Colomban Wendling:
Le 07/01/2011 16:41, Frank Lanitz a écrit :
Am 07.01.2011 15:17, schrieb Alexander Petukhov:
Hello, everybody.
My name is Alexander, i'm a software developer from St.Petersburg, Russia. I started to use Geany at my job, mostly for C++ development, and only feature I was not satisfied with was debuggers support. I looked at the existing GDB plugin but it's seemed a little bit unusual for me, and next I thought about multiple debuggers support in one plugin. So I started to develop my own plugin with the foregoing in mind:
- more VS, Netbeans,... likely GUI
- multiple debuggers support
Now i have GDB working more or less enough for using, and feel like I need some feedback. (I started to work on bashbd backend, but faced some problems and decided to postpone it, until GDB and general features will work well).
So, project adress at SF is https://sourceforge.net/projects/geanydbg/ Also I've prepared a little page with a description - http://geanydbg.sourceforge.net/walkthrough.htm
Waiting four your opinions and feedbacks.
Just a general: Maybe we should think about renaming as the 'original' one already is called geanydbg[1]
AFAIK (and as far as I can see) the original is geanygdb and Alexander's one is geanydbg. OK, it's a bit confusing, but it's at least not the same ^^ But I agree, changing the name to something more different would be better I think.
Oh.... You are right. I'm sorry. But obviously its a good sign for changing :D
geanygdb geanydbg externdbg
...
and I think I remember another plugin which earlier was called geanydbg. Could be that's what externdbg now is and it got renamed right to avoid such confusion for the users... I also vote to rename the plugin.
Regards, Dominic
On Fri, 7 Jan 2011 17:17:01 +0300 Alexander Petukhov Alexander.Petukhov@mail.ru wrote:
Hello, everybody.
Hi.
Now i have GDB working more or less enough for using, and feel like I need some feedback.
Wow, a working, full debugger interface for Geany! At last! :)
Waiting four your opinions and feedbacks.
IMHO, it should be included included in geany-plugins immediately after plugins 0.20 release. The basic functions: Run, Breakpoint, Step, Watches, Locals and Stack all work, though I had Step Into crash once.
Now a few remarks, in the order of appearance:
For some reason, all .[ch] files are marked as executable.
The plugin uses uses vte development files, at least <vte/vte.h>, but configure does not check for them. Perhaps it would be possible, in the future, to drop this dependency (Geany uses libvte directly), but this is low priority, at least for me.
The preferences are currently empty. Obvious candidates are the breakpoint / current line foreground and background (or maybe they can be placed in a configuration file, like the highlighting settings).
Target -> Browse lists all files. The selection would be easier if only the executables are shown, but I'm not sure if the gtk file chooser can handle this.
Shortcuts are good, but a menu will be helpful too - for example, I rarely use Stop, and prefer it unassigned to avoid accidentially terminating a debugging session. In fact, I'd like "Debug" directly in the main menu, after "Build", though other developers may oppose.
The breakpoint hit count does not seem to work, stays 0.
But these are all minor. The one thing that definitely feels uncomfortable is that the display is scrolled on each step (very distracting), and the current line is not even centered, but on about 1/3 of the height. This seems intentional?
Finally, thank you for the good work! Now I hope to drop nemiver soon, since functions like "Load core file" and "Attach to running program" are not really useful to me, while it's lack of shortcut preferences and the different color scheme are inconvenient.
On Fri, 7 Jan 2011 20:39:02 +0200 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
IMHO, it should be included included in geany-plugins immediately after plugins 0.20 release.
So we have plugin #4 to be added post 0.20 ;)
Cheers, Frank
Oops. Pressing Delete in the Watch tab crashes if there are no watches do delete, no matter if the debugger is running or not.
On 07.01.2011 15:17, Alexander Petukhov wrote:
Hello, everybody.
My name is Alexander, i'm a software developer from St.Petersburg, Russia. I started to use Geany at my job, mostly for C++ development, and only feature I was not satisfied with was debuggers support. I looked at the existing GDB plugin but it's seemed a little bit unusual for me, and next I thought about multiple debuggers support in one plugin. So I started to develop my own plugin with the foregoing in mind:
- more VS, Netbeans,... likely GUI
- multiple debuggers support
Now i have GDB working more or less enough for using, and feel like I need some feedback. (I started to work on bashbd backend, but faced some problems and decided to postpone it, until GDB and general features will work well).
So, project adress at SF is https://sourceforge.net/projects/geanydbg/ Also I've prepared a little page with a description - http://geanydbg.sourceforge.net/walkthrough.htm
Waiting four your opinions and feedbacks.
Just tried your plugin, it seems very awesome so far! I seem to like it better than the existing debugger plugin.
I think it would work great with: http://lists.uvena.de/geany-devel/2011-January/003777.html
Best regards.
PS: It crashes if the program to be debugged has no debug symbols.
Thanks Thomas,
I'll try to look at crash on non-debug modules soon, though i didn't have this bug when I tried to debug a plugin itself i.e. run geany as a debug target.
To Geany-plugins mainteiners: how can i start to move source code to geany-plugins svn?
Regading plugin name, does anybody mind if the name will be simply "debugger"? Though GeanyGDB has this title exposed in plugins dialog, no such name is presented as a real plugin name.
Best regards, Alex
Tue, 25 Jan 2011 09:24:39 +0100 письмо от Thomas Martitz thomas.martitz@student.htw-berlin.de:
On 07.01.2011 15:17, Alexander Petukhov wrote:
Hello, everybody.
My name is Alexander, i'm a software developer from St.Petersburg, Russia. I started to use Geany at my job, mostly for C++ development, and only
feature I was not satisfied with
was debuggers support. I looked at the existing GDB plugin but it's seemed a little bit unusual for
me,
and next I thought about multiple debuggers support in one plugin. So I started to develop my own plugin with the foregoing in mind:
- more VS, Netbeans,... likely GUI
- multiple debuggers support
Now i have GDB working more or less enough for using, and feel like I need some feedback. (I started to work on bashbd backend, but faced some problems and decided to
postpone it,
until GDB and general features will work well).
So, project adress at SF is https://sourceforge.net/projects/geanydbg/ Also I've prepared a little page with a description -
http://geanydbg.sourceforge.net/walkthrough.htm
Waiting four your opinions and feedbacks.
Just tried your plugin, it seems very awesome so far! I seem to like it better than the existing debugger plugin.
I think it would work great with: http://lists.uvena.de/geany-devel/2011-January/003777.html
Best regards.
PS: It crashes if the program to be debugged has no debug symbols. _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Tue, 25 Jan 2011 14:50:17 +0300, Александр wrote:
Thanks Thomas,
I'll try to look at crash on non-debug modules soon, though i didn't have this bug when I tried to debug a plugin itself i.e. run geany as a debug target.
To Geany-plugins mainteiners: how can i start to move source code to geany-plugins svn?
First, tell us your Sourceforge username, so we can give you SVN write access. Then just commit your plugin code into trunk/geany-plugins/debugger (or whatever name you'll choose). Afterwards, you/we need to update the autotools and Waf-based build systems to get your plugin built. But this is one of the last steps.
Regading plugin name, does anybody mind if the name will be simply "debugger"? Though GeanyGDB has this title exposed in plugins dialog, no such name is presented as a real plugin name.
It definitely will confuse users but I don't know of anything better so far too :(. Can it replace the geanygdb plugin at some time?
Regards, Enrico
Am Sonntag, den 30.01.2011, 14:09 +0100 schrieb Enrico Tröger:
On Tue, 25 Jan 2011 14:50:17 +0300, Александр wrote:
Thanks Thomas,
I'll try to look at crash on non-debug modules soon, though i didn't have this bug when I tried to debug a plugin itself i.e. run geany as a debug target.
To Geany-plugins mainteiners: how can i start to move source code to geany-plugins svn?
First, tell us your Sourceforge username, so we can give you SVN write access. Then just commit your plugin code into trunk/geany-plugins/debugger (or whatever name you'll choose). Afterwards, you/we need to update the autotools and Waf-based build systems to get your plugin built. But this is one of the last steps.
Regading plugin name, does anybody mind if the name will be simply "debugger"? Though GeanyGDB has this title exposed in plugins dialog, no such name is presented as a real plugin name.
It definitely will confuse users but I don't know of anything better so far too :(. Can it replace the geanygdb plugin at some time?
I actually didn't found time yet to have a look at this new one, but GeanyGDB is quiet unmaintained at present and didn't change since almost a year. Of course I'd appreciate any support or patches, but if this new one does the job more better, than I'd also be fine with replacing GeanyGDB.
Regards, Dominic
SF username is cesspit I'll commit code next week after finishing one bugfixing. I'll cope with autotools, note sure about Waf, never dealed with, I'll ask here if have questions One more question is about windows build, how to avoid plugin to attemt to build under win32? much effors are needed to support cross-platformin, don't have time for it now.
as for GeanyGDB replacement, don't want to sound too assertive, but my one already offers more features than GeanyGDB does and from my point of view is more user friendly, Of course to get it right one definitely has to try out both of them.
also I still aim to reach multiple debuggers support, to do this i wrote some kind of abstracion layer code so general name "debugger" looks suitable for me here also.
Best regards, Alexander
On Sun, 30 Jan 2011 14:09:10 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
On Tue, 25 Jan 2011 14:50:17 +0300, Александр wrote:
Thanks Thomas,
I'll try to look at crash on non-debug modules soon, though i didn't have this bug when I tried to debug a plugin itself i.e. run geany as a debug target.
To Geany-plugins mainteiners: how can i start to move source code to geany-plugins svn?
First, tell us your Sourceforge username, so we can give you SVN write access. Then just commit your plugin code into trunk/geany-plugins/debugger (or whatever name you'll choose). Afterwards, you/we need to update the autotools and Waf-based build systems to get your plugin built. But this is one of the last steps.
Regading plugin name, does anybody mind if the name will be simply "debugger"? Though GeanyGDB has this title exposed in plugins dialog, no such name is presented as a real plugin name.
It definitely will confuse users but I don't know of anything better so far too :(. Can it replace the geanygdb plugin at some time?
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
On 30.01.2011 14:57, Alexander Petukhov wrote:
as for GeanyGDB replacement, don't want to sound too assertive, but my one already offers more features than GeanyGDB does and from my point of view is more user friendly, Of course to get it right one definitely has to try out both of them.
I agree with this, your plugin is a lot better and should eventually replace geanygdb. But yours is not quite stable yet (although geanygdb also isn't IIRC).
Best regards
On Sun, 30 Jan 2011 15:31:14 +0100, Thomas wrote:
On 30.01.2011 14:57, Alexander Petukhov wrote:
as for GeanyGDB replacement, don't want to sound too assertive, but my one already offers more features than GeanyGDB does and from my point of view is more user friendly, Of course to get it right one definitely has to try out both of them.
I agree with this, your plugin is a lot better and should eventually replace geanygdb. But yours is not quite stable yet (although geanygdb also isn't IIRC).
I take this as that we can replace geanygdb at some time by the debugger plugin (e.g. once it got quite stable)?
Regards, Enrico
need more bug reports/feedbacks to make it more stable. will try to do all my best until next geany-plugins release, by the way how often do you issue plugins releases?
On Sun, 30 Jan 2011 15:31:14 +0100 Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
On 30.01.2011 14:57, Alexander Petukhov wrote:
as for GeanyGDB replacement, don't want to sound too assertive, but my one already offers more features than GeanyGDB does and from my point of view is more user friendly, Of course to get it right one definitely has to try out both of them.
I agree with this, your plugin is a lot better and should eventually replace geanygdb. But yours is not quite stable yet (although geanygdb also isn't IIRC).
Best regards _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Sun, 30 Jan 2011 18:05:51 +0300 Alexander Petukhov Alexander.Petukhov@mail.ru wrote:
need more bug reports/feedbacks to make it more stable.
As of revision 36:
Shows all tabs always, so I can't easily tell when a program is running (Browse and Debugger in the Target tab are disabled, so there is some indication).
Applies the debug vertical scroll policy on Geany startup. Interestingly, when Geany is started and debugger is activated after that, the standard policy remains, even when debugging.
yeah, u're right, always visible debug tabs make it hard to tell if the debugger running or not. but, if you are not on the debugger page, i.e. don't see it, you also can't guess what is going on, and the second reason for make them persistent was a bug when after several run/stop actions VTE stopped displaying input or output characters. Now I realized that it was not about it, probably it's better to change things back. As to showing debugger state, I was thinking of a toolbar button with Run or Stop image, based on debugger state, or how is itr done in most IDEs?
On Sun, 30 Jan 2011 18:40:55 +0200 Dimitar Zhekov dimitar.zhekov@gmail.com wrote:
On Sun, 30 Jan 2011 18:05:51 +0300 Alexander Petukhov Alexander.Petukhov@mail.ru wrote:
need more bug reports/feedbacks to make it more stable.
As of revision 36:
Shows all tabs always, so I can't easily tell when a program is running (Browse and Debugger in the Target tab are disabled, so there is some indication).
Applies the debug vertical scroll policy on Geany startup. Interestingly, when Geany is started and debugger is activated after that, the standard policy remains, even when debugging.
-- E-gards: Jimmy _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Sun, 30 Jan 2011 16:57:52 +0300, Alexander wrote:
SF username is cesspit
I added you to the SF geany-plugins project, so you should be able to commit to the SVN repository.
I'll commit code next week after finishing one bugfixing.
Cool.
I'll cope with autotools, note sure about Waf, never dealed with,
Don't worry. I can update the Waf stuff for you.
I'll ask here if have questions One more question is about windows build, how to avoid plugin to attemt to build under win32? much effors are needed to support cross-platformin, don't have time for it now.
The only working way of building the geany-plugins on Windows is to use Waf, at least I do it this way and using autotools on Windows is just a bit of pain in the a** (IMHO). So, to answer your question, I can add a check in the Waf build system to not build the debugger on Windows.
Regards, Enrico
I'm done with commitimg code. Someone could probably look if it;s all right wih it, I'm rather new with svn and autotools.
Regard, Alex
On Sun, 30 Jan 2011 15:47:04 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
On Sun, 30 Jan 2011 16:57:52 +0300, Alexander wrote:
SF username is cesspit
I added you to the SF geany-plugins project, so you should be able to commit to the SVN repository.
I'll commit code next week after finishing one bugfixing.
Cool.
I'll cope with autotools, note sure about Waf, never dealed with,
Don't worry. I can update the Waf stuff for you.
I'll ask here if have questions One more question is about windows build, how to avoid plugin to attemt to build under win32? much effors are needed to support cross-platformin, don't have time for it now.
The only working way of building the geany-plugins on Windows is to use Waf, at least I do it this way and using autotools on Windows is just a bit of pain in the a** (IMHO). So, to answer your question, I can add a check in the Waf build system to not build the debugger on Windows.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
On Sat, 5 Feb 2011 15:48:27 +0300 Alexander Petukhov Alexander.Petukhov@mail.ru wrote:
I'm done with commitimg code. Someone could probably look if it;s all right wih it, I'm rather new with svn and autotools.
Will try to add it to waf build system ;)
Hi,
On Sat, 5 Feb 2011 15:48:27 +0300 Alexander Petukhov Alexander.Petukhov@mail.ru wrote:
I'm done with commitimg code. Someone could probably look if it;s all right wih it, I'm rather new with svn and autotools.
I had a short look. If you include it to geany-plugins project you will not need to have an autogen.sh etc. inside your src tree. Maybe you can have a look at http://git.geany.org/geany-plugins/commit/?id=2aae88ad74247fb882975eec558b5e... as I did add a new plugin some time ago with autotools integration to geany-plugins project.
However, during test for putting it into waf I found some issue which is preventing from being build on my box:
[ 4/143] c: debugger/src/callbacks.c -> _build_/debugger/src/callbacks.c.1.o ../debugger/src/breakpoints.c: In function ‘lookup_breakpoint’: ../debugger/src/breakpoints.c:79: warning: cast to pointer from integer of different size ../debugger/src/breakpoints.c: In function ‘handle_break_remove’: ../debugger/src/breakpoints.c:142: warning: cast to pointer from integer of different size ../debugger/src/breakpoints.c: In function ‘breaks_add’: ../debugger/src/breakpoints.c:301: warning: cast to pointer from integer of different size ../debugger/src/breakpoints.c: In function ‘breaks_is_set’: ../debugger/src/breakpoints.c:445: warning: cast to pointer from integer of different size [ 5/143] c: debugger/src/dbm_bash.c -> _build_/debugger/src/dbm_bash.c.1.o [ 6/143] c: debugger/src/dbm_gdb.c -> _build_/debugger/src/dbm_gdb.c.1.o ../debugger/src/dbm_bash.c: In function ‘on_read_from_bash’: ../debugger/src/dbm_bash.c:187: warning: passing argument 4 of ‘g_io_channel_read_line’ from incompatible pointer type /usr/include/glib-2.0/glib/giochannel.h:234: note: expected ‘gsize *’ but argument is of type ‘gint *’ ../debugger/src/dbm_bash.c: At top level: ../debugger/src/dbm_bash.c:514: error: ‘get_files’ undeclared here (not in a function) ../debugger/src/dbm_gdb.c: In function ‘on_read_from_gdb’: ../debugger/src/dbm_gdb.c:256: warning: passing argument 4 of ‘g_io_channel_read_line’ from incompatible pointer type /usr/include/glib-2.0/glib/giochannel.h:234: note: expected ‘gsize *’ but argument is of type ‘gint *’ ../debugger/src/dbm_gdb.c: In function ‘get_stack’: ../debugger/src/dbm_gdb.c:903: warning: cast from pointer to integer of different size
Maybe you can be so kind and have a look. To be honest, I didn't ;)
Cheers, Frank
Frank, Hi. dbm_bash.c is excluded from autotools build, because it doesn't work for now. As to cast warnings, I don't have them, can guess it's about glib, cause its function are called at lines that were mentioned. Regarding build system, yeah I didn't get clear about commom autoconf and gettext package, will change it today.
Best regards Alex
On Sat, 5 Feb 2011 15:18:52 +0100 Frank Lanitz frank@frank.uvena.de wrote:
Hi,
On Sat, 5 Feb 2011 15:48:27 +0300 Alexander Petukhov Alexander.Petukhov@mail.ru wrote:
I'm done with commitimg code. Someone could probably look if it;s all right wih it, I'm rather new with svn and autotools.
I had a short look. If you include it to geany-plugins project you will not need to have an autogen.sh etc. inside your src tree. Maybe you can have a look at http://git.geany.org/geany-plugins/commit/?id=2aae88ad74247fb882975eec558b5e... as I did add a new plugin some time ago with autotools integration to geany-plugins project.
However, during test for putting it into waf I found some issue which is preventing from being build on my box:
[ 4/143] c: debugger/src/callbacks.c -> _build_/debugger/src/callbacks.c.1.o ../debugger/src/breakpoints.c: In function ‘lookup_breakpoint’: ../debugger/src/breakpoints.c:79: warning: cast to pointer from integer of different size ../debugger/src/breakpoints.c: In function ‘handle_break_remove’: ../debugger/src/breakpoints.c:142: warning: cast to pointer from integer of different size ../debugger/src/breakpoints.c: In function ‘breaks_add’: ../debugger/src/breakpoints.c:301: warning: cast to pointer from integer of different size ../debugger/src/breakpoints.c: In function ‘breaks_is_set’: ../debugger/src/breakpoints.c:445: warning: cast to pointer from integer of different size [ 5/143] c: debugger/src/dbm_bash.c -> _build_/debugger/src/dbm_bash.c.1.o [ 6/143] c: debugger/src/dbm_gdb.c -> _build_/debugger/src/dbm_gdb.c.1.o ../debugger/src/dbm_bash.c: In function ‘on_read_from_bash’: ../debugger/src/dbm_bash.c:187: warning: passing argument 4 of ‘g_io_channel_read_line’ from incompatible pointer type /usr/include/glib-2.0/glib/giochannel.h:234: note: expected ‘gsize *’ but argument is of type ‘gint *’ ../debugger/src/dbm_bash.c: At top level: ../debugger/src/dbm_bash.c:514: error: ‘get_files’ undeclared here (not in a function) ../debugger/src/dbm_gdb.c: In function ‘on_read_from_gdb’: ../debugger/src/dbm_gdb.c:256: warning: passing argument 4 of ‘g_io_channel_read_line’ from incompatible pointer type /usr/include/glib-2.0/glib/giochannel.h:234: note: expected ‘gsize *’ but argument is of type ‘gint *’ ../debugger/src/dbm_gdb.c: In function ‘get_stack’: ../debugger/src/dbm_gdb.c:903: warning: cast from pointer to integer of different size
Maybe you can be so kind and have a look. To be honest, I didn't ;)
Cheers, Frank
Hi,
On Sun, 6 Feb 2011 14:27:25 +0300 Alexander Petukhov Alexander.Petukhov@mail.ru wrote:
dbm_bash.c is excluded from autotools build, because it doesn't work for now.
I'd like to don't add a workaround into build system for this. Can't we remove this from svn until its working as expected?
As to cast warnings, I don't have them, can guess it's about glib, cause its function are called at lines that were mentioned.
Which environment are you using? What are you compiler flags? Did you use -Wall etc?
Regarding build system, yeah I didn't get clear about commom autoconf and gettext package, will change it today.
Not a big thing. Looking forward to.
Cheers, Frank
On 7 February 2011 01:16, Frank Lanitz frank@frank.uvena.de wrote:
Hi,
On Sun, 6 Feb 2011 14:27:25 +0300 Alexander Petukhov Alexander.Petukhov@mail.ru wrote:
dbm_bash.c is excluded from autotools build, because it doesn't work for now.
I'd like to don't add a workaround into build system for this. Can't we remove this from svn until its working as expected?
As to cast warnings, I don't have them, can guess it's about glib, cause its function are called at lines that were mentioned.
Which environment are you using? What are you compiler flags? Did you use -Wall etc?
Or is it 64 bit vs 32 bit?? Its the sort of errors I get compiling unportable 32 bit code on 64 bit machine.
Cheers Lex
Regarding build system, yeah I didn't get clear about commom autoconf and gettext package, will change it today.
Not a big thing. Looking forward to.
Cheers, Frank -- http://frank.uvena.de/en/
Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Sunday 06,February,2011 07:27 PM, Alexander Petukhov wrote:
dbm_bash.c is excluded from autotools build, because it doesn't work for now. As to cast warnings, I don't have them, can guess it's about glib, cause its function are called at lines that were mentioned. Regarding build system, yeah I didn't get clear about commom autoconf and gettext package, will change it today.
Hi Alex,
I've just committed some changes to integrate the debugger plugin into the current geany-plugins autotools build system. While building, I encountered the warnings/errors. They come from improper use of Glib, and from casting pointers into ints and vice versa.
The attached patches should fix the warnings. Please review them and commit as you see fit.
Am 09.02.2011 17:57, schrieb Chow Loong Jin:
gint compare_func(gconstpointer a, gconstpointer b, gpointer user_data) {
- if (a == b)
- gint ia = GPOINTER_TO_INT(a);
- gint ib = GPOINTER_TO_INT(b);
- if (ia == ib) return 0; else
return a> b ? 1 : -1;
return ia> ib ? 1 : -1;
FWIW, this can be replaced with "return ia - ib".
On Thursday 10,February,2011 02:16 AM, Thomas Martitz wrote:
Am 09.02.2011 17:57, schrieb Chow Loong Jin:
gint compare_func(gconstpointer a, gconstpointer b, gpointer user_data) {
- if (a == b)
- gint ia = GPOINTER_TO_INT(a);
- gint ib = GPOINTER_TO_INT(b);
- if (ia == ib) return 0; else
return a> b ? 1 : -1;
return ia> ib ? 1 : -1;FWIW, this can be replaced with "return ia - ib".
Ooh cool, I didn't think of that. Thanks for the tip! Here's a revised patch.
Le 10/02/2011 00:55, Chow Loong Jin a écrit :
On Thursday 10,February,2011 02:16 AM, Thomas Martitz wrote:
Am 09.02.2011 17:57, schrieb Chow Loong Jin:
gint compare_func(gconstpointer a, gconstpointer b, gpointer user_data) {
- if (a == b)
- gint ia = GPOINTER_TO_INT(a);
- gint ib = GPOINTER_TO_INT(b);
- if (ia == ib) return 0; else
return a> b ? 1 : -1;
return ia> ib ? 1 : -1;FWIW, this can be replaced with "return ia - ib".
Ooh cool, I didn't think of that. Thanks for the tip! Here's a revised patch.
No more need for a temporary variable then, since the value is used only once ;)
Jin, thanks for the patches! they were absolutely correct, applied them to the source tree, pls look if its all good now there.
Alex
On Thu, 10 Feb 2011 08:42:34 +0800 Chow Loong Jin hyperair@gmail.com wrote:
On Thursday 10,February,2011 07:58 AM, Colomban Wendling wrote:
No more need for a temporary variable then, since the value is used only once ;)
Aaand another revised patch!
-- Kind regards, Loong Jin
On 25.01.2011 09:24, Thomas Martitz wrote:
I think it would work great with: http://lists.uvena.de/geany-devel/2011-January/003777.html
My quick hack :) http://imagebin.org/134336 I like it!
Best regards.