Hi Krish,

Oops. Yes, there seems to be a bit of an issue here so thanks
for flagging it. I'll follow up offline with you.

Jon.

Hi all,
I ran the following one-liner, dtrace -n 'pid3524:::*read* {}' and dtrace
dumped core. Of course the intention was to place '*read*' as probefunc.
Shouldn't dtrace be exiting gracefully, even if this means searching through
all instructions of the process being traced?

kr...@trantor:~/D-scripts# pstack core
core 'core' of 3621:    dtrace -n pid3524:::*read* {}
fffffd7ffb520f92 dt_getbyte () + 12
fffffd7ffb4ddbff dtrace_get_SIB () + 2f
fffffd7ffb4ddc82 dtrace_get_modrm () + 32
fffffd7ffb4dfbc8 dtrace_disx86 () + 1c00
fffffd7ffb521056 dt_instr_size () + 66
fffffd7ffb5204c8 dt_pid_has_jump_table () + 78
fffffd7ffb520d8f dt_pid_create_glob_offset_probes () + 87
fffffd7ffb511514 dt_pid_per_sym () + 1a4
fffffd7ffb51188d dt_pid_sym_filt () + cd
fffffd7ffc08568f Psymbol_iter_com () + 2bf
fffffd7ffc085902 Psymbol_iter_by_addr () + 2a
fffffd7ffb511a3f dt_pid_per_mod () + 17f
fffffd7ffb511c68 dt_pid_mod_filt () + a8
fffffd7ffc0851a1 i_Pobject_iter () + 71
fffffd7ffc08523c Pobject_iter () + 14
fffffd7ffb511fcd dt_pid_create_pid_probes () + 1dd
fffffd7ffb512622 dt_pid_create_probes () + 16a
fffffd7ffb4e88f6 dt_setcontext () + 6e
fffffd7ffb4e84f4 dt_compile_one_clause () + 34
fffffd7ffb4e87ce dt_compile_clause () + 2e
fffffd7ffb4ea09d dt_compile () + 46d
fffffd7ffb4ea3de dtrace_program_strcompile () + 26
0000000000404d40 compile_str () + 40
00000000004070de main () + bde
00000000004034bc ???????? ()

_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org

_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org

Reply via email to