On Wed, Aug 10, 2011 at 7:28 PM, Helmut Hartl wrote:
> Am 10.08.11 16:56, schrieb Max Vlasov:
>
> 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
Am 10.08.11 16:56, schrieb Max Vlasov:
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
Max,
This works (for me)
1) Add a file like :
/
On Wed, Aug 10, 2011 at 6:20 PM, Jonas Maebe 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"
>>
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
On Wed, Aug 10, 2011 at 5:43 PM, Jonas Maebe wrote:
>
>
> I tried adding
>> --eval-command="handle SIGUSR1 nostop noprint pass"
>>
>
> While this won't solve your problem, as Michael said you should not use
> SIGUSR1 because it's probably already used by the system.
>
>
SIG35 behaves the same. St
On 10 Aug 2011, at 15:32, Max Vlasov wrote:
On Wed, Aug 10, 2011 at 4:34 PM, Jonas Maebe >wrote:
Can I somehow tell it to
ignore some, for example 'SIG35'? I tried to add it to Language
exceptions
ignore list as 'External: SIG35', 'External:SIG35' (without
space), SIG35.
Nothing helped.
On Wed, Aug 10, 2011 at 4:34 PM, Jonas Maebe wrote:
>
>
> Can I somehow tell it to
>> ignore some, for example 'SIG35'? I tried to add it to Language exceptions
>> ignore list as 'External: SIG35', 'External:SIG35' (without space), SIG35.
>> Nothing helped.
>>
>
> handle SIG35 nostop noprint pass
On 10 Aug 2011, at 14:24, Max Vlasov wrote:
On Wed, Aug 10, 2011 at 1:18 PM, Max Vlasov
wrote:
I tried to implement linux timer with timer_create and signals, but
an
exception always fired (External:SIGUSR1).
Hmm, it seems that it's not a 'wrong' exception, I executed the same
program
On Wed, Aug 10, 2011 at 1:18 PM, Max Vlasov wrote:
> Hi,
>
> I tried to implement linux timer with timer_create and signals, but an
> exception always fired (External:SIGUSR1).
>
Hmm, it seems that it's not a 'wrong' exception, I executed the same program
from console and it worked. So there's
