[MDEV-23467] SIGSEGV in fill_record/fill_record_n_invoke_before_triggers on INSERT DELAYED Created: 2020-08-13 Updated: 2020-10-06 Resolved: 2020-08-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Manipulation - Insert |
| Affects Version/s: | 10.3, 10.4 |
| Fix Version/s: | 10.3.26, 10.4.16 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Roel Van de Paar | Assignee: | Aleksey Midenkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | affects-tests, not-10.1, not-10.2, not-10.5 | ||
| Issue Links: |
|
||||||||
| Description |
|
Though there are many other bugs with similar frames in their stack, I could not locate any open bug that matched this scenario. Closest one was
Leads to:
Bug confirmed present in: Bug confirmed not present in: |
| Comments |
| Comment by Roel Van de Paar [ 2020-08-13 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
InnoDB outcome
Aria gives the same ERROR 1616. MyISAM also crashes:
| ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Roel Van de Paar [ 2020-08-13 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
This bug is seen very frequently in my runs | ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aleksey Midenkov [ 2020-08-24 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
Roel Did you try to reproduce under ASAN/Valgrind? | ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aleksey Midenkov [ 2020-08-24 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
The question is applicable to | ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aleksey Midenkov [ 2020-08-24 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
Roel Can you please link to similar traces bugs? "(in optimized builds)" in title is not true anymore? | ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Roel Van de Paar [ 2020-08-24 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
ASAN on 10.4.14, relevant output (original testcase):
| ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Roel Van de Paar [ 2020-08-25 ] | ||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aleksey Midenkov [ 2020-08-25 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
If it is applicable to any build type the notice about optimized builds in title is misleading. Removing it. Please test ASAN debug first before optimized. This is important if it is not reproducible in debug build. | ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Roel Van de Paar [ 2020-08-25 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
The output on ASAN debug is similar.
| ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aleksey Midenkov [ 2020-08-25 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks! I just wanted to stress that optimized stacks are unimportant when it is reproducible on debug. Reproduces for me. | ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aleksey Midenkov [ 2020-08-25 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
Reproducible without System Versioning:
| ||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Aleksey Midenkov [ 2020-08-25 ] | ||||||||||||||||||||||||||||||||||||||||||||||
|
Correction, please forget this:
And take into accout this: When debug and non-debug builds indeed fail the exact same way, with the debug stack trace being just fuller and better resolved, then of course, it is sufficient to paste only the best one available. © elenst For me as a developer it is important to know whether it is reproducible or not on debug. |