certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] CERTI deadlock


From: Michael Raab
Subject: Re: [certi-dev] CERTI deadlock
Date: Tue, 26 Jun 2012 14:01:17 +0200

Hi Eric,

the file gets created with pid appended but RTIA still crashes... I have no clue why....
I've debugged into and it crashes in: _defaultOutputStream.rdbuf(fb);
The filebuf seems to be opened correctly, as fb->open(...) return something unequal NULL..

Michael


Mit freundlichen Grüßen,
Michael Raab


Dipl.-Inform. Michael Raab

Fraunhofer-Institut für Fabrikbetrieb und -automatisierung IFF
Virtuell Interaktives Training
Sandtorstr. 22, 39106 Magdeburg, Germany                
Telefon +49 (0) 391/ 40 90 122
Telefax +49 (0) 391/ 40 90 115
address@hidden
http://www.iff.fraunhofer.de oder http://www.vdtc.de



Von:        Eric Noulard <address@hidden>
An:        CERTI development discussions <address@hidden>
Datum:        21.06.2012 14:18
Betreff:        Re: [certi-dev] CERTI deadlock
Gesendet von:        address@hidden




2012/6/21 Eric Noulard <address@hidden>:
> 2012/6/21 Michael Raab <address@hidden>:
>> Hi Eric,
>>
>> it crashes at start up.  The log file was created but is empty....
>> I would guess it's some sort of concurrent file access problem as there are
>> N instances trying to write to the same log file...
>
> Yes right...windows is really picky about file sharing.
> I'll try to mangle the file using process Id...
>
> Sending one more message when it's done.

The specified filename should now be mangled with the process ID.
-<PID> is appended to the specified filename.

I just commited the change.

This should avoid concurrent access.

Beware of the size of those file.
Depending on how many pretty debug trace you enable
you can get as many as 1MB/s of trace.


--
Erk
Le gouvernement représentatif n'est pas la démocratie --
http://www.le-message.org

--
CERTI-Devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/certi-devel


reply via email to

[Prev in Thread] Current Thread [Next in Thread]