Displaying 2 results from an estimated 2 matches for "name_resolv".
Did you mean:
name_resolve
1997 Nov 14
0
Linux IP fragment overlap bug (fwd)
...rst packet */
#define MAGIC 0x3 /* Magic Fragment Constant (tm). Should be 2 or 3 */
#define COUNT 0x1 /* Linux dies with 1, NT is more stalwart and can
* withstand maybe 5 or 10 sometimes... Experiment.
*/
void usage(u_char *);
u_long name_resolve(u_char *);
u_short in_cksum(u_short *, int);
void send_frags(int, u_long, u_long, u_short, u_short);
int main(int argc, char **argv)
{
int one = 1, count = 0, i, rip_sock;
u_long src_ip = 0, dst_ip = 0;
u_short src_prt = 0, dst_prt = 0;
struct in_addr addr;
fprintf(stderr, &...
2008 Aug 25
11
pid-provider sees ld.so.1 only
I''m trying to do some userspace tracing on a server-process with the pid provider.
My problem is, that the only probes the pid-provider lists for the server-process (to which I attach dtrace with "-p nnnn") are coming from "ld.so.1".
There''s not a single one from my modules.
If I''m specifying "a.out" (or any of our shared-objects) as the