Em 10/7/2012 23:19, waldo kitty escreveu:
On 7/10/2012 07:00, Luiz Americo Pereira Camara wrote:
With the old behavior, in an system with a system code page <> UTF8,
if i try to
show the parsed value of "\u4E01" in e.g. a LCL app will get garbage.
I would expect to work correctly in any enviro
Hello,
I wrote a handler to intercept the SIGTERM signal and execute some
processing before terminating the program.
It works fine.
But when i add the cthreads unit in the uses clause, the application seems
to do a shutdown after the end of the handler function, and the processing
before terminati
Did you try a simpler handler ?
Maybe just set a variable and exit. Just a kind of test case...
2012/7/11 jmbottu :
> Hello,
> I wrote a handler to intercept the SIGTERM signal and execute some
> processing before terminating the program.
> It works fine.
>
> But when i add the cthreads unit in t
jmbottu wrote:
Hello,
I wrote a handler to intercept the SIGTERM signal and execute some
processing before terminating the program.
It works fine.
But when i add the cthreads unit in the uses clause, the application seems
to do a shutdown after the end of the handler function, and the processing
On 7/11/2012 01:36, Reinier Olislagers wrote:
On 11-7-2012 4:19, waldo kitty wrote:
On 7/10/2012 07:00, Luiz Americo Pereira Camara wrote:
With the old behavior, in an system with a system code page<> UTF8,
if i try to
show the parsed value of "\u4E01" in e.g. a LCL app will get garbage.
I wo
In the handler i just set a variable.
I have solved my problem in setting my own handler later in the application,
after having started the threads.
It seems there is another handler which is setting when i use threads and
that starts a shutdown of the application when receiving SIGTERM.
Thank you
