Newbie ddb question
I've been poking around in ddb in an attempt to work on some forkbomb/low memory problems, and I've found it extremely useful. There's one thing I can't figure out how to do that would be useful, though. Say that I have a process of interest tsleeping. Is there some way for me to get a backtrace of that process at the time it entered tsleep? In the case I'm creating, many processes are tsleeping on vmwait. As there are multiple places where such a wait can occur, I'd really like to see which codepaths are causing processes to enter that state. The trace command doesn't seem to have the necessary functionality to do this, so I was thinking that I might be able to simulate such an effect by putting a null pointer reference right before such calls, thereby creating a panic. Is this the best way to go, or is there some easier way to accomplish a similar effect? Thanks, Mike Silby' Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Newbie ddb question
On Thu, 14 Feb 2002, Mike Silbersack wrote: I've been poking around in ddb in an attempt to work on some forkbomb/low memory problems, and I've found it extremely useful. There's one thing I can't figure out how to do that would be useful, though. Say that I have a process of interest tsleeping. Is there some way for me to get a backtrace of that process at the time it entered tsleep? In the case I'm Try t pid. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Newbie ddb question
On Thu, 14 Feb 2002, Bruce Evans wrote: On Thu, 14 Feb 2002, Mike Silbersack wrote: I've been poking around in ddb in an attempt to work on some forkbomb/low memory problems, and I've found it extremely useful. There's one thing I can't figure out how to do that would be useful, though. Say that I have a process of interest tsleeping. Is there some way for me to get a backtrace of that process at the time it entered tsleep? In the case I'm Try t pid. Bruce Ah, I see now. That never got MFC'd to -stable. I'll see if it's easily MFCable, or just move my testing over to -current. Thanks, Mike Silby Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
