• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
RE: lightweight traces in kernelmode?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: lightweight traces in kernelmode?


  • Subject: RE: lightweight traces in kernelmode?
  • From: Philip Lukidis <email@hidden>
  • Date: Tue, 6 Sep 2005 17:39:30 -0400

I have a small question about firelog.  I have successfully integrated
firelog
into my kext.  However, I did find that I have an issue.

I found that I cannot unload my driver, because the IOFireLog object has
an extra reference to it.  Indeed, in
IOFireLogPublisher::initWithController,
an extra reference is taken on this object.  Removing this extra reference
allowed my driver to unload.  I call this an "extra" reference because as
far as I understand, the reference count of the object would be 1 right
after its creation.

I'm sure that I'm missing something.  If you know what it is, and have
a moment to respond, I would greatly appreciate it.

thanks,

Philip Lukidis

-----Original Message-----
From: Philip Lukidis
Sent: Wednesday, August 31, 2005 2:56 PM
To: Matthew Xavier Mora; email@hidden
Subject: RE: lightweight traces in kernelmode?


Thanks, I'll do that.  I was worried that I would have to recompile the
kernel
with a larger buffer for IOLog, but obviously I like this solution much
better  :-)

Philip Lukidis

-----Original Message-----
From: Matthew Xavier Mora [mailto:email@hidden]
Sent: Wednesday, August 31, 2005 2:34 PM
To: Philip Lukidis; email@hidden
Subject: Re: lightweight traces in kernelmode?


At 11:37 AM -0400 8/31/05, Philip Lukidis wrote:
>Hi.  Are there any facilities for lightweight tracing in kernelmode (like
>IOLog, but not so expensive)?  Or do I have to create my own trace thread,
>and post messages to its queue on my own?  IOLog is expensive, and moreover
>its buffer is so tiny so as to almost render it almost completely useless.
>I need to trace in the IOProc for my audio driver in case of buffer
>problems, and I certainly don't want to use IOLog there.
>
>Does anyone know of any such examples, and/or ready infrastructure to use
>for this?


Use FireLog from the FireWire SDK. Very lightweight and it's what our
team uses internally.

Matt
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
m

This email sent to email@hidden
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • RE: lightweight traces in kernelmode?
      • From: Matthew Xavier Mora <email@hidden>
  • Prev by Date: Re: Coreaudio-api Digest, Vol 2, Issue 267
  • Next by Date: How to use kAudioDevicePropertyChannelCategoryName?
  • Previous by thread: Re: Coreaudio-api Digest, Vol 2, Issue 267
  • Next by thread: RE: lightweight traces in kernelmode?
  • Index(es):
    • Date
    • Thread