linux-kernel - Re: kgdb errors with serial console

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-id: <C07919DD-643F-4645-A261-91FB8F381A2C@mac.com>
Date:	Sat, 09 Oct 2010 04:05:16 +0400
From:	Elvis Dowson <elvis.dowson@....com>
To:	Jason Wessel <jason.wessel@...driver.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux OMAP Mailing List <linux-omap@...r.kernel.org>
Subject: Re: kgdb errors with serial console

Hi Jason,
                   Perhaps the debugger is timing out because it doesn't get a break point to debug a specific event? 

Could you tell me the order in which I should try it? 

I think earlier on, when I used the kgdbwait bootarg, it ran and initialized eclipse debugger. Then when I entered the 

echo g > /proc/sysrq-trigger

it just activated the debugger correctly because the kgdb_breakpoint method was called in file kgdb.c

So, what should I do to test this? Do I write a small file, and add a call to kgdb_breakpoint in that example file, and then when I execute it, the debugger would get activated? 

Is there any other test that I can run, without writing my own example ?

Best regards,

Elvis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/