Quoting Jason Wessel <[email protected]>:
>>> I'm currently booting with:
>>>
>>> kgdb8250=ttyS0,115200 kgdbwait kgdbcon=ttyS0,115200
>>>
>>> What am I missing to get the printk output to kgdb like I used to?
>>>
>>>
>>>
>> I had a 2.6.30-rc3 already built so I tried it out on that.
>>
>> I used:
>>
>> kgdb8250=ttyS0,115200 kgdbcon kgdbwait
>>
>> And it did seem to work ok, but I hit an extra break point that I didn't
>> set, so I was going to take a look at that.
>>
>>
> As far as I can tell, it is working fine. The extra breakpoint happen
> to be a result of a .gdbinit file I didn't notice.
>
> When using the early debug functionality the "kgdbcon" parameter does
> 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.
> Cheers,
> 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
