Recent

Recent Posts

Pages: [1] 2 3 ... 10
1
Other / Re: Forum slow
« Last post by Thaddy on Today at 10:45:59 am »
Seems fixed, probably by the hosting company. I did not experience it.
2
Debugger / Registers dialog - register sequence lost when moving between call frames
« Last post by ccrause on Today at 10:44:26 am »
When the debugger stops at a breakpoint or gets paused, the register dialog is populated with registers supplied by the back end.  The order of the registers typically doesn't change (depending on the back end I assume, I am interested in fpdebug specifically).  If one changes the current call stack frame to a different frame, typically fewer registers are available and the displayed register list is shorter. If one then moves back to the top call frame (with all registers available), the order of the registers is affected. The registers previously displayed stays at the top of the list, while newer (not previously available) registers are added to the bottom of the list. 

For an example refer to the attachments, which shows registers views for 1) the top level frame, 2) the next frame, 3) back to the top frame. My expectation is that the register order should be as the back end supplied them unless the user selected a sort option.

What is the general opinion on this, is this the desired/expected behaviour? I want to change this, but there is quite a bit of code to implement the current behaviour.  I do not want to change this if there are reasons that I am unaware of.
3
Other / Re: Forum slow
« Last post by cdbc on Today at 10:40:57 am »
Hi
Same here  %)
Regards Benny
4
General / Re: HeapTrc not showing line numbers
« Last post by Martin_fr on Today at 10:40:33 am »
Quote
LAZ+FPC trunk, MacOS Sonoma

Make sure "fpc trunk" is the lastest trunk => Afaik (not sure) there were issues on Mac, but they were fixed in fpc trunk.

Try explicitly setting debug info type to dwarf.
5
General / Re: Access violation when opening Tools/Options
« Last post by JuhaManninen on Today at 10:29:38 am »
Quote from: Чебурашка on April 19, 2024, 12:27:34 pm
... when I do Tools/Options I get an Access Violation, that seems related to the parsing of the jedi code formatter settings.
Nobody else seems to have the problem, thus it must be wrong/corrupt data in your local configuration.
Delete or rename your local configuration directory, by default ~/.lazarus
It will be recreated with default data when you start Lazarus again. Do you still get the error?
6
General / Re: HeapTrc not showing line numbers
« Last post by TRon on Today at 10:26:30 am »
User dbannon did a lot of grunt-work some time ago (probably others went the same route even before that, I seem unable to recall) trying to figure that out and the result of that is more or less summarized in this thread.
7
General / HeapTrc not showing line numbers
« Last post by JdeHaan on Today at 09:59:27 am »
Hi,

I'm trying to find out where in my code memory leaks are created (actually, memory not freed properly).
However, the HeapTrc doesn't show the line numbers.
I followed the instructions on this page: https://www.freepascal.org/docs-html/rtl/heaptrc/usage.html
And settings are as in the attached picture.

What am I missing?

Code: Text  [Select][+][-]
  1. Call trace for block $0000000106054400 size 32
  2.   $0000000105E05BA8
  3.   $0000000105E05E9A
  4.   $0000000105E05EEE
  5.   $0000000105E0532A
  6.   $0000000105E052AB
  7.   $0000000105E053EB
  8.   $0000000105E0626B
  9.   $0000000105E061DE
  10.   $0000000105E06956
  11.   $0000000105DFC752
  12.   $0000000105DC5845
  13.   $0000000105DD520C
  14.   $00007FF8178E1366
  15. Call trace for block $0000000106054200 size 32
  16.   $0000000105E05B8D
  17.   $0000000105E05E9A
  18.   $0000000105E05EEE
  19.   $0000000105E0532A
  20.   $0000000105E052AB
  21.   $0000000105E053EB
  22.   $0000000105E0626B
  23.  

---------------------------------
LAZ+FPC trunk, MacOS Sonoma
8
Databases / Re: Step-into the field setter
« Last post by ginoo on Today at 07:50:24 am »
thanks  @Martin_fr
9
General / Re: Access violation when opening Tools/Options
« Last post by TRon on Today at 07:06:49 am »
Debian bookworm x86_64 with mate & gtk here and no problem as described when running Lazarus 2.2.4, 2.2.6, 2.3, 3.0 or 3.2

Have you tried running Lazarus from the commandline ? Usually it emits a couple of lines when things go wrong and those lines might be able to tell more (so please copy-paste those lines to a message in this forum in case it emitted something useful).

It is possible to even obtain more (debug) information by providing commandline options to Lazarus. Type ./lazarus --help for detailed information for the argument --debug-enable and the options that it accepts.
10
Beginners / Re: Does anyone know why these code cannot be compiled by the fpc?
« Last post by TYDQ on Today at 05:24:32 am »
Quote from: Laksen on April 19, 2024, 03:04:14 pm
The proper way to initialize a record is to name each field:
Code: Pascal  [Select][+][-]
  1. const efi_loaded_image_protocol_guid:efi_guid=(data1: $5B1B31A1; data2:$9562; data3: $11D2; data4: ($8E,$3F,$00,$A0,$C9,$69,$72,$3B));

A nice shortcut if you use instead the inbuilt TGuid is that you can write:
Code: Pascal  [Select][+][-]
  1. const efi_loaded_image_protocol_guid: TGuid = '{5B1B31A1-9562-11D2-8E3F-00A0C969723B}';
Thank you,Problem solved.
Pages: [1] 2 3 ... 10

TinyPortal © 2005-2018