Skip to:

Skip to Jira Navigation
Skip to Side Navigation
Skip to Main Content

Clean TokuDB and MyRocks ASAN and UBSAN mtr runs

General

Escalation

General

Escalation

Description

Ensure that both TokuDB and MyRocks complete mtr under UBSAN and ASAN with no issues.

Environment

None

Child issues

100% Done

UBSAN storage/rocksdb/rocksdb/util/coding.h:384:3: runtime error: load of misaligned address

-

UBSAN storage/rocksdb/rocksdb/util/coding.h:367:3: runtime error: store to misaligned address

-

UBSAN storage/tokudb/PerconaFT/ft/ft-cachetable-wrappers.cc:278:45: runtime error: variable length array bound evaluates to non-positive value

-

UBSAN storage/tokudb/PerconaFT/ft/log_code.cc:1957:10: runtime error: member access within misaligned address

-

UBSAN storage/tokudb/PerconaFT/ft/serialize/wbuf.h:116:37: runtime error: store to misaligned address

-

UBSAN storage/tokudb/PerconaFT/util/x1764.cc:74:38: runtime error: load of misaligned address

-

UBSAN storage/tokudb/PerconaFT/util/omt.cc:532:15: runtime error: null pointer passed as argument 2, which is declared to never be null

-

UBSAN storage/tokudb/PerconaFT/ft/bndata.cc:362:15: runtime error: null pointer passed as argument 2, which is declared to never be null

-

UBSAN storage/tokudb/PerconaFT/ft/ule.cc:907:19: runtime error: store to misaligned address

-

UBSAN storage/tokudb/PerconaFT/ft/ule.cc:956:42: runtime error: load of misaligned address

-

UBSAN storage/tokudb/PerconaFT/ft/txn/rollback-apply.cc:111:46: runtime error: member access within misaligned address

-

UBSAN storage/tokudb/PerconaFT/ft/node.cc:862:16: runtime error: store to misaligned address

-

UBSAN storage/tokudb/PerconaFT/ft/node.cc:1009:30: runtime error: load of misaligned address

-

UBSAN storage/tokudb/PerconaFT/util/mempool.cc:196:11: runtime error: null pointer passed as argument 2, which is declared to never be null

-

UBSAN storage/tokudb/PerconaFT/ft/serialize/wbuf.h:148:11: runtime error: null pointer passed as argument 2, which is declared to never be null

-

UBSAN storage/tokudb/PerconaFT/ft/serialize/quicklz.cc:110:26: runtime error: member access within misaligned address

-

UBSAN storage/tokudb/PerconaFT/ft/serialize/quicklz.cc:154:22: runtime error: load of misaligned address

-

UBSAN storage/tokudb/PerconaFT/ft/serialize/quicklz.cc:204:19: runtime error: store to misaligned address 0x7f086d1ff86b for type 'ui16', which requires 2 byte alignment

-

UBSAN storage/tokudb/PerconaFT/ft/serialize/ft_node-serialize.cc:391:14: runtime error: store to misaligned address 0x7f086d1ff857 for type 'uint32_t', which requires 4 byte alignment

-

UBSAN storage/tokudb/PerconaFT/portability/memory.cc:443:11: runtime error: null pointer passed as argument 2, which is declared to never be null

-

UBSAN storage/tokudb/PerconaFT/ft/cachetable/cachetable.cc:1451:52: runtime error: variable length array bound evaluates to non-positive value 0

-

UBSAN storage/tokudb/PerconaFT/ft/ule.cc:932:15: runtime error: null pointer passed as argument 2, which is declared to never be null

-

UBSAN storage/tokudb/PerconaFT/ft/serialize/ft-serialize.cc:616:32: runtime error: load of misaligned address 0x619000211cc1 for type 'int', which requires 4 byte alignment

-

UBSAN storage/tokudb/PerconaFT/portability/file.cc:413:23: runtime error: null pointer passed as argument 1, which is declared to never be null

-

UBSAN storage/tokudb/PerconaFT/ft/serialize/rbuf.h:92:34: runtime error: load of misaligned address 0x619000211ca5 for type 'uint32_t', which requires 4 byte alignment

-

Smart Checklist

Activity

Show:

Julia Vural March 4, 2025 at 9:02 PM

It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.

Won't Do

Details

Assignee

Unassigned

Reporter

George Lorch(Deactivated)

Labels

Time tracking

2d 7h 15m logged3d 5h 30m remaining

Include subtasks

Components

Priority

Medium

Smart Checklist

Created September 19, 2018 at 8:15 PM

Updated March 4, 2025 at 9:02 PM

Resolved March 4, 2025 at 9:02 PM