On Wed, Oct 17, 2001 at 09:28:42PM -0400, Roland McGrath wrote:
> I hope that stepping through the stubs added to your understanding
> of how RPC's are marshalled into Mach messages. But the upshot is
> that the io_map RPC is returning EOPNOTSUPP. (And the easy way to
> see that in the debugger
> ./main: error while loading shared libraries: ./main: failed to map segment from
>shared object: Error 1073741869
That value is EOPNOTSUPP (I used "p (error_t)1073741869" in gdb).
> > Also, show us objdump --private-headers of both executables.
This stuff is probably not actually relevant in
On Wed, Oct 17, 2001 at 04:11:00AM -0400, Roland McGrath wrote:
As before "./mutt" (the working one) is the one on top, and "./main"
(the not working one) is the one of bottom.
> See if you can get anything telling out of LD_DEBUG before you look too
> hard with gdb. LD_DEBUG=help .../ld.so --v
See if you can get anything telling out of LD_DEBUG before you look too
hard with gdb. LD_DEBUG=help .../ld.so --verify should show you the options.
Also, show us objdump --private-headers of both executables.
This is a good thing to always include when the dynamic linker is involved.
Try some
The symptom is that executables produced on my system show up as:
jbailey@hurd:~/test$ ldd main
not a dynamic executable
However, a few things suggest that it really is:
jbailey@hurd:~/test$ file main
main: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked (uses
sha
