> the arguments are printed if they're available. it's just that > on amd64 (which i'm assuming Paul is using) doesn't give you > those since they're passed in registers and aren't stored or > kept anywhere. i386 shows them.. (or at least, their current > value on their stack location): > > crash> bt/t 1 > trace: pid 1 lid 1 at 0xdc9ebe2c > sleepq_block(0,1,c0b9b25c,c0d6d2f0,0,c453ad40,0,ffffffff,c4c97d80,dc9ebec0) > at sleepq_block+0x8f > cv_wait_sig(c4c97d98,c4520f00,c4d7ef00,c4d7ec30,dc9ebeb0,0,0,c4d7ec30,0,ffffffff) > at cv_wait_sig+0x101 > do_sys_wait(dc9ebedc,dc9ebed8,0,0,0,ffffffff,c4c97d80,2,dc9ebf00,40) at > do_sys_wait+0x1c2 > sys___wait450(c4d80d40,dc9ebf68,dc9ebf60,2,bbba3000,c0d6cdb4,dc9ebf68,1c1,0,0) > at sys___wait450+0x37 > syscall() at syscall+0x8a > --- syscall (number 449) --- > bba76937:
Hmmm, I´ve never seen crash or ddb print any arguments. Either way, this feature is certainly architecture-dependant, since they all have their own calling convention(s).
