search for: mblk_t

Using the following dtrace command, I can see who''s calling what with lots of +/- numbers: dtrace -n ''fbt:ip:ip_output:entry{@dbtypes[((mblk_t *)arg1)->b_datap->db_type,caller] = count();}'' ...the output is what I want but not how I want to see it. What I''d rather see is the function names associated with caller and for db_type to be output in hex. Looking at the docs online for s10, http://developers.sun.com/so...

...indices into an "associative" array. If all that an array takes as an index is an int64_t, is there any reason for dtrace to require me to have an explicit type conversion in there rather than having it do it for me automatically? At present I need to do: mblks[arg0] or mblks[(int64_t)((mblk_t *)arg0)->b_cont] whereas what I''d like to be able to do is: mblks[arg0] and mblks[((mblks_t *)arg0)->b_cont] and have dtrace worry about what b_cont needs to be transformed into in order for that to work. Darren

1. 566 squeue_enter(squeue_t *sqp, mblk_t *mp, mblk_t *tail, uint32_t cnt, Why cnt is declared as uint32_t (fixed size?) Why not just int or uint_t? 554 * squeue_enter() - enter squeue sqp with mblk mp (which can be 555 * a chain), while tail points to the end and cnt in number of 556 * mblks in the chain. It is not quite clear wh...

...======================================= configure:4318: checking sys/ttcompat.h usability configure:4327: gcc -c -g -O2 -Wall -Wpointer-arith -Wno-uninitialized -I/usr/l ocal/include conftest.c >&5 In file included from configure:4356: /usr/include/sys/ttcompat.h:48: parse error before "mblk_t" /usr/include/sys/ttcompat.h:60: parse error before '}' token /usr/include/sys/ttcompat.h:51: storage size of `t_new_sgttyb' isn't known /usr/include/sys/ttcompat.h:52: storage size of `t_new_tchars' isn't known /usr/include/sys/ttcompat.h:53: storage size of `t_new_ltc...