Hi,
I am trying to simulate a benchmark developed using OpenCV 3.1 in
Syscall emulation mode.
OpenCV uses libpthread due to the use of locks, so I have to use
"m5threads" istead "libpthread" because Syscall emulatio mode can't
emulate the libpthread calls.
I can't use Full System mode because I am using gem5 with Aladdin, and
Aladdin doesn't support Full System mode.
Using "m5threads" instead of "libpthread" produces a deadlock when I try
to read an image with the OpenCV function "imread(path-to-the image)".
Compiling in DEBUG mode I obtain the next trace before the deadlock:
pthread_mutex_lock: start
pthread_mutex_lock: 11462
pthread_mutex_lock: start
pthread_mutex_lock: 11462
The process is calling 2 consecutive times to the mutex_lock function.
I'm thinking that the driver should be able to access the lock, but it
is not capable or is calling another function that is not the
"m5threads" "unlock" function, but I really do not know what's going on
and how can I fix it.
Thank you very much.
Best regards,
Alberto Alvarez.
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
