Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2026-03

What bug tracker is used now?

3 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Unknown author

Hi,

Years back, it was Mantis. What is used now? Does the FPC team use GitLab's own issue tracker?

I discovered a bug (FPC 3.3.1) in TFPHashList when 1000's of entries are added. Find() returns incorrect results. This caused me endless debugging my own debugger. 🙈 I'm working on putting together a sample app that can reproduce the issue. I'll try and submit a patch too - if I can figure it out.

Regards,
- Graeme -

Michael Van Canneyt
to Unknown author
mailinglists--- wrote
Hi, Years back, it was Mantis. What is used now? Does the FPC team use GitLab's own issue tracker?

Yes.

Show quoted text 6 lines
I discovered a bug (FPC 3.3.1) in TFPHashList when 1000's of entries are added. Find() returns incorrect results. This caused me endless debugging my own debugger. 🙈 I'm working on putting together a sample app that can reproduce the issue. I'll try and submit a patch too - if I can figure it out.

If you're talking about gitlab:
It's not difficult. Just drag and drop your patch file to the edit box.

if you're talking about the fix: YMMV :-)

Michael.

Michalis Kamburelis
to Unknown author: Years back, it was Mantis. What is used now? Does the FPC team use GitLab's own issue…
I'll try and submit a patch too - if I can figure it out.

Instead of attaching a patch, one can also fork + commit into fork + submit a "merge request" through GitLab. Quite like a pull request from GitHub :) Then it can be reviewed with GitLab UI, potentially can go through CI, merged using simple click etc.

(I'm not FPC developer, just recommending how I submit FPC/Lazarus patches.)

Regards,
Michalis