Author Topic: Debugging with gdb and bare metal target, prevent SE issuing a reset?  (Read 284 times)

rowbearto

  • Senior Community Member
  • Posts: 1768
  • Hero Points: 119
Re: Debugging with gdb and bare metal target, prevent SE issuing a reset?
« Reply #15 on: September 17, 2020, 12:51:41 am »
When I look at the implementation of debug_send_command(), at the end of this function I see:

Code: [Select]
   // display the result
   _message_box(reply:+errmsg,command);

Could you add an optional input parameter to debug_send_command() to allow to bypass displaying this message box?

Also for the debug_remote() function, I think it could be possible to provide all the parameters of the dialog box, as well as not show the dialog box by filling in the "attach_info" parameter. I performed a "say()" in my local copy of this function after the call to show() and I now see how I would format "attach_info" to have all the required parameters. This would be very useful, then my macro can read the IP address/port from a file that my gdb script generator creates, and I can also provide the executable there. It would really help my automation. Is this feasible?

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1371
  • Hero Points: 127
Re: Debugging with gdb and bare metal target, prevent SE issuing a reset?
« Reply #16 on: September 17, 2020, 01:52:12 pm »
I'll take a look at adding a quiet option to debug_send_command this morning.

For debug remote, I attached a small example of building the attach info for gdb debug_remote and calling debug_remote with it.
« Last Edit: September 17, 2020, 01:54:55 pm by patrick »

rowbearto

  • Senior Community Member
  • Posts: 1768
  • Hero Points: 119
Re: Debugging with gdb and bare metal target, prevent SE issuing a reset?
« Reply #17 on: September 17, 2020, 02:48:29 pm »
Thanks Patrick. I think adding a quiet option to debug_send_command() will be very easy for you to do.

I'll follow your example for building the attach info for debug_remote().

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1371
  • Hero Points: 127
Re: Debugging with gdb and bare metal target, prevent SE issuing a reset?
« Reply #18 on: September 17, 2020, 08:35:39 pm »
The quiet flag for debug_send_command() will be in the next beta.

rowbearto

  • Senior Community Member
  • Posts: 1768
  • Hero Points: 119
Re: Debugging with gdb and bare metal target, prevent SE issuing a reset?
« Reply #19 on: September 17, 2020, 08:37:27 pm »
Thanks Patrick!

rowbearto

  • Senior Community Member
  • Posts: 1768
  • Hero Points: 119
Hi Patrick:

Could you also add the quiet mode for debug_send_command() to the next v24 hotfix?

Thanks!

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1371
  • Hero Points: 127
It will be in the next hotfix.

rowbearto

  • Senior Community Member
  • Posts: 1768
  • Hero Points: 119
Excellent! Thank you! Then my developers who are still using v24 can use my debug macros.