Quoting Jason Wessel <[email protected]>:
>>>> kgdb8250=ttyS0,115200 kgdbcon kgdbwait
[snip]
>>> not take any arguments.
>>>
>>
>> Trying this with your 2.6.27 kernel and I'm not getting any
>> printk's through gdb. Note again that I'm just using the
>> standard F10 gdb 6.8. What version of gdb are you using?
>> Do you have anything special in your gdbinit? Or anything special
>> to do the "console/gdb split"? But it's definitely not working for
>> me.
>>
>>
>
> Nothing special here. I erased my .gdbinit file because it was only
> setting some extra breakpoints.
>
> I do make sure not to set the console= to anything when I am using the
> connected debugger as the console device. There are probably a great
> deal of configuration possibility that could cause something or other
> not to work.
>
> I guess I would ask the question if gdb is connecting at all? The other
> possibility is that your kernel is crashing before console init, which
> is the first point you would see any messages anyway.
Yes, gdb is connecting. I get:
(gdb) target remote /dev/pts/17
Remote debugging using /dev/pts/17
kgdb_register_io_module (new_kgdb_io_ops=0xc074ff08) at kernel/kgdb.c:1804
1804 wmb(); /* Sync point after breakpoint */
(gdb) c
Continuing.
> The pxe kernel params I was using are:
>
> ip=dhcp root=/dev/nfs nfsroot=10.0.1.2:/space/exp/x86 rw
> kgdb8250=ttyS0,115200 kgdbcon kgdbwait
>
> So again there is nothing particularly special there. The test I ran
> was an ARCH=i386 smp config on a 2 processor target.
Also, the gdb Ctrl-C interrupt seems to work intermittently, and I seem
to have some problem typing the SysRq-G key combo. HOWEVER, when I
DID get it typed I did see this in the gdb output:
^C^CInterrupted while waiting for the program.
Give up (and stop debugging it)? (y or n) n
SysRq : SysRq : GDB
[New Thread -2]
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread -2]
sysrq_handle_gdb (key=103, tty=0xde338400) at kernel/kgdb.c:1804
1804 wmb(); /* Sync point after breakpoint */
It still seems strange, though -- if I boot up without my kernel
module in the initrd I still don't see anything printed to the
gdb screen like I'd expect, like device probes and such.
No, I don't have a console= setup.
Also, it doesn't look like the module autoload works for initrd
modules. Is that true? How can I teach gdb about the symbols in
a kernel module loaded in initrd?
Thanks for your help!! I very much appreciate it!
> Jason.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[email protected] PGP key available
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
