That is not 100% true. I use 64-bit Linux (OpenSUSE 12.01),
and I've tested and build RC1 multiple times. The only
failure I had was due to an outdated FPC 2.6.1
The problem is with Lazarus and fpc 2.6.0 installed from the release deb's.
Lazarus is installed in non-user land and when
On 9 August 2012 07:38, Ludo Brands ludo.bra...@free.fr wrote:
The problem is with Lazarus and fpc 2.6.0 installed from the release deb's.
Ah, OK. For those users I then recommend installing from the source
release .zip or .tar.gz file. At least then you can continue testing
Lazarus.
--
On 9 August 2012 08:16, Ludo Brands ludo.bra...@free.fr wrote:
If everybody continues installing from source, RC1 won't
get a lot of testing, does it?
RC1 is still the same product even if you install it from RPM, DEB's
or Source. So yes, the 1.0rc1 product will still get testing. At least
you
Graeme Geldenhuys graemeg.li...@gmail.com hat am 9. August 2012 um 10:24
geschrieben: On 1 August 2012 22:35, Mattias Gaertner
nc-gaert...@netcologne.de wrote:
Please, let me know if you find any problems with these release candidates.
Found another bug... The Project Inspector doesn't
On Saturday 04 of August 2012 23:09:43 Marco van de Voort wrote:
Hello,
Cleaning my harddisk I found a MDI demo (on win32 api level) that I
translated in December.
I haven't gotten around trying to integrate in Lazarus yet (seeing that the
main windowproc very big), but maybe sb wants to
When debugging e.g. a cdecl call to a standard library, how can one
inspect the top few words on the stack?
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
--
___
On 09/08/2012 14:02, Mark Morgan Lloyd wrote:
When debugging e.g. a cdecl call to a standard library, how can one
inspect the top few words on the stack?
Usually at least the top most frame is shown (though locals, and params
may not)
If further frames or some info is missing, then it
On 09/08/2012 14:09, Martin wrote:
On 09/08/2012 14:02, Mark Morgan Lloyd wrote:
When debugging e.g. a cdecl call to a standard library, how can one
inspect the top few words on the stack?
Usually at least the top most frame is shown (though locals, and
params may not)
If further frames or
Martin wrote:
On 09/08/2012 15:01, Mark Morgan Lloyd wrote:
Martin wrote:
If you mean raw memory
depends on cpu. Intel with esp, add a watch, set to memory dump:
^Byte($esp)[-20]
starts 20 bytes before esp
Thanks, I think that'll do. I'm trying to sort out a shared library
call- the
On 09/08/2012 16:14, Mark Morgan Lloyd wrote:
Martin wrote:
If you wont words, and use laz trunk, instead of memory-dump, you can
set the watches repeat count to see multiple indexed elements,
following the given one.
Then you can typecast ^word. The index is not in bytes, but whatever
the
I just installed Lazarus 0.9.30 on Ubuntu 11.10 and have run into all
sorts of problems.
Examples are:
Sometimes I can't switch between the source editor windows (a restart
helps), instead when I click on an editor-tab a breakpoint close to the
mouse cursor gets set.
I can't change editor font
Hi,
after having moved from a 32 bit machine to a 64 bit one I'm
experiencing a problem. I cannot start any program. I think it had been
working a while ago, but now any time a program in lazarus is started a
dialog pops up saying:
Debugger error
Ooops, the debugger entered the error state
Save
On 09/08/2012 22:02, Marc Santhoff wrote:
after having moved from a 32 bit machine to a 64 bit one I'm
experiencing a problem. I cannot start any program. I think it had been
working a while ago, but now any time a program in lazarus is started a
dialog pops up saying:
[Debugger] Running
2012/8/9 Martin laza...@mfriebe.de:
On 09/08/2012 22:02, Marc Santhoff wrote:
after having moved from a 32 bit machine to a 64 bit one I'm
experiencing a problem. I cannot start any program. I think it had been
working a while ago, but now any time a program in lazarus is started a
dialog
14 matches
Mail list logo
