problem with remote target settings, insight 6.1

problem with remote target settings, insight 6.1

[Alexander Neundorf]

Hi, 
 
it seems insight 6.1, compiled from sources, has the following problem: 
In the dialog File -> Target Settings there are combo boxes Target, Baud 
Rate and Port. If I select another target, e.g. Remote/Serial, the Baud 
Rate is automatically set to the value I selected the last time (115200). 
If I then try to upload a file, it fails, it can't connect. 
If I set the Baud Rate manually from 115200 to something else and back to 
115200 it works. 
So it seems that when filling the baud rate automatically into the 
combobox when selecting another target, that in this case the baudrate is 
not "applied" to gdb. 
 
The code is in gdb/gdbtk/library/targetselection.itb, probably 
TargetSelection::change_target, but I'm no tcl expert, so I have some 
problems understanding this code. 
 
Bye 
Alex 
 
 

-- 
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info

Re: problem with remote target settings, insight 6.1

[Martin M. Hunt]

On Wed, 2004-06-16 at 00:18, Alexander Neundorf wrote:
> Hi, 
>  
> it seems insight 6.1, compiled from sources, has the following problem: 
> In the dialog File -> Target Settings there are combo boxes Target, Baud 
> Rate and Port. If I select another target, e.g. Remote/Serial, the Baud 
> Rate is automatically set to the value I selected the last time (115200). 
> If I then try to upload a file, it fails, it can't connect. 
> If I set the Baud Rate manually from 115200 to something else and back to 
> 115200 it works. 
> So it seems that when filling the baud rate automatically into the 
> combobox when selecting another target, that in this case the baudrate is 
> not "applied" to gdb. 

Please try the following patch and let me know if it fixes your
problems.

Index: interface.tcl
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/interface.tcl,v
retrieving revision 1.49
diff -u -r1.49 interface.tcl
--- interface.tcl       5 Apr 2004 20:36:42 -0000       1.49
+++ interface.tcl       16 Jun 2004 17:59:35 -0000
@@ -119,6 +119,7 @@
     set current_args [gdb_get_inferior_args]
     set current_dir $gdb_current_directory
     Session::notice_file_change
+    set_baud
     if {[string length $current_args] > 0} {
       gdb_set_inferior_args $current_args
       gdb_cmd "cd $current_dir"

-- 
Martin M. Hunt <hunt@redhat.com>
Red Hat Inc.

Re: problem with remote target settings, insight 6.1

[Alexander Neundorf]

> On Wed, 2004-06-16 at 00:18, Alexander Neundorf wrote: 
> > Rate is automatically set to the value I selected the last time 
> (115200).  
> > If I then try to upload a file, it fails, it can't connect.  
> > If I set the Baud Rate manually from 115200 to something else and back 
> > to 115200 it works.  
> > So it seems that when filling the baud rate automatically into the  
> > combobox when selecting another target, that in this case the baudrate 
> > is not "applied" to gdb.  
>  
> Please try the following patch and let me know if it fixes your 
> problems. 
 
Yes, works, 
thank you very much :-) 
 
Bye 
Alex 
  

-- 
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info

Re: problem with remote target settings, insight 6.1

[Bernhard Walle]

Hello,

Alexander Neundorf wrote:
>  
> it seems insight 6.1, compiled from sources, has the following problem: 
> In the dialog File -> Target Settings there are combo boxes Target, Baud 
> Rate and Port. If I select another target, e.g. Remote/Serial, the Baud 
> Rate is automatically set to the value I selected the last time (115200). 
> If I then try to upload a file, it fails, it can't connect. 

I have a similar problem which is not fixed with this patch. To reproduce:

  1. Delete the [session] and [load] part of ~/.gdbtkinit
  2. Start Insight
  3. Target Settings: Select a remote target which has default setting
     9600 which is ok.
  4. Run: Connect fails. The settings dialog is displayed which shows
     38400 as baudrate.

If you explicitely click on 9600 in step 3), it works. Is it possible to 
fix this bug, too.


Regards,
Bernhard