Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UT Symbol table dump size too small on MCP750 (vxworks) #1082

Closed
jphickey opened this issue Jun 25, 2021 · 0 comments · Fixed by #1090 or #1098
Closed

UT Symbol table dump size too small on MCP750 (vxworks) #1082

jphickey opened this issue Jun 25, 2021 · 0 comments · Fixed by #1090 or #1098
Assignees
Labels
bug unit-test Tickets related to the OSAL unit testing (functional and/or coverage)
Milestone

Comments

@jphickey
Copy link
Contributor

Describe the bug
The unit test case that verifies the OS_SymbolTableDump() function has a size limit of only 32000 bytes. The actual size of the symbol table on the MCP750 test platform is larger, and this returns an error.

To Reproduce
Run loader test on MCP750, dump test will fail due to symbol table size limit getting reached

Expected behavior
Test should pass

System observed on:
MCP750, VxWorks 6.9

Reporter Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey added the bug label Jun 25, 2021
@jphickey jphickey self-assigned this Jun 25, 2021
@skliper skliper added this to the 6.0.0 milestone Jun 25, 2021
jphickey added a commit to jphickey/osal that referenced this issue Jun 25, 2021
For the MCP750, the symbol table fairly large and requires a considerably
larger limit to avoid the OS_ERR_OUTPUT_TOO_LARGE limit.  This also uses
a different name, so that the user can actually see the symbol dump file
if they want (otherwise the next test overwrites the file).
@jphickey jphickey added the unit-test Tickets related to the OSAL unit testing (functional and/or coverage) label Jun 25, 2021
astrogeco added a commit that referenced this issue Jul 2, 2021
Fix #1082, increase UT symbol dump size limit
jphickey pushed a commit to jphickey/osal that referenced this issue Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unit-test Tickets related to the OSAL unit testing (functional and/or coverage)
Projects
None yet
2 participants