[MDEV-18241] Downgrade from 10.4 to 10.3 crashes Created: 2019-01-15 Updated: 2019-04-24 Resolved: 2019-04-24 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Server |
| Affects Version/s: | 10.3 |
| Fix Version/s: | 10.2.24, 5.5.64, 10.1.39, 10.3.15, 10.4.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
While we do not expect downgrade between major versions to work, it would be nice if downgrade failed with an error message rather than crash in SIGSEGV. After I fixed a trivial bug in the InnoDB redo log format check, I would encounter a SIGSEGV outside InnoDB.
The test will kill and also normally restart the server. On a normal restart, issue the file command in gdb in order to start up with 10.3 instead. Possibly, also do show args and pass edited arguments to run, to include --lc-messages-dir pointing to 10.3 instead of 10.4. Whether or not I adjusted --lc-messages-dir, I would get a SIGSEGV within the following stack trace:
|