Date: Mon, 11 Feb 2013 11:49:00 +0400 From: "Alexander V. Chernikov" <melifaro@FreeBSD.org> To: h bagade <bagadeh@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: debug em driver code after applying patch Message-ID: <5118A26C.2050300@FreeBSD.org> In-Reply-To: <CAARSjE2yxtFR5i8zgc5OoOPahRzd8B0SReyg7KDTsMRgQeyssg@mail.gmail.com> References: <CAARSjE2yxtFR5i8zgc5OoOPahRzd8B0SReyg7KDTsMRgQeyssg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05.02.2013 18:44, h bagade wrote: > Hi all, > > I applied patch on em driver code and I want to check how it is working on > different situations. I need to put some output in different parts of the > code to trace what's going on in different situations. > I've tried to write to files or executing commands(like echo) using system > function, but in these two methods, by adding headers some conflicting > issues happen which I don't know how to resolve! > > I've tried to use it's macros like INIT_DEBUGOUT to print some messages but > it only works on startup, not when the system is running! > > I don't know how to print out messages to debug the code?! Is there anybody > to help me handle it? I really need help. You can use printf or log for some rarely-called cases (see printf(9)). for others you can take a look on ktr(9) API and ktrdump(8). > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5118A26C.2050300>