Re: lazarus debug with gdb [Re: [fpc-devel] bounty: FPC based debugger]

2011-09-13 Thread Marcos Douglas
On Mon, Sep 12, 2011 at 7:59 PM, Martin  wrote:
> On 12/09/2011 23:18, Martin wrote:
>>
>> However, I still recommend trunk => a lot of fixes have been applied.
>
> And if you are on windows, I recommend gdb 7.3
>
> 32bit:
> http://svn.freepascal.org/svn/lazarus/binaries/i386-win32/gdb/bin
> libraries go into the same folder as gdb.

My env is:
Lazarus 0.9.31 r31914 FPC 2.4.5 i386-win32-win32/win64  and FPC 2.5.1 too.

I'm using GDB from:
http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_4/install/binw32
and:
http://svn.freepascal.org/svn/fpcbuild/branches/fixes_2_6/install/binw32

Why Lazarus uses another copy from GDB?
When will be updated the GDB in svn/fpcbuild/* to 7.3?

Thanks,

Marcos Douglas
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: lazarus debug with gdb [Re: [fpc-devel] bounty: FPC based debugger]

2011-09-12 Thread Martin

On 12/09/2011 23:18, Martin wrote:


However, I still recommend trunk => a lot of fixes have been applied.


And if you are on windows, I recommend gdb 7.3

32bit:
http://svn.freepascal.org/svn/lazarus/binaries/i386-win32/gdb/bin
libraries go into the same folder as gdb.

64 bit => not yet updated. Debugging on win64 bit is not yet that good ( 
though if you get yourself the latest gdb, and use fpc trunk, it may 
even work)



Otherwise I recommend at least gdb 7.x
Though version 6.7.5 and 6.8.3 seem to work too for many cases
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


lazarus debug with gdb [Re: [fpc-devel] bounty: FPC based debugger]

2011-09-12 Thread Martin

cced lazarus

On 12/09/2011 22:51, Hans-Peter Diettrich wrote:

Paul Ishenin schrieb:

12.09.2011 19:00, Martin Schreiber wrote:
True. And maintaining all platforms is a fulltime job too. And a FPC 
only debugger can not debug linked c libraries which we can do 
currently with gdb. And think of the remote debugging options gdb 
provides with many targets.
As I understand the plan is to create a new debugger without 
destroying what we already have with gdb. At the moment Lazarus 
allows to write debugger plugins. When the new debugger is ready the 
new plugin should be written.


My wishes don't call for an new (platform dependent) debugger, I only 
want *better* high-level (language specific) support in Lazarus. 
Finally I want to debug applications, not an new debugger with 
different behaviour and restrictions on every platform ;-)


In so far I'm not very interested in commandline and remote debugging, 
when these discourage the use of an already existing debugger (gdb...).


Best to list individual issues.
If told it should work, then the best is to provide little test apps, 
that demonstrate the issue.


See my notes on hints in the other mail though.

However, I still recommend trunk => a lot of fixes have been applied.

Known issues are :
- properties with getter.
- strings 0 versus 1 based (I do hope to test with dwarf3 soon, but no 
idea yet, if it will help...)
- dyn array, element access in deeply nested pascal expression (simple 
cases are normally handled)

- dyn array: not possible to see the entire list.
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel