Problem with Remote/Serial in Insight

Problem with Remote/Serial in Insight

[Bernhard Walle]

Hello,

we're using Stubs and try to connect with the "Remote/Serial" target in 
Insight. It works, the code jumps to the breakpoint but after that the 
target settings dialog is displayed again. If you click "ok", it fetches 
some memory and displays it again. That gives an endless loop.

If we use "target remote /dev/ttyS14" on commandline, there's no such 
problem. Does anybody have an idea where the problem could be?


Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Bernhard Walle wrote:
> Does anybody have an idea where the problem could be?

Does anybody know how to find it out with less efforts?


Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Fri, 2004-12-10 at 15:26, Bernhard Walle wrote:
> we're using Stubs and try to connect with the "Remote/Serial" target in 
> Insight. It works, the code jumps to the breakpoint but after that the 
> target settings dialog is displayed again. If you click "ok", it fetches 
> some memory and displays it again. That gives an endless loop.

Can you describe the whole situation, step by step? That will help me
isolate where the problem might be occuring. Also, if you open the debug
window before attaching, send the output. Maybe there is something in
there that might help.

FWIW, I find the best way to start debugging on a remote is to simply
press the Run button. Insight will do whatever it takes to get a session
going.

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Hello,

Keith Seitz wrote:
> On Fri, 2004-12-10 at 15:26, Bernhard Walle wrote:
> 
>>we're using Stubs and try to connect with the "Remote/Serial" target in 
>>Insight. It works, the code jumps to the breakpoint but after that the 
>>target settings dialog is displayed again. If you click "ok", it fetches 
>>some memory and displays it again. That gives an endless loop.
> 
> Can you describe the whole situation, step by step? That will help me
> isolate where the problem might be occuring. Also, if you open the debug
> window before attaching, send the output. Maybe there is something in
> there that might help.

  1. I download the program with the stubs to the target manually with
     minicom and start it on the target. The stub is responding if I
     press ENTER. I close minicom.

  2. I start Insight with "insight program"

  3. I adjust the tharget settings to "Remote/Serial", 9600 (confirmed by
     a click, you know the bug), my serial interface (/dev/ttyS14),
     [X] Set breakpoint at main, [X] Attach to target, [ ] Download
     program, (X) Run program. I click ok.

  4. I press the RUN button.

  5. It jumps to a breakpoint (it shows the BREAKPOINT() macro, and not
     to main(), well, that might be a bug in the stups) and displays the
     target settings dialog again. Clicking OK fetches something from the
     target and displays that dialog again and again. I simply cannot
     work. With GDB (not insight) I can do next, continue, etc.

I hope it's clear what I do. I don't know which debug window you mean, 
can you give me the point?

The problem appears on Insight on Windows XP and on Linux. We use the 
Insight 6.1 which a few additions (additional remote targets but that's 
unrelated to _the_ remote target) and a patch from the CVS which fixes a 
bug. I can send you the whole diff between 6.1 and our Insight if you 
really think that that's the problem, but I don't think.


Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Tue, 2004-12-14 at 02:51, Bernhard Walle wrote:
>   3. I adjust the tharget settings to "Remote/Serial", 9600 (confirmed by
>      a click, you know the bug), my serial interface (/dev/ttyS14),
>      [X] Set breakpoint at main, [X] Attach to target, [ ] Download
>      program, (X) Run program. I click ok.

I presume you mean "continue", not "run"...

> I hope it's clear what I do. I don't know which debug window you mean, 
> can you give me the point?

Yes, that is exactly what I was after... And exactly what baffles me the
most! I can hardly imagine how this is happening, but I have a
suspicion.

To open the debug window, enter "tk ManagedWin::open DebugWin" in the
console window when insight starts up. Copy the output to a file and
send that.

> I can send you the whole diff between 6.1 and our Insight if you 
> really think that that's the problem, but I don't think.

That won't be necessary unless I cannot figure the whole thing out...
Hopefully you've given me enough to go on.

With any luck, I can get gdbserver to demonstrate the same problem.

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Keith Seitz wrote:
> On Tue, 2004-12-14 at 02:51, Bernhard Walle wrote:
> 
>>  3. I adjust the tharget settings to "Remote/Serial", 9600 (confirmed by
>>     a click, you know the bug), my serial interface (/dev/ttyS14),
>>     [X] Set breakpoint at main, [X] Attach to target, [ ] Download
>>     program, (X) Run program. I click ok.
> 
> 
> I presume you mean "continue", not "run"...

No, I mean "Run Method: (X) Run program". If I choose "Continue from 
Last Stop", nothing works. I simple want Insight to do the same as GDB 
if I type "target remote /dev/ttyS14".

>>I hope it's clear what I do. I don't know which debug window you mean, 
>>can you give me the point?
> 
> 
> Yes, that is exactly what I was after... And exactly what baffles me the
> most! I can hardly imagine how this is happening, but I have a
> suspicion.
> 
> To open the debug window, enter "tk ManagedWin::open DebugWin" in the
> console window when insight starts up. Copy the output to a file and
> send that.

It's simply not possible. Because the dialog is opened, this debug 
window is not accessible and because I cannot close that dialog ...

Well, I made a screenshot of the last part, but I cannot do more. :(
http://www.bwalle.de/temp/insight-debug.png.



Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Tue, 2004-12-14 at 10:23, Bernhard Walle wrote:
> > I presume you mean "continue", not "run"...
> 
> No, I mean "Run Method: (X) Run program". If I choose "Continue from 
> Last Stop", nothing works. I simple want Insight to do the same as GDB 
> if I type "target remote /dev/ttyS14".

Unless gdb has changed substantially since the last time I used a remote
target, one never uses "run" on a remote target. It doesn't make any
sense: there's no process to create. [It's a subtle difference, but
that's what gdb does.]

When you download a program to the target, gdb sets the PC to the start
address. "Continuing" the program will start its execution.

> It's simply not possible. Because the dialog is opened, this debug 
> window is not accessible and because I cannot close that dialog ...

Set GDBTK_DEBUG to non-zero and GDBTK_DEBUGFILE to a filename in your
environment before running. This will save all the debugging information
into $GDBTK_DEBUGFILE.

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

Keith Seitz wrote:
> On Tue, 2004-12-14 at 10:23, Bernhard Walle wrote:
> 
>>>I presume you mean "continue", not "run"...
>>
>>No, I mean "Run Method: (X) Run program". If I choose "Continue from 
>>Last Stop", nothing works. I simple want Insight to do the same as GDB 
>>if I type "target remote /dev/ttyS14".
> 
> 
> Unless gdb has changed substantially since the last time I used a remote
> target, one never uses "run" on a remote target. It doesn't make any
> sense: there's no process to create. [It's a subtle difference, but
> that's what gdb does.]
> 
> When you download a program to the target, gdb sets the PC to the start
> address. "Continuing" the program will start its execution.

Well, you're right the "process" is still running and it sounds logic. 
But simply it doesn't work without run, Insight is hanging. Insight 
should simply do the same as "target remote" does.

>>It's simply not possible. Because the dialog is opened, this debug 
>>window is not accessible and because I cannot close that dialog ...
> 
> Set GDBTK_DEBUG to non-zero and GDBTK_DEBUGFILE to a filename in your
> environment before running. This will save all the debugging information
> into $GDBTK_DEBUGFILE.

Thanks, output attached.


Regards,
Bernhard

[-- Attachment #2: debug.txt --]
[-- Type: text/plain, Size: 14819 bytes --]

I global pref_set_defaults {}
I global pref_set_colors {}
I global pref_load_default {loading default colors}
I global gdbtk_locate_main {}
I global gdbtk_clear_file {}
I global gdbtk_locate_main {}
I ManagedWin find SrcWin
I global gdbtk_locate_main {}
I SrcWin point_to_main {could not find main}
I ManagedWin startup {Got active list {ManagedWin::open Console} {ManagedWin::open SrcWin}}
I ManagedWin _open {Console }
I ManagedWin _create {win=console args=}
I EmbeddedWin constructor {}
I Console constructor {}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.console0.console"}
I ManagedWin _open {SrcWin }
I ManagedWin _create {win=srcwin args=}
I GDBWin constructor {}
I TopLevelWin constructor .srcwin0.srcwin
I SrcWin constructor {}
I SrcBar create_plugin_menu {No plugins configured, go remove the PlugIn menu...}
I SrcBar _set_runstop normal
I SrcBar enable_ui {2 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I GDBToolBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I SrcBar {} {configuring runstop normal}
I SrcBar _set_runstop normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I GDBWin constructor {}
I ManagedWin find SrcWin
I Session notice_file_change {noticed file change event for /home/bwalle/devel/remdbg/stubs/neu/test.out}
I Session notice_file_change {reloading session for /home/bwalle/devel/remdbg/stubs/neu/test.out}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin"}
I Session notice_file_change {Restoring Target: remote}
I Session notice_file_change {Restoring Target_Cmd: remote /dev/ttyS14 }
I GDBEventHandler GDBEventHandler::dispatch {posting event "set_variable" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I SrcTextWin set_variable {Set hook got called with remotebaud 9600}
I GDBEventHandler GDBEventHandler::dispatch {posting event "set_variable" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "set_variable" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I SrcBar set_variable {Got remotebaud = 9600}
I GDBEventHandler GDBEventHandler::dispatch {posting event "set_variable" to "::.srcwin0.srcwin"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "set_variable" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I SrcTextWin set_variable {Set hook got called with remotebaud 9600}
I GDBEventHandler GDBEventHandler::dispatch {posting event "set_variable" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "set_variable" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I SrcBar set_variable {Got remotebaud = 9600}
I GDBEventHandler GDBEventHandler::dispatch {posting event "set_variable" to "::.srcwin0.srcwin"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "update" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "update" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "update" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "update" to "::.srcwin0.srcwin"}
I SrcWin choose_and_update {chose window ::.srcwin0.srcwin}
I SrcWin _update {loc={} {} {} 0 0x00000000 0x00000000 {}}
I SrcWin location {running=0 tag= linespec={} {} {} 0 0x00000000 0x00000000 {}}
I SrcWin location {not running: name= funcname= line=0}
I global gdbtk_locate_main {}
I SrcWin location {new linespec=test.c main /home/bwalle/devel/remdbg/stubs/neu/test.c 17 0x00010fc0 0x00000000 {}}
I SrcTextWin _mtime_changed {no mtime. resetting to zero}
I SrcTextWin LoadFile {/home/bwalle/devel/remdbg/stubs/neu/test.c  SOURCE}
I SrcTextWin LoadFromCache {LoadFromCache t /home/bwalle/devel/remdbg/stubs/neu/test.c S}
I SrcTextWin LoadFromCache name=/home/bwalle/devel/remdbg/stubs/neu/test.c
I SrcTextWin LoadFromCache pane=pane1
I SrcTextWin LoadFile {READING /home/bwalle/devel/remdbg/stubs/neu/test.c}
I SrcWin _set_state {gdb_running l=0 d=0 r=0}
I global gdbtk_attach_remote Attaching....
I ManagedWin find SrcWin
I SrcBar enable_ui {2 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I GDBToolBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I global set_target {CONNECTING TO TARGET: remote /dev/ttyS14 }
I GDBEventHandler GDBEventHandler::dispatch {posting event "busy" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "busy" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "busy" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I SrcBar enable_ui {0 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Control disabled  Other disabled  Trace disabled  Attach disabled  Detach disabled}
I GDBToolBar set_class_state {Enable list is: Control disabled  Other disabled  Trace disabled  Attach disabled  Detach disabled}
I GDBEventHandler GDBEventHandler::dispatch {posting event "busy" to "::.srcwin0.srcwin"}
I combobox combobox::Configure newValue=disabled
I combobox combobox::Configure newValue=disabled
I combobox combobox::Configure newValue=disabled
I SrcBar {} {configuring runstop running}
I SrcBar _set_runstop running
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I SrcBar enable_ui {1 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Trace disabled  Control normal  Other normal  Attach disabled  Detach normal }
I GDBToolBar set_class_state {Enable list is: Trace disabled  Control normal  Other normal  Attach disabled  Detach normal }
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin"}
I SrcBar {} {configuring runstop normal}
I SrcBar _set_runstop normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I SrcBar enable_ui {2 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I GDBToolBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I SrcWin _set_state {gdb_running l=0 d=0 r=1}
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I SrcWin _set_state {gdb_loaded l=0 d=0 r=1}
I global gdbtk_locate_main {}
I global run_executable {Setting new BP at main}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "breakpoint" to "::.srcwin0.srcwin"}
I global run_executable {Runnning target...}
I GDBEventHandler GDBEventHandler::dispatch {posting event "busy" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "busy" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "busy" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I SrcBar enable_ui {0 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Control disabled  Other disabled  Trace disabled  Attach disabled  Detach disabled}
I GDBToolBar set_class_state {Enable list is: Control disabled  Other disabled  Trace disabled  Attach disabled  Detach disabled}
I GDBEventHandler GDBEventHandler::dispatch {posting event "busy" to "::.srcwin0.srcwin"}
I combobox combobox::Configure newValue=disabled
I combobox combobox::Configure newValue=disabled
I combobox combobox::Configure newValue=disabled
I SrcBar {} {configuring runstop running}
I SrcBar _set_runstop running
I SrcBar enable_ui {2 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I GDBToolBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I SrcWin _set_state {gdb_running l=0 d=0 r=0}
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I GDBEventHandler GDBEventHandler::dispatch {posting event "update" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "update" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "update" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "update" to "::.srcwin0.srcwin"}
I SrcWin choose_and_update {chose window ::.srcwin0.srcwin}
I SrcWin _update {loc=m68k-stub.c breakpoint /home/bwalle/devel/remdbg/stubs/neu/m68k-stub.c 1206 0x00010f74 0x00010f74 {}}
I SrcWin location {running=0 tag= linespec=m68k-stub.c breakpoint /home/bwalle/devel/remdbg/stubs/neu/m68k-stub.c 1206 0x00010f74 0x00010f74 {}}
I SrcWin location {not running: name=/home/bwalle/devel/remdbg/stubs/neu/m68k-stub.c funcname=breakpoint line=1206}
I SrcTextWin _mtime_changed {no mtime. resetting to zero}
I SrcTextWin LoadFile {/home/bwalle/devel/remdbg/stubs/neu/m68k-stub.c /home/bwalle/devel/remdbg/stubs/neu/test.c SOURCE}
I SrcTextWin LoadFromCache {LoadFromCache t /home/bwalle/devel/remdbg/stubs/neu/m68k-stub.c S}
I SrcTextWin LoadFromCache name=/home/bwalle/devel/remdbg/stubs/neu/m68k-stub.c
I SrcTextWin LoadFromCache pane=pane2
I SrcTextWin LoadFile {READING /home/bwalle/devel/remdbg/stubs/neu/m68k-stub.c}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I SrcBar enable_ui {1 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Trace disabled  Control normal  Other normal  Attach disabled  Detach normal }
I GDBToolBar set_class_state {Enable list is: Trace disabled  Control normal  Other normal  Attach disabled  Detach normal }
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin"}
I SrcBar {} {configuring runstop normal}
I SrcBar _set_runstop normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I SrcBar enable_ui {2 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I GDBToolBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
W global run_executable {msg=Don't know how to run.  Try "help target".
}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin.container.pane2.childsite.con"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.console0.console"}
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin.container.pane0.childsite.con"}
I SrcBar enable_ui {1 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Trace disabled  Control normal  Other normal  Attach disabled  Detach normal }
I GDBToolBar set_class_state {Enable list is: Trace disabled  Control normal  Other normal  Attach disabled  Detach normal }
I GDBEventHandler GDBEventHandler::dispatch {posting event "idle" to "::.srcwin0.srcwin"}
I SrcBar {} {configuring runstop normal}
I SrcBar _set_runstop normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I SrcBar enable_ui {2 - Browsing=0}
I GDBMenuBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I GDBToolBar set_class_state {Enable list is: Control disabled  Trace disabled  Other normal  Attach normal  Detach disabled }
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I ManagedWin _open {TargetSelection -exportcancel 1 -center -transient}
I ManagedWin _create {win=targetselection args=-exportcancel 1 -center -transient}
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I TargetSelection change_target remote
I combobox combobox::Configure newValue=normal
I combobox combobox::Configure newValue=normal
I ManagedWin find SrcWin
I ModalDialog post {POST ::.targetselection0.targetselection}
I SrcWin _exit {}
I ManagedWin find SrcWin
I SrcWin destructor {}
I TopLevelWin destructor {}
I global pref_save {pref_save /home/bwalle/.gdbtkinit}
I EmbeddedWin destructor {}

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Tue, 2004-12-14 at 10:40, Bernhard Walle wrote:
> > Set GDBTK_DEBUG to non-zero and GDBTK_DEBUGFILE to a filename in your
> > environment before running. This will save all the debugging information
> > into $GDBTK_DEBUGFILE.
> 
> Thanks, output attached.

There are some clues in the file. To clear up a few things, can you
please send me a complete command-line-only session of you connecting to
your stub and stopping in main()?

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Keith Seitz wrote:
> On Tue, 2004-12-14 at 10:40, Bernhard Walle wrote:
> 
>>>Set GDBTK_DEBUG to non-zero and GDBTK_DEBUGFILE to a filename in your
>>>environment before running. This will save all the debugging information
>>>into $GDBTK_DEBUGFILE.
>>
>>Thanks, output attached.
> 
> 
> There are some clues in the file. To clear up a few things, can you
> please send me a complete command-line-only session of you connecting to
> your stub and stopping in main()?

Don't know what you mean.

    (gdb) run
    Error: Don't know how to run.  Try "help target".

    (gdb) (gdb) target remote /dev/ttyS14
    Remote debugging using /dev/ttyS14
    0x00010f74 in breakpoint () at m68k-stub.c:1206

But Insight doesn't recognize this.


Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Tue, 2004-12-14 at 12:43, Bernhard Walle wrote:
> Don't know what you mean.
> 
>     (gdb) run
>     Error: Don't know how to run.  Try "help target".
> 
>     (gdb) (gdb) target remote /dev/ttyS14
>     Remote debugging using /dev/ttyS14
>     0x00010f74 in breakpoint () at m68k-stub.c:1206

You say you can get gdb to stop at a breakpoint in main. I would like to
see the whole process, from starting gdb up, attaching to the target and
stopping at the breakpoint in main().

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Keith Seitz wrote:
> On Tue, 2004-12-14 at 12:43, Bernhard Walle wrote:
> 
>>Don't know what you mean.
>>
>>    (gdb) run
>>    Error: Don't know how to run.  Try "help target".
>>
>>    (gdb) (gdb) target remote /dev/ttyS14
>>    Remote debugging using /dev/ttyS14
>>    0x00010f74 in breakpoint () at m68k-stub.c:1206
> 
> 
> You say you can get gdb to stop at a breakpoint in main. I would like to
> see the whole process, from starting gdb up, attaching to the target and
> stopping at the breakpoint in main().

Did I say this?

No, it doesn't stop in main(), it stops in breakpoint() which is called 
from main()


Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Tue, 2004-12-14 at 12:56, Bernhard Walle wrote:
> Did I say this?
> 
> No, it doesn't stop in main(), it stops in breakpoint() which is called 
> from main()

Sorry, my bad. Could you just please send a whole session using the
command line? I really need to see what your process is.

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Keith Seitz wrote:
> On Tue, 2004-12-14 at 12:56, Bernhard Walle wrote:
> 
>>Did I say this?
>>
>>No, it doesn't stop in main(), it stops in breakpoint() which is called 
>>from main()
> 
> 
> Sorry, my bad. Could you just please send a whole session using the
> command line? I really need to see what your process is.

I cannot reproduce the GUI problem with command line.

What do you mean with "whole session"? Just break main and target 
remote, or am I understanding wrong?


Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Tue, 2004-12-14 at 13:08, Bernhard Walle wrote:

> What do you mean with "whole session"? Just break main and target 
> remote, or am I understanding wrong?

I would like to see something like this but targeted for your stub:

$ ./gdb -q -nx
(gdb) file ~/pi/pi-print.arm-elf
Reading symbols from /home/keiths/pi/pi-print.arm-elf...done.
(gdb) b main
Breakpoint 1 at 0x80fc: file pi.c, line 25.
(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) r
Starting program: /home/keiths/pi/pi-print.arm-elf
 
Breakpoint 1, main (argc=1, argv=0x1ffffc) at pi.c:25
25            int i=0;
(gdb)

I would like to see the series of commands that you use to start your
debugging. There is a disconnect between the way you and your stub works
and the way Insight does. By understanding exactly how your target
starts, I can get a better understanding of what insight should be doing
in your case.

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Keith Seitz wrote:
> On Tue, 2004-12-14 at 13:08, Bernhard Walle wrote:
> 
> 
>>What do you mean with "whole session"? Just break main and target 
>>remote, or am I understanding wrong?
> 
> 
> I would like to see something like this but targeted for your stub:

Well, simply

[~/devel/remdbg/stubs/neu] $ m68k-elf-gdb
GNU gdb 6.1
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=m68k-elf".
(gdb) file test.out
Reading symbols from test.out...done.
(gdb) target remote /dev/ttyS14
Remote debugging using /dev/ttyS14
0x00010f74 in breakpoint () at m68k-stub.c:1206
1206             BREAKPOINT ();
(gdb)


I must download and start the program with minicom and the monitor 
program in the ROM of the target.

Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Tue, 2004-12-14 at 13:29, Bernhard Walle wrote:
> [~/devel/remdbg/stubs/neu] $ m68k-elf-gdb
> GNU gdb 6.1
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain 
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu --target=m68k-elf".
> (gdb) file test.out
> Reading symbols from test.out...done.
> (gdb) target remote /dev/ttyS14
> Remote debugging using /dev/ttyS14
> 0x00010f74 in breakpoint () at m68k-stub.c:1206
> 1206             BREAKPOINT ();
> (gdb)

Okay, so now what's the next step to start the stub executing?

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Keith Seitz wrote:
> On Tue, 2004-12-14 at 13:29, Bernhard Walle wrote:
> 
>>[~/devel/remdbg/stubs/neu] $ m68k-elf-gdb
>>GNU gdb 6.1
>>Copyright 2004 Free Software Foundation, Inc.
>>GDB is free software, covered by the GNU General Public License, and you are
>>welcome to change it and/or distribute copies of it under certain 
>>conditions.
>>Type "show copying" to see the conditions.
>>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>>This GDB was configured as "--host=i686-pc-linux-gnu --target=m68k-elf".
>>(gdb) file test.out
>>Reading symbols from test.out...done.
>>(gdb) target remote /dev/ttyS14
>>Remote debugging using /dev/ttyS14
>>0x00010f74 in breakpoint () at m68k-stub.c:1206
>>1206             BREAKPOINT ();
>>(gdb)
> 
> 
> Okay, so now what's the next step to start the stub executing?

Simply for example "break 23" and then "cont". I think that's the 
normale way stubs work.

Well, to say the truth, it doesn't work very well in the moment because 
the stubs don't work very well. But I didn't program/adapt the stubs, 
that was another person in my team and he's working on that. Sometimes 
it work, sometimes not. But with Insight, I always have this problem.

But if you think that the problem in Insight has something to do with a 
problem with the stubs, then please tell me!


Regards,
Bernhard

Re: Problem with Remote/Serial in Insight

[Keith Seitz]

On Wed, 2004-12-15 at 10:03, Bernhard Walle wrote:
> > Okay, so now what's the next step to start the stub executing?
> 
> Simply for example "break 23" and then "cont". I think that's the 
> normale way stubs work.

Aha! That's what I've been waiting to hear. Yes, that is exactly right:
the "normal" process for a stub is to set baud (if using serial),
attach, load (optional), and continue -- NOT run.

This is why I was so baffled when you said that your target preferences
had "attach" and "run" and not "attach" and "continue". In fact, the
reason the Target Settings dialog keeps reappearing is because of the
"Run" option set in your target settings. From the log you sent me:

I global gdbtk_attach_remote Attaching....
I global set_target {CONNECTING TO TARGET: remote /dev/ttyS14 }
I global run_executable {Setting new BP at main}
I global run_executable {Runnning target...}
W global run_executable {msg=Don't know how to run.  Try "help target".
}
I ManagedWin _open {TargetSelection -exportcancel 1 -center -transient}

From this, I conclude that it attached to the target (remote
/dev/ttyS14), set a break at main, and attempted to RUN the target
(i.e., gdb's "run" command). This elicited an error ('Don't know how to
run. Try "help target".'), which caused the target selection dialog to
open again.

If you are having other problems while specifying "continue", then
that's a different problem that we need to address.

Keith

Re: Problem with Remote/Serial in Insight

[Bernhard Walle]

Keith Seitz wrote:
> On Wed, 2004-12-15 at 10:03, Bernhard Walle wrote:
> 
>>>Okay, so now what's the next step to start the stub executing?
>>
>>Simply for example "break 23" and then "cont". I think that's the 
>>normale way stubs work.
> 
> Aha! That's what I've been waiting to hear. Yes, that is exactly right:
> the "normal" process for a stub is to set baud (if using serial),
> attach, load (optional), and continue -- NOT run.

Ok, thank you VERY much and SORRY, since it was my fault. If the stubs 
really work without problems in GDB, I can see if the "continue" works 
in Insight. If not, I come here again with a detailled error description 
(now I know much more about error trapping in Insight).


Regards,
Bernhard