I would like to debug Inkscape on Windows but given the lack of response here, I want to try a different approach. http://sourceforge.net/p/inkscape/mailman/message/33438177/
It is possible to debug a linux application on Windows using Visual Studio and WinGDB. However, they only support Make, not Btool.
I asked WinGDB for support and this was their reply:
/////////////// WinGDB can work with other build systems than make, but project generation is supported only for make. You should be able to build and debug, though.
You need to change default command lines from 'make' calls to something suitable to build system used. Please consult following sections of the documentation:
http://www.wingdb.com/docs/pages/wg_dev_mingw.htm http://www.wingdb.com/docs/pages/wg_remotebuild.htm
We are not familiar with 'btool' build system, so you need to find out how to call it in order to perform build and clean tasks. /////////////
Anyone know what the btool commands are equivalent to make?
2015-03-01 15:29 GMT+01:00 Bit Barrel <bitbarrelmedia@...400...>:
I would like to debug Inkscape on Windows but given the lack of response here, I want to try a different approach. http://sourceforge.net/p/inkscape/mailman/message/33438177/
Our current debugging process on Windows involves simply using commandline GDB. I don't know whether any of our Windows developers figured out how to make everything work in an IDE.
It is possible to debug a linux application on Windows using Visual Studio and WinGDB. However, they only support Make, not Btool.
I asked WinGDB for support and this was their reply:
/////////////// WinGDB can work with other build systems than make, but project generation is supported only for make. You should be able to build and debug, though.
You need to change default command lines from 'make' calls to something suitable to build system used. Please consult following sections of the documentation:
http://www.wingdb.com/docs/pages/wg_dev_mingw.htm http://www.wingdb.com/docs/pages/wg_remotebuild.htm
We are not familiar with 'btool' build system, so you need to find out how to call it in order to perform build and clean tasks. /////////////
Anyone know what the btool commands are equivalent to make?
Basically the same as make, but to create a workable application you need to write "btool dist". This will create an "inkscape" directory that contains the main binary and all the required libraries.
Regards, Krzysztof
Ok, thanks. So it should work by running btool first, so all libraries are created (no need to debug those) and then just feeding btool make like commands via WinGDB.
If I can make this to work I will create a new wiki page. I think a lot of people will find this useful.
Regards, Tjeerd
On Mon, Mar 2, 2015 at 3:01 AM, Krzysztof Kosiński <tweenk.pl@...1063....> wrote:
2015-03-01 15:29 GMT+01:00 Bit Barrel <bitbarrelmedia@...400...>:
I would like to debug Inkscape on Windows but given the lack of response here, I want to try a different approach. http://sourceforge.net/p/inkscape/mailman/message/33438177/
Our current debugging process on Windows involves simply using commandline GDB. I don't know whether any of our Windows developers figured out how to make everything work in an IDE.
It is possible to debug a linux application on Windows using Visual
Studio
and WinGDB. However, they only support Make, not Btool.
I asked WinGDB for support and this was their reply:
/////////////// WinGDB can work with other build systems than make, but project generation is supported only for make. You should be able to build and debug, though.
You need to change default command lines from 'make' calls to something suitable to build system used. Please consult following sections of the documentation:
http://www.wingdb.com/docs/pages/wg_dev_mingw.htm http://www.wingdb.com/docs/pages/wg_remotebuild.htm
We are not familiar with 'btool' build system, so you need to find out how to call it in order to perform build and clean tasks. /////////////
Anyone know what the btool commands are equivalent to make?
Basically the same as make, but to create a workable application you need to write "btool dist". This will create an "inkscape" directory that contains the main binary and all the required libraries.
Regards, Krzysztof
On 01-Mar-2015 12:01, Krzysztof Kosiński wrote:
I don't know whether any of our Windows developers figured out how to make everything work in an IDE.
Not me! Command line gdb is fine for me anyway. A more pressing issue is that I could never find a decent substitute for valgrind, so it wasn't possible to look for memory issues on the Windows version that can be found on Linux. Dr. Memory appeared to have promise. Unfortunately the last time I tried it, almost 2 years ago, Inkscape wouldn't run in it. I don't recall what the problem was, just that it was a no go.
Regards,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech
I am not the command line debug freak ;-)
I used Code::Blocks as IDE having integrated debugger using MIngW environment. There where recepies to compile and debug Incscape using Eclipse. Currently I have a Book from the library that explains that :-)
Both workflows use btool as builder and use the hast platform for debugging.
Please let me know if you need more directions here.
Adib. --
On Sun, Mar 1, 2015 at 9:01 PM, Krzysztof Kosiński <tweenk.pl@...1063....> wrote:
2015-03-01 15:29 GMT+01:00 Bit Barrel <bitbarrelmedia@...400...>:
I would like to debug Inkscape on Windows but given the lack of response here, I want to try a different approach. http://sourceforge.net/p/inkscape/mailman/message/33438177/
Our current debugging process on Windows involves simply using commandline GDB. I don't know whether any of our Windows developers figured out how to make everything work in an IDE.
It is possible to debug a linux application on Windows using Visual
Studio
and WinGDB. However, they only support Make, not Btool.
I asked WinGDB for support and this was their reply:
/////////////// WinGDB can work with other build systems than make, but project generation is supported only for make. You should be able to build and debug, though.
You need to change default command lines from 'make' calls to something suitable to build system used. Please consult following sections of the documentation:
http://www.wingdb.com/docs/pages/wg_dev_mingw.htm http://www.wingdb.com/docs/pages/wg_remotebuild.htm
We are not familiar with 'btool' build system, so you need to find out how to call it in order to perform build and clean tasks. /////////////
Anyone know what the btool commands are equivalent to make?
Basically the same as make, but to create a workable application you need to write "btool dist". This will create an "inkscape" directory that contains the main binary and all the required libraries.
Regards, Krzysztof
Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
If you can update the wiki on how to use Eclipse, that would be great.
I am also investigating using Visual Studio with WinGDB and VisualGDB. I will make a new wiki for those once I get it to work.
On Wed, Mar 4, 2015 at 12:19 AM, the Adib <theadib@...400...> wrote:
I am not the command line debug freak ;-)
I used Code::Blocks as IDE having integrated debugger using MIngW environment. There where recepies to compile and debug Incscape using Eclipse. Currently I have a Book from the library that explains that :-)
Both workflows use btool as builder and use the hast platform for debugging.
Please let me know if you need more directions here.
Adib.
On Sun, Mar 1, 2015 at 9:01 PM, Krzysztof Kosiński <tweenk.pl@...2179......> wrote:
2015-03-01 15:29 GMT+01:00 Bit Barrel <bitbarrelmedia@...400...>:
I would like to debug Inkscape on Windows but given the lack of response here, I want to try a different approach. http://sourceforge.net/p/inkscape/mailman/message/33438177/
Our current debugging process on Windows involves simply using commandline GDB. I don't know whether any of our Windows developers figured out how to make everything work in an IDE.
It is possible to debug a linux application on Windows using Visual
Studio
and WinGDB. However, they only support Make, not Btool.
I asked WinGDB for support and this was their reply:
/////////////// WinGDB can work with other build systems than make, but project generation is supported only for make. You should be able to build and debug, though.
You need to change default command lines from 'make' calls to something suitable to build system used. Please consult following sections of the documentation:
http://www.wingdb.com/docs/pages/wg_dev_mingw.htm http://www.wingdb.com/docs/pages/wg_remotebuild.htm
We are not familiar with 'btool' build system, so you need to find out how to call it in order to perform build and clean tasks. /////////////
Anyone know what the btool commands are equivalent to make?
Basically the same as make, but to create a workable application you need to write "btool dist". This will create an "inkscape" directory that contains the main binary and all the required libraries.
Regards, Krzysztof
Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
2015-03-02 18:04 GMT+01:00 mathog <mathog@...1176...>:
On 01-Mar-2015 12:01, Krzysztof Kosiński wrote:
I don't know whether any of our Windows developers figured out how to make everything work in an IDE.
Not me! Command line gdb is fine for me anyway. A more pressing issue is that I could never find a decent substitute for valgrind, so it wasn't possible to look for memory issues on the Windows version that can be found on Linux. Dr. Memory appeared to have promise. Unfortunately the last time I tried it, almost 2 years ago, Inkscape wouldn't run in it. I don't recall what the problem was, just that it was a no go.
Another option is to use Address Sanitizer / Thread Sanitizer present in newer GCC. It has a lot lower overhead, though it won't catch memory leaks.
Stack Overflow says that deleaker can be used on Windows instead of Valgrind.
Regards, Krzysztof
participants (4)
-
Bit Barrel -
Krzysztof Kosiński -
mathog -
the Adib