* * *

Author Topic: debugger for windows, fully featured (crowdfunding)  (Read 4867 times)

molly

  • Hero Member
  • *****
  • Posts: 2345
Re: debugger for windows, fully featured (crowdfunding)
« Reply #15 on: December 10, 2017, 02:33:22 am »
Who wants to have a user-friendly Lazarus debugger for windows, please welcome to support developing with money.
Destination:
...
https://www.patreon.com/LazarusDebugger

The modern world of individualism.
No more team work... well, challenge accepted! :D
https://www.patreon.com/duby
Ok.
But I don't understand what we will get if we pay :)
The difference there is that in case of skalogryz, the patreon page is meant as encouragement for the developer(s). Development has already started and will continue even without people donating (as can be read). More money simply means more respect for the developer(s). Duby will progress no matter what, while in your case you won't even start before you receive a certain amount of money (although perhaps not intended that smells fishy to me as that is how any scam works).

I am aware of skalogryz's work, while i can't seem to remember having seen yours.

There is a reason why skalogryz is confident enough to put up a challenge ;)

skalogryz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2020
    • havefunsoft.com
Re: debugger for windows, fully featured (crowdfunding)
« Reply #16 on: December 10, 2017, 04:12:07 am »
But I don't understand what we will get if we pay :) There be a good user-friendly debugger (with expression evaluation, function calls)?
Sure. Expression Valuations + Function Calls were my latest development effort (this October).
Made it work in command-line debugger for functions like this:
Code: Text  [Select]
  1. function Calc(a,b: integer): Integer; cdecl;
  2. function Calc2(a,b: integer): integer;
Note the difference in calling conventions.

and expressions like that:
Code: [Select]
  1+Calc(i,2)*Calc(3,i)
Works with integer types only though.

The hardest part is integration with IDE itself.

The development is currently on hold, for another bounty.

I want only good debugger, not a toy for patching.
Everything is a toy for patching in the software world. (look at recent Apple flows. And that's the company with really deep pockets).
I bet your concern is that you want to be sure, that some one else would be able to patch it for you ;)
Patron Cocoa Widgetset development https://www.patreon.com/skalogryz

Nick

  • New member
  • *
  • Posts: 16
Re: debugger for windows, fully featured (crowdfunding)
« Reply #17 on: December 10, 2017, 10:43:24 am »
There is a reason why skalogryz is confident enough to put up a challenge ;)
I have no objection. But I want good debugging experience. It will be good?

Nick

  • New member
  • *
  • Posts: 16
Re: debugger for windows, fully featured (crowdfunding)
« Reply #18 on: December 10, 2017, 10:53:56 am »
Everything is a toy for patching in the software world.
I don't have fun with that: https://bugs.freepascal.org/view.php?id=29762
There was >40 of broken windows api functions and headers. It was bad experience, to patch what must just work.

skalogryz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2020
    • havefunsoft.com
Re: debugger for windows, fully featured (crowdfunding)
« Reply #19 on: December 10, 2017, 03:21:02 pm »
I don't have fun with that: https://bugs.freepascal.org/view.php?id=29762
There was >40 of broken windows api functions and headers. It was bad experience, to patch what must just work.
It's not a big issue in my view.
If you know what the right declarations are - simply create a stand-alone unit with the proper version and use it.
(no need to recompile rtl or anything)
I run into missing declarations pretty often. Rarely do much fuss about it. (just create my own declaration and use it)

Sharing the findings is definitely a sign of a responsible community member :)

I can argue about "must just work". The headers were created back in the days of win9x, where unicode versions didn't exist.
Headers were "just working" at that time.
There's no dedicated person in FPC team to keep headers up to date with MS releases
So as time went by, headers became outdated.

One can blame Microsoft for not providing up-to-date Pascal versions of their WinAPI.

The same is true for any other 3d party library.
OpenGL is an example. The new APIs are being added by the developers patches, rather than someone from the core team.
Patron Cocoa Widgetset development https://www.patreon.com/skalogryz

 

Recent

Get Lazarus at SourceForge.net. Fast, secure and Free Open Source software downloads Open Hub project report for Lazarus