Hello,
Now with the latest improvments, I am able to build openocd again under cygwin.
But it looks like the gdb_port command insist on using 3333 as port, I
have it set to 2332 in my config file but openocd is still listening
on 3333.
If I try to change it from the telnet interface :
Open On-Chip Debugger
> gdb_port
3333
> gdb_port 2332
> gdb_port
3333
>
It doesn't want to ...
The debug log shows :
Info : 125 6125 server.c:79 add_connection(): accepting 'telnet'
connection from 0
Debug: 127 14359 command.c:68 script_debug(): command - gdb_port
Debug: 128 14359 command.c:77 script_debug(): gdb_port - argv[0]=ocd_gdb_port
User : 129 14359 command.c:396 command_print(): 3333
Debug: 131 23906 command.c:68 script_debug(): command - gdb_port
Debug: 132 23906 command.c:77 script_debug(): gdb_port - argv[0]=ocd_gdb_port
Debug: 133 23906 command.c:77 script_debug(): gdb_port - argv[1]=2332
Debug: 135 28328 command.c:68 script_debug(): command - gdb_port
Debug: 136 28328 command.c:77 script_debug(): gdb_port - argv[0]=ocd_gdb_port
User : 137 28328 command.c:396 command_print(): 3333
This code in gdb_server.c looks suspicious to me :
/* daemon configuration command gdb_port */
int handle_gdb_port_command(struct command_context_s *cmd_ctx, char
*cmd, char **args, int argc)
{
if (argc == 0)
{
command_print(cmd_ctx, "%d", gdb_port);
return ERROR_OK;
}
/* only if the port wasn't overwritten by cmdline */
if (gdb_port == 0)
gdb_port = strtoul(args[0], NULL, 0);
return ERROR_OK;
}
gdb_port is initialized to 3333 so it is unlikely to be equal to 0 ...
Regards
Francois
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
