* set debug remote 1 @ 2004-11-30 13:00 Ilko Iliev 2004-11-30 17:41 ` Keith Seitz 0 siblings, 1 reply; 4+ messages in thread From: Ilko Iliev @ 2004-11-30 13:00 UTC (permalink / raw) To: insight Hi, I have try to debug remote connection with: set debug remote 1 from the insight console window and it dosn't work. It doesn't print debug info neither in insight console window nor in xterm console. But iin gdb it works, in insight v5.3 too. Is there a new option for debugging of remote connection? my platform: RedHat 9/ KDE insight snapshot from today target: arm-elf regards ilko iliev ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: set debug remote 1 2004-11-30 13:00 set debug remote 1 Ilko Iliev @ 2004-11-30 17:41 ` Keith Seitz 2004-12-01 9:06 ` Ilko Iliev 0 siblings, 1 reply; 4+ messages in thread From: Keith Seitz @ 2004-11-30 17:41 UTC (permalink / raw) To: Ilko Iliev; +Cc: insight On Tue, 2004-11-30 at 04:59, Ilko Iliev wrote: > Hi, > I have try to debug remote connection with: > set debug remote 1 > from the insight console window and it dosn't work. > It doesn't print debug info neither in insight console window nor in > xterm console. I hate to say stuff like this, but... It works for me. From the insight console (snapshot of cvs today): (gdb) tar sim Connected to the simulator. (gdb) load Loading section .text, size 0x9210 vma 0x8000 Loading section .rodata, size 0x314 vma 0x11210 Loading section .data, size 0x864 vma 0x11624 Loading section .ctors, size 0x8 vma 0x11e88 Loading section .dtors, size 0x8 vma 0x11e90 Start address 0x8000 Transfer rate: 322752 bits in <1 sec. (gdb) b main Breakpoint 3 at 0x80fc: file pi.c, line 25. (gdb) set debug remote 1 (gdb) r Starting program: /home/keiths/pi/pi-print.arm-elf gdbsim_create_inferior: exec_file "/home/keiths/pi/pi-print.arm-elf", args "" gdbsim_kill gdbsim_fetch_register: 13 0x800 gdbsim_xfer_inferior_memory: myaddr 0x0x9a90e50, memaddr 0x8d54, len 4, write 0 0xe59f2064 gdbsim_xfer_inferior_memory: myaddr 0x0x83534d0, memaddr 0x8d54, len 4, write 1 0xe7ffdefe gdbsim_xfer_inferior_memory: myaddr 0x0x9a28b98, memaddr 0x80fc, len 4, write 0 0xe3a03000 gdbsim_xfer_inferior_memory: myaddr 0x0x83534d0, memaddr 0x80fc, len 4, write 1 0xe7ffdefe gdbsim_fetch_register: 15 0x8000 gdbsim_resume: step 0, signal 0 gdbsim_wait gdbsim_fetch_register: 15 0x80fc gdbsim_fetch_register: 13 0x1fffd8 gdbsim_xfer_inferior_memory: myaddr 0x0x9a90e50, memaddr 0x8d54, len 4, write 1 0xe59f2064 gdbsim_xfer_inferior_memory: myaddr 0x0x9a28b98, memaddr 0x80fc, len 4, write 1 0xe3a03000 Breakpoint 3, main (argc=gdbsim_fetch_register: 11 0x1ffff8 gdbsim_xfer_inferior_memory: myaddr 0x0x9ab5b30, memaddr 0x1fffe4, len 4, write 0 0x1 1, argv=gdbsim_xfer_inferior_memory: myaddr 0x0x9a98ba0, memaddr 0x1fffe0, len 4, write 0 0x1ffffc 0x1ffffc) at pi.c:25 Are you using "set debug remote" or "set remotedebug"/"set remote debug" which are deprecated? Keith ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: set debug remote 1 2004-11-30 17:41 ` Keith Seitz @ 2004-12-01 9:06 ` Ilko Iliev 2004-12-01 18:04 ` Keith Seitz 0 siblings, 1 reply; 4+ messages in thread From: Ilko Iliev @ 2004-12-01 9:06 UTC (permalink / raw) To: Keith Seitz; +Cc: insight Hi, I use the set debug remote 1 and the variable remote_debug in remote.c is 1. The debugging the conection with the sim target works (like your exmple), but with real remote target don't work. The difference is that remote.c print to the gdb_stdlog (fprintf(gdb_stdlog, ....)) but remote-sim.c print to the gdb_stdout (printf_filtered ). It seems that the setting of gdb_stdlog is not correct. regards ilko Keith Seitz wrote: >On Tue, 2004-11-30 at 04:59, Ilko Iliev wrote: > > >>Hi, >>I have try to debug remote connection with: >>set debug remote 1 >>from the insight console window and it dosn't work. >>It doesn't print debug info neither in insight console window nor in >>xterm console. >> >> > >I hate to say stuff like this, but... It works for me. From the insight >console (snapshot of cvs today): > >(gdb) tar sim >Connected to the simulator. > >(gdb) load >Loading section .text, size 0x9210 vma 0x8000 >Loading section .rodata, size 0x314 vma 0x11210 >Loading section .data, size 0x864 vma 0x11624 >Loading section .ctors, size 0x8 vma 0x11e88 >Loading section .dtors, size 0x8 vma 0x11e90 >Start address 0x8000 >Transfer rate: 322752 bits in <1 sec. > >(gdb) b main >Breakpoint 3 at 0x80fc: file pi.c, line 25. > >(gdb) set debug remote 1 >(gdb) r >Starting program: /home/keiths/pi/pi-print.arm-elf >gdbsim_create_inferior: exec_file "/home/keiths/pi/pi-print.arm-elf", >args "" >gdbsim_kill >gdbsim_fetch_register: 13 0x800 >gdbsim_xfer_inferior_memory: myaddr 0x0x9a90e50, memaddr 0x8d54, len 4, >write 0 > 0xe59f2064 >gdbsim_xfer_inferior_memory: myaddr 0x0x83534d0, memaddr 0x8d54, len 4, >write 1 > 0xe7ffdefe >gdbsim_xfer_inferior_memory: myaddr 0x0x9a28b98, memaddr 0x80fc, len 4, >write 0 > 0xe3a03000 >gdbsim_xfer_inferior_memory: myaddr 0x0x83534d0, memaddr 0x80fc, len 4, >write 1 > 0xe7ffdefe >gdbsim_fetch_register: 15 0x8000 >gdbsim_resume: step 0, signal 0 >gdbsim_wait >gdbsim_fetch_register: 15 0x80fc >gdbsim_fetch_register: 13 0x1fffd8 >gdbsim_xfer_inferior_memory: myaddr 0x0x9a90e50, memaddr 0x8d54, len 4, >write 1 > 0xe59f2064 >gdbsim_xfer_inferior_memory: myaddr 0x0x9a28b98, memaddr 0x80fc, len 4, >write 1 > 0xe3a03000 > >Breakpoint 3, main (argc=gdbsim_fetch_register: 11 0x1ffff8 >gdbsim_xfer_inferior_memory: myaddr 0x0x9ab5b30, memaddr 0x1fffe4, len >4, write 0 > 0x1 >1, argv=gdbsim_xfer_inferior_memory: myaddr 0x0x9a98ba0, memaddr >0x1fffe0, len 4, write 0 > 0x1ffffc >0x1ffffc) at pi.c:25 > >Are you using "set debug remote" or "set remotedebug"/"set remote debug" >which are deprecated? > >Keith > > ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: set debug remote 1 2004-12-01 9:06 ` Ilko Iliev @ 2004-12-01 18:04 ` Keith Seitz 0 siblings, 0 replies; 4+ messages in thread From: Keith Seitz @ 2004-12-01 18:04 UTC (permalink / raw) To: Ilko Iliev; +Cc: insight On Wed, 2004-12-01 at 01:05, Ilko Iliev wrote: > I use the set debug remote 1 and the variable remote_debug in remote.c is 1. > The debugging the conection with the sim target works (like your > exmple), but with real remote target don't work. > The difference is that remote.c print to the gdb_stdlog > (fprintf(gdb_stdlog, ....)) but remote-sim.c print to the gdb_stdout > (printf_filtered ). > It seems that the setting of gdb_stdlog is not correct. Ah, okay, that makes sense. I know we have some special handling for all the gdb_* file "descriptors". I presume that gdb_stdlog is not handled by us, though. You've got two options: hack remote.c in your copy to send output to gdb_stdout or hack at insight and teach it out to display stdlog. Hmm... I see in gdbtk/generic/gdbtk-hooks.c that gdbtk_fputs already knows about stdlog. It calls gdb_tcl_fputs_log, which will send the output to the console as long as it is open. Is ::gdbtk_state(console) set when you open the console window? It is for me, but then that doesn't explain why you're not seeing the output from stdlog. If you put a debug statement in gdb_tcl_fputs_log, does it ever get there? Keith ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-12-01 18:04 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2004-11-30 13:00 set debug remote 1 Ilko Iliev 2004-11-30 17:41 ` Keith Seitz 2004-12-01 9:06 ` Ilko Iliev 2004-12-01 18:04 ` Keith Seitz
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).