Re: Linuxulator: possible Giant pushdown victim

2001-09-10 Thread John Baldwin
On 10-Sep-01 Dag-Erling Smorgrav wrote: > Julian Elischer <[EMAIL PROTECTED]> writes: >> Marcel Moolenaar wrote: >> > BTW: Do we have handy functions for use in the remote debugger, such >> > as show_proc, show_vm or whatever, that dump important information >> > in a readable form? >> Matt has a

Re: Linuxulator: possible Giant pushdown victim

2001-09-10 Thread Dag-Erling Smorgrav
Julian Elischer <[EMAIL PROTECTED]> writes: > Marcel Moolenaar wrote: > > BTW: Do we have handy functions for use in the remote debugger, such > > as show_proc, show_vm or whatever, that dump important information > > in a readable form? > Matt has a cool set of macros as does Grog. I have a coup

Re: Linuxulator: possible Giant pushdown victim

2001-09-07 Thread Julian Elischer
Marcel Moolenaar wrote: > > BTW: Do we have handy functions for use in the remote debugger, such > as show_proc, show_vm or whatever, that dump important information > in a readable form? Matt has a cool set of macros as does Grog. -- ++ __ _ __ |

Re: Linuxulator: possible Giant pushdown victim

2001-09-07 Thread Marcel Moolenaar
On Thu, Sep 06, 2001 at 11:55:19AM -0700, John Baldwin wrote: > > > Note that 3 of these are runnable (stat of 2 == SRUN). In top, see if they are > chewing up lots of time. Top doesn't update after the first mozilla process has started. Its trace is: mi_switch() cv_timedwait_sig() select() s

Re: Linuxulator: possible Giant pushdown victim

2001-09-06 Thread John Baldwin
On 06-Sep-01 Marcel Moolenaar wrote: > On Wed, Sep 05, 2001 at 02:47:28PM -0700, John Baldwin wrote: >> >> Yes, you can trace indiviudal processes though, using 'trace ', and I'm >> more curious about the traces of the Mozilla processes. > > Ok, here it is: > > db> ps > pid proc addr

Re: Linuxulator: possible Giant pushdown victim

2001-09-05 Thread Marcel Moolenaar
On Wed, Sep 05, 2001 at 02:47:28PM -0700, John Baldwin wrote: > > Yes, you can trace indiviudal processes though, using 'trace ', and I'm > more curious about the traces of the Mozilla processes. Ok, here it is: db> ps pid proc addruid ppid pgrp flag stat wmesg wchan cmd 52

Re: Linuxulator: possible Giant pushdown victim

2001-09-05 Thread John Baldwin
On 05-Sep-01 Marcel Moolenaar wrote: > On Wed, Sep 05, 2001 at 11:04:04AM -0700, John Baldwin wrote: >> >> On 05-Sep-01 Marcel Moolenaar wrote: >> > Hi, >> > >> > I get consistent locks when trying to run Mozilla for Linux (RH 7.1). >> > >> > Breaking into the debugger, I see it hangs in fork_

Re: Linuxulator: possible Giant pushdown victim

2001-09-05 Thread Marcel Moolenaar
On Wed, Sep 05, 2001 at 11:04:04AM -0700, John Baldwin wrote: > > On 05-Sep-01 Marcel Moolenaar wrote: > > Hi, > > > > I get consistent locks when trying to run Mozilla for Linux (RH 7.1). > > > > Breaking into the debugger, I see it hangs in fork_exit()+180. This > > is should be the PROC_LOCK

RE: Linuxulator: possible Giant pushdown victim

2001-09-05 Thread John Baldwin
On 05-Sep-01 Marcel Moolenaar wrote: > Hi, > > I get consistent locks when trying to run Mozilla for Linux (RH 7.1). > > Breaking into the debugger, I see it hangs in fork_exit()+180. This > is should be the PROC_LOCK(p) in the source file (kern_fork.c). Can you do 'show locks ' where is the

Linuxulator: possible Giant pushdown victim

2001-09-05 Thread Marcel Moolenaar
Hi, I get consistent locks when trying to run Mozilla for Linux (RH 7.1). Breaking into the debugger, I see it hangs in fork_exit()+180. This is should be the PROC_LOCK(p) in the source file (kern_fork.c). Since a deadlock in this place should be seen for FreeBSD binaries as well and since that