MariaDB Segmentation fault on M4 iPad Pro
- Dominant language
- C
- Stars
- 20.5k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
This may be related to the new M4 Chip on an iPad Pro 13“ with 256GB (8 GB RAM?). MariaDB crashes with a Segmentation Fault. Try to run e.g. `mysql_install_db`.
If there is anything I can to do help, please let me know.
```
360 page fault on 0xf7f573dc at 0x568d2082
stack at ffffd880, base at 0, ip at 568d2082
ffffd880: 570755e4 00000000 00000200 00000000 576e85c0 57728324 00000000 56ee946d
ffffd8a0: 57f6d7d4 00000002 f7ffaf88 f7f8a2ac f7ffcdc8 00000080 f7f89877 f7f8a1e9
ffffd8c0: 57f6d853 00000080 00000001 b5459e19 f7f8975d 00000001 568d1ed5 576a133c
ffffd8e0: 000001e8 f7b858e0 00001010 56eb71ed 00000200 00000000 00000000 000001e8
ffffd900: 0000007f 570755e4 00000200 00000000 576a133c 57f6d853 56eb710e 576a133c
ffffd920: ffffd9fc 00000020 ffffd9fc 56eb1729 00000000 000001e4 00001010 00000030
ffffd940: 0000007f 00000000 00000000 000001e4 00000001 00000000 56eb1687 576a133c
ffffd960: ffffdcd4 57fbcbf0 ffffd9fc 56ea6d25 ffffd9fc 00000020 ffffdc28 56ea7ad8
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the crash with mysql_install_db on the reported M4 iPad Pro environment, using the supplied page-fault address and stack trace as the initial evidence. Done means identifying the cause of the MariaDB segmentation fault and confirming that mysql_install_db no longer crashes in that environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, ios, mariadb
- Domain
- databases, mobile, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100