|
Re: kgdb on arm for 2.6: msg#00129linux.kernel.debugging.kgdb.bugs
George Anzinger wrote: For this you will need an ARM dude. That is not me... Is there an ARM kgdb expert on this list? I'm running into another problem with the new kgdb. Since this platform doesn't have an MMU I can debug both the kernel and user applications in the same gdb/kgdb debug session. This mostly works but breakpoints dont seem to work right. After I load the symbols for the user program I can set a breakpoint and run to it but then if I try to continue to run to another one, I always just wake up at the same breakpoint. Gdb reports an error about not being writable (see below). However, if I manually clear the breakpoint then hit continue, it will run to the next breakpoint (at which time the process repeats). Any idea why it can't automatically clear user-space breakpoints in the current kgdb? This works OK with the old kgdb and 2.4. Here's an example of the breakpoint not clearing right when I try to continue: Breakpoint 3, main (argc=1, argv=0x1fe3ffc0) at simpleinit.c:407 (gdb) cont Sending packet: $m1fe011bc,4#20...Ack Packet received: fedeffe7 Sending packet: $Z0,1fe011c0,4#37...Ack Packet received: OK Sending packet: $Hc1#dc...Ack Packet received: OK Sending packet: $c#63...Ack Packet received: T05thread:0000000000000001; Sending packet: $g#67...Ack Packet received: 00000000c8fde31f0000000000000000d0fee31f0000000000000000c0ffe31f0100000000000000c4f1e01f90ffe31f30fde31f74fee31f9886e01fbc11e01f00000000000000000000000000000000000000000000000000000000000000000000000010000020 Sending packet: $z0,1fe011c0,4#57...Ack Packet received: OK Sending packet: $m1fe011bc,4#20...Ack Packet received: fedeffe7 Sending packet: $Hc0#db...Ack Packet received: OK Sending packet: $c#63...Ack Packet received: T05thread:0000000000000001; Sending packet: $g#67...Ack Packet received: 00000000c8fde31f0000000000000000d0fee31f0000000000000000c0ffe31f0100000000000000c4f1e01f90ffe31f30fde31f74fee31f9886e01fbc11e01f00000000000000000000000000000000000000000000000000000000000000000000000010000020 Sending packet: $m1fe011bc,4#20...Ack Packet received: fedeffe7 Sending packet: $m1fe011bc,4#20...Ack Packet received: fedeffe7 Sending packet: $m1fe0103c,4#f0...Ack Packet received: f0412de9 Sending packet: $m1fe01040,4#be...Ack Packet received: fedeffe7 Sending packet: $m1fe01044,4#c2...Ack Packet received: e8d04de2 Sending packet: $m1fe01048,4#c6...Ack Packet received: 003096e5 Sending packet: $m1fe0104c,4#f1...Ack Packet received: 0080a0e1 Sending packet: $m1fe01050,4#bf...Ack Packet received: 000053e3 Sending packet: $m1fe01054,4#c3...Ack Packet received: 0170a0e1 Sending packet: $m1fe01058,4#c7...Ack Packet received: 0700000a Sending packet: $z0,1fe01040,4#27...Ack Packet received: E02 Cannot remove breakpoints because program is no longer writable. It might be running in another process. Further execution is probably impossible. Breakpoint 3, main (argc=1, argv=0x1fe3ffc0) at simpleinit.c:407 Also, if I try to run "next" while in a user-space program it usually just hangs the gdb session. This also worked correctly on the old kgdb and 2.4. Are these problems unique to me or is this new arm kgdb code just not being used widely? Thanks in advance, Lance ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: kgdb on arm for 2.6: 00129, George Anzinger |
|---|---|
| Next by Date: | h/w watchpoint pointer initialization patch.: 00129, Jitendra Pawar |
| Previous by Thread: | Re: kgdb on arm for 2.6i: 00129, George Anzinger |
| Next by Thread: | Re: kgdb on arm for 2.6: 00129, George Anzinger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |