On Thursday 20 November 2014 19:01:06 Geoffrey Barton wrote:
> view>cpu produces a window headed 'CPU I386' with i386 register names.
>
Should be fixed in git master 3f9a033c97332be8a061a3ca37c6e56c0ad7d575.
Martin
--
Dow
On Thursday 20 November 2014 18:43:09 Geoffrey Barton wrote:
> what is the difference between project>make and project>build?
>
Build adds -B, see 'Project'-'Options'-'Make'-'Make options'.
> They both seem to recompile all the units used every time you do either.
> This is rather impractical as,
On Thursday 20 November 2014 19:01:06 Geoffrey Barton wrote:
> view>cpu produces a window headed 'CPU I386' with i386 register names.
>
Set 'Project'-'Debugger'-'Target'-'Processor' to 'arm'. The 'Auto' mode must
be adapted for arm, I'll have a look.
Martin
--
view>cpu produces a window headed 'CPU I386' with i386 register names.
Geoffrey
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
what is the difference between project>make and project>build?
They both seem to recompile all the units used every time you do either.
This is rather impractical as, if you make a simple syntax error in the main
file, this is not detected until after all the other units have been built, so
debu
On Thursday 20 November 2014 16:46:56 Geoffrey Barton wrote:
>
> The 'facedemo' example fails with SIGSEGV too.
>
Can not reproduce, it works for me.
Martin
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Se
On 20 Nov 2014, at 14:18, Geoffrey Barton wrote:
>
> On 20 Nov 2014, at 12:26, Martin Schreiber wrote:
>
>> On Thursday 20 November 2014 12:23:33 Geoffrey Barton wrote:
It loads it into gdb.
>>>
>>> runs ok in gdb.
>>>
Try to start the program by 'Target'-'Next Instruction',
On 20 Nov 2014, at 12:26, Martin Schreiber wrote:
> On Thursday 20 November 2014 12:23:33 Geoffrey Barton wrote:
>>>
>>> It loads it into gdb.
>>
>> runs ok in gdb.
>>
>>> Try to start the program by 'Target'-'Next Instruction',
>>> open the assembler window, step through the assembler code a
On Thursday 20 November 2014 12:23:33 Geoffrey Barton wrote:
> >
> > It loads it into gdb.
>
> runs ok in gdb.
>
> > Try to start the program by 'Target'-'Next Instruction',
> > open the assembler window, step through the assembler code and check what
> > happens.
>
> it goes to 'Stop error:'
>
Wor
On Wednesday 19 November 2014 19:39:34 Geoffrey Barton wrote:
> On 19 Nov 2014, at 16:26, Martin Schreiber wrote:
> > On Wednesday 19 November 2014 12:41:34 Geoffrey Barton wrote:
> >> I am getting 'access violation' when I try and save files. New project
> >> seems to create the template files ok
On 20 Nov 2014, at 09:34, Martin Schreiber wrote:
> On Thursday 20 November 2014 10:04:03 Geoffrey Barton wrote:
>>> Can not reproduce, works for me with FPC 2.4.6 armel-eabi from here:
>>> ftp://gd.tuwien.ac.at/languages/pascal/fpc/dist/2.6.4/arm-linux/fpc-2.6.4
>>> .arm-linux.tar
>>
>> any id
On Thursday 20 November 2014 10:04:03 Geoffrey Barton wrote:
> > Can not reproduce, works for me with FPC 2.4.6 armel-eabi from here:
> > ftp://gd.tuwien.ac.at/languages/pascal/fpc/dist/2.6.4/arm-linux/fpc-2.6.4
> >.arm-linux.tar
>
> any idea how to debug it? When the IDE runs the app, what else is
On 20 Nov 2014, at 06:54, Martin Schreiber wrote:
> On Wednesday 19 November 2014 19:39:34 Geoffrey Barton wrote:
>>
>> ok, this saves now, and compiles. I just edited the caption on the buttion
>> of the 'demo' program. app does not run in ide 'Signal received. Signal
>> SiGSEGV, Segmentation
13 matches
Mail list logo
