From 3de213cc00f2889d2cd693968fd38c10a7f5def1 Mon Sep 17 00:00:00 2001 From: Robert Watson Date: Tue, 25 Dec 2007 17:52:02 +0000 Subject: Add a new 'why' argument to kdb_enter(), and a set of constants to use for that argument. This will allow DDB to detect the broad category of reason why the debugger has been entered, which it can use for the purposes of deciding which DDB script to run. Assign approximate why values to all current consumers of the kdb_enter() interface. --- sys/arm/at91/uart_dev_at91usart.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sys/arm/at91/uart_dev_at91usart.c') diff --git a/sys/arm/at91/uart_dev_at91usart.c b/sys/arm/at91/uart_dev_at91usart.c index 88625899f197..f87dcaaaab64 100644 --- a/sys/arm/at91/uart_dev_at91usart.c +++ b/sys/arm/at91/uart_dev_at91usart.c @@ -508,7 +508,7 @@ at91_rx_put(struct uart_softc *sc, int key) #if defined(KDB) && defined(ALT_BREAK_TO_DEBUGGER) if (sc->sc_sysdev != NULL && sc->sc_sysdev->type == UART_DEV_CONSOLE) { if (kdb_alt_break(key, &sc->sc_altbrk)) - kdb_enter("Break sequence to console"); + kdb_enter(KDB_WHY_BREAK, "Break sequence to console"); } #endif uart_rx_put(sc, key); -- cgit v1.2.3