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: Fri, 15 Jun 2012 08:25:53 +0200

I think it may help to forward all RTIA output messages to a certain log file. I tried the following:

// redirect std::out and std::cerr to file
                       
// get process id
DWORD pid = GetCurrentProcessId();
stringstream outfilename;
outfilename << "d:\\rtia_" << pid << ".log";
       
ofstream logfile;
logfile.open (outfilename.str().c_str());

cout.rdbuf(logfile.rdbuf());
cerr.rdbuf(logfile.rdbuf());

But unfortunately nothing seems to be dropped to this file.
May be its because the PrettyDebug code has the following static var: std::ostream PrettyDebug::_defaultOutputStream(std::cerr.rdbuf());
Is it somehow already possible to redirect the output?

Thanks,
Michael




Von:        Michael Raab <address@hidden>
An:        CERTI development discussions <address@hidden>
Datum:        14.06.2012 16:48
Betreff:        Re: [certi-dev] CERTI deadlock
Gesendet von:        address@hidden




Hi Eric,

I'm still facing this problem. :-(

Could you please tell me, which component decides whether a requested time advancement can be granted?


Thanks,

Michael





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:        
06.06.2012 15:06
Betreff:        
Re: [certi-dev] CERTI deadlock
Gesendet von:        
address@hidden




2012/6/6 Michael Raab <address@hidden>:
> OK,
>
> the execution using the recent CERTI version and
> CERTI_USE_NULL_PRIME_MESSAGE_PROTOCOL works and is much faster.

When using NER (Next Event Request) CERTI_USE_NULL_PRIME_MESSAGE_PROTOCOL
may give you huge boost in performance because it lowers the number
of NULL message to a quasi minimal value...

> The deadlock appears much later but it still appears :-(
>
> I set RTIA_CONSOLE_SHOW to true but still no console pops up.

Did you recompile from scratch and relink your app?

> I would like to try the default billard example.
> What do I need to do to get that running?

You don't need anything special to have the billard running.
On Windows you don't have the graphical version "billard"
but you should have the text-only "billard-nogui" version.

in order to run billard you should

1) run
   rtig
2) run
   billard-nogui -n "Name1" -fTest -FTest.fed -t10

will make one billard running fro 10 seconds.

you can [theoretically] launch as many billard as you want.



--
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
--
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]