Hello list, I'm attempting to track a memory leak i'm experiencing with GHDL.
Context: - I'm using the VHPI interface in order to get and put signals. - I'm using POSIX shared memory and semaphores. I've fully tested my POSIX shm/sem code in separate client/server applications. There isn't any memleaks. However, running the code with GHDL clearly shows memleaks (non-scientifically shown by `top`). Running a long simulation with GHDL doesn't show any memleak. I'm requesting help in order to track this memleak issue. Please see valgrind report in attachment. -Pascal PS: Note that i still haven't resolved my POSIX sem_wait() issue... Reminder, sem_wait() doesn't work in GHDL, i've to use sem_trywait()! Can it be connected to the warning shown by valgrind: "Warning: client switching stacks? SP change: 0xBEC7B2AC --> 0x46EFF7C" -- Homepage (http://organact.mine.nu) Debian GNU/Linux (http://www.debian.org) LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)
ghdl_valgrind_report.log
Description: Binary data
_______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
