------------------------------- KNOWN BUG LIST ---------------------------------
DESCRIPTION:
RESOLUTION STATUS:
--------------------------------------------------------------------------------
----------------------------- PROPOSED TODO LIST -------------------------------
DESCRIPTION:
The functions that implement the "search" command (most notably when using
the "search -k" option) were originally written to be architecture-neutral,
on machines with:
(1) a single unity-mapped region to map physical memory, and
(2) a single vmalloc region for module memory and other vmalloc() callers.
However, architectures may contain more kernel virtual memory regions than
just those two regions. For example, the ia64 and x86_64 architectures
contain mapped, relocatable, kernel text/static-data regions; and the x86_64
separates its vmalloc() region from the mapped region containing kernel
modules. In the case of x86_64 specifically, the mapped kernel region
is skipped entirely; it overlaps with the unity-mapped section, but it
would be helpful to check/display both addresses. So it makes sense to
have some special handling for the mapped kernel regions on those two
architectures.
RESOLUTION STATUS: TBD
--------------------------------------------------------------------------------
DESCRIPTION:
Code restructuring:
- streamline the *_init() functions so as that crash is at least
able to open the dump image and perform minimal set of commands
like bt, dump dmesg log, disassemble etc. irrespective of kernel
version.
RESOLUTION STATUS: TBD
--------------------------------------------------------------------------------
DESCRIPTION:
Mini report:
- The goal of this is to produce a summary report of common information
that is used to track problems. The idea here is for many problems we
probably don't need to get the whole dump shipped and as you probably
figured out by now it is not easy to ship and store these huge dump
files.
RESOLUTION STATUS: TBD
--------------------------------------------------------------------------------
DESCRIPTION:
Automatic verification of the dump:
- When you get a dump to look at problem there are few common tasks
one performs, the idea here is to automate those tasks and provide
a simple interface in the tool. Another possibility is automatic
verification of important datastructures, for example if the task
list says there are 30 tasks this feature automatically walks the
list and counts to verify if there are 30 in the list or not, if 30
entries or not found this may give a clue of some kind of a
corruption.
RESOLUTION STATUS: TBD
--------------------------------------------------------------------------------
DESCRIPTION:
Function arguments:
- Display arguments in the stack trace. At present, we do not have
support for PPC64 and x86_64. On PPC64, user can dump retrieve only
for top level frame from pt_regs. However, user can dump complete
stack frame and read arguments. So, it is manual process and need
to have some expertise on the stack frame
RESOLUTION STATUS: TBD
--------------------------------------------------------------------------------
DESCRIPTION:
Local variables:
- Facilitate possible display of local variables with stack frames
Since we are using debug vmlinux, we can find local variables
locations from Dwarf2.
RESOLUTION STATUS: TBD
--------------------------------------------------------------------------------
DESCRIPTION:
User space enhancements:
- show user space stack backtrace, if present in the dump file,
- ability to link user space namelist (debug object files),
RESOLUTION STATUS: TBD
--------------------------------------------------------------------------------
DESCRIPTION:
Platform specific enhancements:
- Establish CPU registers at the time of exceptions in the current
context
- Ability to handle CPU registers from current context using symbols
in expressions
- Ability to format basic processor structures like LDT, GDT, task
gates for x86 arch
RESOLUTION STATUS: TBD
--------------------------------------------------------------------------------
DESCRIPTION:
Scripting support:
- integrating scripting support with perl or python like language,
"Alicia" can be one example or the solution itself.
RESOLUTION STATUS:
SIAL script support implemented in version 4.0-4.7 (lucchouina@yahoo.com)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------