Page MenuHomeFreeBSD

ddb: don't return undefined symbols to a lookup
ClosedPublic

Authored by markj on Jun 18 2015, 5:21 PM.
Tags
None
Referenced Files
Unknown Object (File)
Apr 20 2024, 8:56 AM
Unknown Object (File)
Feb 28 2024, 10:50 AM
Unknown Object (File)
Feb 28 2024, 9:02 AM
Unknown Object (File)
Feb 26 2024, 11:06 AM
Unknown Object (File)
Dec 23 2023, 11:36 AM
Unknown Object (File)
Nov 15 2023, 4:05 PM
Unknown Object (File)
Aug 3 2023, 3:57 PM
Unknown Object (File)
Aug 3 2023, 3:55 PM
Subscribers
None

Details

Summary

Undefined symbols have a value of 0, so it makes no sense to return such
a symbol when performing a lookup by value. This occurs when unwinding
the stack after calling a NULL function pointer, and we confusingly
report the current function as uart_sab82532_class() on amd64.

Convert db_print_loc_and_inst() to only attempt disassembly if we
managed to find a symbol corresponding to the IP. Otherwise we may fault
and reenter the debugger.

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage

Event Timeline

markj retitled this revision from to ddb: don't return undefined symbols to a lookup.
markj edited the test plan for this revision. (Show Details)
markj updated this object.
jhb edited edge metadata.
This revision is now accepted and ready to land.Jun 20 2015, 2:22 PM
This revision was automatically updated to reflect the committed changes.