[Note TOP posting is not the preferred way on this group. I can't be bothered
to reformat it all - so look back on the thread for the full context.]
Sudhahar wrote:
>>Thanks Cliff/Dave. I could not find the code where the dll data/bss
>>segments address are updated in cygwin. But in the fork code we are
>>doing a copy for all linked and loaded dlls data/bss segments by
>>giving the address as
>>for (dll *d = dlls.istart (DLL_LINK); d; d = dlls.inext ())
>> {
>> debug_printf ("copying data/bss of a linked dll");
>> if (!fork_copy (pi, "linked dll data/bss", d->p.data_start,
>> d->p.data_end,
>> d->p.bss_start, d->p.bss_end,
>> NULL))
>> goto cleanup;
>> }
>>and
>> for (dll *d = dlls.istart (DLL_LOAD); d; d = dlls.inext ())
>> {
>> debug_printf ("copying data/bss for a loaded dll");
>> if (!fork_copy (pi, "loaded dll data/bss", d->p.data_start,
>> d->p.data_end,
>> d->p.bss_start,
>> d->p.bss_end,
>> NULL))
>> goto cleanup;
>> }
>>
>>And also please let me know if there exist any document which gives
>>some idea about this.
Brian Dessent wrote:
> There is no code to update them. As the other replies have already
> said, they act like labels and are established by the linker via the
> linker script. When the program runs, they contain the address, that's
> it. The values in the per_process struct are filled in by the startup
> code in _cygwin_crt0_common.cc.
>
> The 'ld' manual, section 3.5.3.
Sudahar wrote:
> Brian,
> From your comments I understand that dll data/bss segment
> address is same as that of process data/bss segment
> address(data_start, data_end, bss_start and bss_end) when the process
> is loaded. Is that right
[I am not 100% confident I'm right her, but...] Each cygwin dll has its own
separate data and bss segments, and the linker generates _data_start__ etc
symbols for the dll when the dll is linked, just as it does for a normal
.exe. The dll initialisation code, which you will find in
winsup/cygwin/dcrt0.cc, copies the addresses of these symbols into
the dll structures (d->...) which is used during fork as you quoted above.
Hope that helps.
-- Cliff
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
