On Wed, Aug 10, 2011 at 6:20 PM, Jonas Maebe <jonas.ma...@elis.ugent.be>wrote:
> > On 10 Aug 2011, at 16:12, Max Vlasov wrote: > > SIG35 behaves the same. Strangely, I looked in system monitor for gdb >> command-line, it looked ok >> >> /usr/bin/gdb -silent -i mi -nx --eval-command="handle SIG35 nostop noprint >> pass" >> >> but after the same Initialization output dialog it still stops with >> "External:SIG35" >> Actually looking at the -i mi options, I see it's machine interface with >> all >> these escaping sequences, so probably lazarus didn't undestand something, >> but it's strange it still stops >> > > Most commands are different in the machine interface. "handle SIG35 nostop > noprint pass" is probably only valid when using the default interface. I > don't know what the MI equivalent is. > > > If I invoke the same full line in the terminal the output $ /usr/bin/gdb -silent -i mi -nx --eval-command="handle SIG35 nostop noprint pass" =thread-group-added,id="i1" ~"Signal Stop\tPrint\tPass to program\tDescription\n" ~"SIG35 No\tNo\tYes\t\tReal-time event 35\n" So looks like (Stop = No) gdb got the command. Jonas, I see that you probably have your reasons not to use gdb inside the lazarus, but it was quite decent for me until this strange unavoidable moment :) It still is, hope I will find a work around Max
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
