![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
dbx cheat sheetObtenido de http://tread.files.wordpress.com/2007/05/dbx-cheatsheet-solaris1.pdf.Loading a programdbx program_namedbx process_id Running a program(dbx) run [args](dbx) run [args] [output ] Examining core filesdbx program_name coredbx core Breakpoints(dbx) stop in function_name(dbx) stop at file:line (dbx) status (dbx) delete all/#breakpoint Steppingnext [n]step [n] cont Examining the call stackwhereExamining variablesprint expressiondisplay expression undisplay expression undisplay 0 Examining memoryexamine address [/ [count] [format]Tracing ExecutionDisplay lines as executed(dbx) trace event_spec [modifier] e.g., trace step trace nextin function trace change variable trace in func thread th_id (dbx) dbxenv trace_speed number (dbx) trace file output_file Debugging multithreadedthreadsthread thread thread_id lwps Miscellaneouslist [function_name]dump (show local variables) regs detach Walking the call stackup [h] [number]down [h] [number] frame [h] [number] Runtime checking(dbx) check memuse(dbx) check access Generates reports about memory access/leaks/use Mismatched corese.g., when debugging a core generated on machine X (customer) using machine Y (developer)(dbx) dbxenv core_lo_pathmap on (dbx) pathmap paths_to_correct_libs (dbx) pathmap /install/ /local/dbg/install/ (dbx) debug program core Fix and continueDbx allows you to fix code and continue debugging without rebuilding/restarting the debug session. To fixyour code: 1. Change source 2. (dbx) fix This rebuilds the .o, loads it in memory and runs till the fix. This does not change the exe, so the exe has to be rebuilt post debugging. Exit(dbx) quit |