| red floyd <no.spam.here@its.invalid>: Jul 21 06:02PM -0700 On 7/21/2021 10:31 AM, Paulo da Silva wrote: > the debugging should proceed normally. > A very weird solution, however!! > Regards You could put "break main" in your .gdbinit file. Then it will break at main automatically. |
| Paulo da Silva <p_d_a_s_i_l_v_a_ns@nonetnoaddress.pt>: Jul 22 05:16PM +0100 Às 02:02 de 22/07/21, red floyd escreveu: >>>> Às 01:55 de 20/07/21, red floyd escreveu: >>>>> On 7/19/2021 12:15 PM, Paulo da Silva wrote: >>>>>> Hi! ... >> Regards > You could put "break main" in your .gdbinit file. Then it will break at > main automatically. You are missing the point that the program is launched outside eclipse/gdb. So it runs ... Later we attach to it from eclipse. So, we need to force it "to wait" for us to attach to it. Besides, the eclipse issues a call to gdb using -nx. This means no .gdbinit is executed. Regards |
| red floyd <no.spam.here@its.invalid>: Jul 22 10:38AM -0700 On 7/22/2021 9:16 AM, Paulo da Silva wrote: > Besides, the eclipse issues a call to gdb using -nx. This means no > .gdbinit is executed. > Regards Couldn't you run under gdb in the terminal, break at main, and then detach once you've attached Eclipse? |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment