Your message dated Wed, 20 Nov 2019 10:25:02 +0100
with message-id <f110380856b01754e91b4e8c0048f8cfa376a5f8.ca...@sfr.fr>
and subject line Re: Bug#943600: lazarus autopkgtest intermittedly fails due to
EAccessViolation: Access violation
has caused the Debian Bug report #943600,
regarding lazarus autopkgtest intermittedly fails due to EAccessViolation:
Access violation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
943600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lazarus
Version: 2.0.2+dfsg-7
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear all,
Version 2.0.2+dfsg-7 of lazarus has failed already at least three times
on the ci.d.n infrastructure. The error is always a logged
EAccessViolation, except the stack isn't always the same length. So far
the offset between the two lowest items is the same.
Paul
https://ci.debian.net/data/autopkgtest/testing/amd64/l/lazarus/3271190/log.gz
An unhandled exception occurred at $0000000000000000:
EAccessViolation: Access violation
$0000000000000000
$000055EFE24EAB67
$000055EFE24EBDC1
https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lazarus/3250811/log.gz
An unhandled exception occurred at $0000000000000000:
EAccessViolation: Access violation
$0000000000000000
$0000557D05069B67
$0000557D0506ADC1
https://ci.debian.net/data/autopkgtest/unstable/amd64/l/lazarus/3250711/log.gz
EAccessViolation: Access violation
$0000563EC38CCBF3
$0000563EC3D9ABC5
$0000563EC3D9EB67
$0000563EC3D9FDC1
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Control: fixed -1 2.0.6+dfsg-2
It seems the fix in 2.0.6+dfsg-2 was enough to hide the access violation.
The change is forwarded to upstream and we will integrate their final patch once
available.
For now we consider this patch enough to fix the problem in Debian.
--
Cheers,
Abou Al Montacir
signature.asc
Description: This is a digitally signed message part
--- End Message ---
