Re: The continued remote debugging saga...

2004-09-01 Thread soralx
> |> This works SOMETIMES > boot() which just takes an int of boot flags (which was the 0 that I > shoved into eax for RB_AUTBOOT). are you shure that you don't need to push the 0x0 into stack (`MOV ESP,0x0`)? Timestamp: 0x41367B68 [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2 ___

Re: The continued remote debugging saga...

2004-09-01 Thread Doug Rabson
On Wednesday 01 September 2004 18:15, John-Mark Gurney wrote: > Rob Deker wrote this message on Wed, Sep 01, 2004 at 11:38 -0400: > > So, after a lot of work and help from folks here, I've gotten > > remote gdb functioning (thanks again to those who helped. In the > > end there was a bad cable in t

Re: The continued remote debugging saga...

2004-09-01 Thread Rob Deker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John-Mark Gurney wrote: | If you are able to be at a command line, you could try: sysctl | debug.kdb.current=ddb | If I was able to get to a command line, I'd just use shutdown :) Could I build up the appropriate struct in gdb and use the sysctl() syste

Re: The continued remote debugging saga...

2004-09-01 Thread John-Mark Gurney
Rob Deker wrote this message on Wed, Sep 01, 2004 at 11:38 -0400: > So, after a lot of work and help from folks here, I've gotten remote > gdb functioning (thanks again to those who helped. In the end there > was a bad cable in the mix that was the final screw-up). Now I have > one other question/p

The continued remote debugging saga...

2004-09-01 Thread Rob Deker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, after a lot of work and help from folks here, I've gotten remote gdb functioning (thanks again to those who helped. In the end there was a bad cable in the mix that was the final screw-up). Now I have one other question/problem. I've got cuaa0 on th