Am Montag, 29. Mai 2006 17:20 schrieb George Anzinger: > I take it that you are saying that > a) you have the kgdb console option on,
Yup! > b) that kgdb is not intercepting the watchdog event. Second yup - as long as syslog was running on the target machine. > Are you also saying that turning off the syslog daemon fixes this or just > that this allows you to (or inspired you to) look in the syslog on the > target machine? After stopping the syslog daemon on the target machine, the stacktrace showed up on the remote machine. I never saw the stack on the target machine - maybe because the machine froze before printing out the stacktrace... > As I understand it, kgdb should break, automatically, when ever a watchdog > trips. This should happen before the watchdog event gets to the stack > trace code. In your case, this seems not to be the case. All I can say is that as long as syslog was runing no the target machine, nothing happend on the remote machine when the freeze occured. > A breakpoint in the stack dump code would have worked, but, as I said > above, should not have been needed. Maybe, but we suddenly realitzed our problem when we saw the stack dump. so there was no need for breakpoints after the first dump.
pgpxfrsQUVNVR.pgp
Description: PGP signature
