|
From: Christian P. <tr...@ge...> - 2005-08-12 07:12:24
|
hi, I'm having a rather odd problem; My daemon is loading modules as specified = in=20 a config file (think of apache modules e.g.); Well, when it comes to an end, and all modules have safely to be unloaded I= =20 get *strange strange* results, that is, the order on how I do unload them=20 *seems* important - or else the daemon raises SEGV when accessing some=20 certain memory and V reports "Invalid read of size 8"; Unfortunately, this "Invalid read" doesn't help me, especially, when only a= =20 stupid dlclose() being commented out can fix this; maybe the daemon is still accessing memory that *was* part of the dlopen()e= d=20 module - can that be true? Is there a way to verify that? And, is VG in general having an eye on misusage of dlopen/dlclose/related=20 functions? Many thanks, Christian Parpart. =2D-=20 09:07:22 up 141 days, 22:15, 0 users, load average: 0.82, 0.96, 1.05 |