This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re[2]: problems with dlopen

Hallo Cliff,

Friday, December 07, 2001, 5:26:33 PM, you wrote:

> If your suspicion is correct, then simply moving "state = 1" to before
> the call of dlopen should do the trick, i.e.:

>                 case 0:
>                         state = 1;
>                         handle = dlopen("cygwin1.dll", RTLD_NOW);
>                         orig_malloc = (void *(*)(size_t)) dlsym (handle, "malloc");
>                         /*fall through*/
> -- Cliff

You're right, that was an error.
Unfortunately it doesn't solve the problem. Again, the same error
while executing 'dlopen'.
Now i think the problem ist not a recursive call of 'malloc' (for the
moment), because i should be able to detect such recursive behaviour
by setting a breakpoint in my own malloc... Hmm, and there is no
recursion before the segfault.
Sure, after the current problem is removed, dlopen may call malloc to
get some memory. For that purpose i'll try to implement an additional
state which then use a static memory array to provide the requested

Again, any suggestions?

Best regards,

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]