* Debugging messages
@ 2007-01-18 14:53 Julian Stecklina
0 siblings, 0 replies; 3+ messages in thread
From: Julian Stecklina @ 2007-01-18 14:53 UTC (permalink / raw)
To: xen-devel
Hello,
I would like to include some debugging messages into the hypervisor
(logging certain hypercalls with their arguments) and am unsure how.
When I call printk where does its output go? Is there a better way to do
this?
Regards,
Julian
^ permalink raw reply [flat|nested] 3+ messages in thread
* debugging messages
@ 2007-03-20 10:59 patrick andrieux
2007-03-20 21:45 ` Ian McDonald
0 siblings, 1 reply; 3+ messages in thread
From: patrick andrieux @ 2007-03-20 10:59 UTC (permalink / raw)
To: dccp
Hi list !
I'm trying to find out where debug messages are print out, like
ccid3_pr_debug(...), DCCP_WARN(...), ....
I compiled the latest kernel 2.6.20-3, with all DCCP options enabled
(DCCP debug messages, ccid2/3 debugging messages, ....) and with all
DCCP patches applied. But I still don't find any messages in log from
/var/log/ .
Did I missed something ?
How can I get these messages ?
Thanks.
regards,
Patrick.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: debugging messages
2007-03-20 10:59 debugging messages patrick andrieux
@ 2007-03-20 21:45 ` Ian McDonald
0 siblings, 0 replies; 3+ messages in thread
From: Ian McDonald @ 2007-03-20 21:45 UTC (permalink / raw)
To: dccp
On 3/20/07, patrick andrieux <patrick.andrieux@gmail.com> wrote:
> Hi list !
>
> I'm trying to find out where debug messages are print out, like
> ccid3_pr_debug(...), DCCP_WARN(...), ....
> I compiled the latest kernel 2.6.20-3, with all DCCP options enabled
> (DCCP debug messages, ccid2/3 debugging messages, ....) and with all
> DCCP patches applied. But I still don't find any messages in log from
> /var/log/ .
> Did I missed something ?
> How can I get these messages ?
>
> Thanks.
>
> regards,
> Patrick.
> -
Hi there Patrick,
First of all you need to turn on debugging when you load the module
e.g. put something like this in /etc/modprobe.d/network
options dccp_ccid3 ccid3_debug=1
options dccp dccp_debug=1
and then make sure you're catching debug message in your
/etc/syslog.conf file with a line something like:
*.* -/var/log/syslog
NB These file locations are for Debian. Look for the equivalent in your distro.
Ian
--
Web: http://wand.net.nz/~iam4
Blog: http://iansblog.jandi.co.nz
WAND Network Research Group
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-03-20 21:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-01-18 14:53 Debugging messages Julian Stecklina
-- strict thread matches above, loose matches on Subject: below --
2007-03-20 10:59 debugging messages patrick andrieux
2007-03-20 21:45 ` Ian McDonald
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.