|
| LibC & fork( ) |
 |
Tue, 05 Sep 2006 17:11:34 GMT |
I have an NLM and a NLM library loaded in a protected address
space called TEST. When my NLM is contacted from a remote machine, it
issues a fork( ) and proceeds with establishing communication.
Once the fork( ) is issued, the NLM loads fine into a new protected
address space called TEST(1). But some functions are not available. They
appear as part of the NLM when a "? <function_name>" is
performed in the
debugger. But when an attempt is made to access it programmatically, it
corrupts the address space. And when I try to unassemble this function in
the debugger, I receive a message saying that it "exceeds valid memory
limit". Note that if I change to the TEST address space (the parent), I
can unassemble it without issue.
I believe the problem is fork( ) related.
Thanks,
-Carey
|
| Post Reply
|
| Re: LibC & fork( ) |
 |
Tue, 19 Sep 2006 04:55:43 GMT |
You're best to post to the libc newsgroup.
--
Peter
|
| Post Reply
|
|
|
|
|
|
|
|
|
|