linux-kernel - Re: [git pull] kgdb-light -v10

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Feb 2008 07:59:02 -0600
From:	Jason Wessel <jason.wessel@...driver.com>
To:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [git pull] kgdb-light -v10

Domenico Andreoli wrote:
> Hi,
>
> On Tue, Feb 12, 2008 at 12:27:47PM +0100, Ingo Molnar wrote:
>   
>> this is kgdb-light, version -v10 (against Linus-latest), and can be 
>> pulled from:
>>
>>    git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-kgdb.git
>>
>> shortlog, diffstat and full patch can be found further below.
>>     
>
>   I am just trying to play with this, I am not able to make it work.
> Assume I am able with git, I use it every day on my software, then I
> am correctly tracking and building your branch on git.kernel.org.
>
> My config has both KGDB and KGDB_SERIAL_CONSOLE. kernel command line
> has kgdbwait kgdboc=ttyS0,115200. linux console is not on serial but if
> do not enable KGDB_SERIAL_CONSOLE I am then unable to hit SysRq+g. If
> instead I use linux serial console, gdb messes with getty and things
> quickly get worse.
>
> 1. at boot, kernel waits for a gdb connection
> 2. gdb connection is established from another box
> 3. gdb breaks in
> 4. hit continue at gdb prompt
> 5. target box returns to life. everything looks ok (it is 2.6.25-rc1!)
> 6. SysRq+h on the target correctly shows the help on the console
> 7. SysRq+g on the target, it prints "SysRq : GDB" and hangs forever
> 8. gdb on the host does not break in
>
> is really that simple, am i overlooking anything? thank you.
>
> regards,
> Domenico
>
>   
I doubt the .config you posted was the one you used, because there were
no KGDB options specified at all.

If you want to be using your vga device as the console that is ok. You
can still activate the sysrq with running the command: echo g >
/proc/sysrq-trigger

You might consider doing "set debug remote 1" in the gdb session if you
want to see what is going on. After the continue, the next time you
break in with the debugger it should send $T.........etc which is a stop
packet.

Jason.
--
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/