debug versions of DLLs

debug versions of DLLs

[Maureen Byrne]

Hi All,
I down loaded the source from ftp://sourceware.cygnus.com/pub/pthreads-win32/
to try to build the debug version of the pthread.dll. But, there are no
__declspec(dllexport) in any of the header files...with the result on
pthread.lib was generated.

How do I generate the debug pthread.dll and pthread.lib ?

thanks,
maureen

Re: debug versions of DLLs

[Ross Johnson]

On Tue, 15 Jun 1999, Maureen Byrne wrote:

> Hi All,
> I down loaded the source from ftp://sourceware.cygnus.com/pub/pthreads-win32/
> to try to build the debug version of the pthread.dll. But, there are no
> __declspec(dllexport) in any of the header files...with the result on
> pthread.lib was generated.
> 
> How do I generate the debug pthread.dll and pthread.lib ?

I'm probably going to show my complete ignorance here so please feel
free to correct me. I'm not a regular Windows application developer
and am really guessing here, but, does __declspec(dllexport) do the
same job as the .def file? If so, Maureen, did you build the library
with the /def:pthread.def option?

To build the dll and lib files I use the buildlib.bat file included
with the source code. The /Zi debugging info option is already
included when I build the library for upload but I've never used the
debugger so can't say that it should work. The reason I haven't used
it is because I build the library over a text-only telnet connection
to a remote NT box.

I suspect this is not very helpful, so if someone else can provide
some clarity please do.

Ross

> 
> thanks,
> maureen
> 
> 

+----------------------+---+
| Ross Johnson         |   | E-Mail: rpj@ise.canberra.edu.au
| Info Sciences and Eng|___|
| University of Canberra   | FAX:    +61 6 2015227
| PO Box 1                 |
| Belconnen  ACT    2616   | WWW:    http://willow.canberra.edu.au/~rpj/
| AUSTRALIA                |
+--------------------------+

Re: debug versions of DLLs

[Kevin D. Clark]

Ross Johnson writes:

> I'm probably going to show my complete ignorance here so please feel
> free to correct me. I'm not a regular Windows application developer
> and am really guessing here, but, does __declspec(dllexport) do the
> same job as the .def file? If so, Maureen, did you build the library
> with the /def:pthread.def option?

This tells me that I'm even more ignorant than Ross.  (-:

> To build the dll and lib files I use the buildlib.bat file included
> with the source code. The /Zi debugging info option is already
> included when I build the library for upload but I've never used the
> debugger so can't say that it should work. The reason I haven't used
> it is because I build the library over a text-only telnet connection
> to a remote NT box.
> 
> I suspect this is not very helpful, so if someone else can provide
> some clarity please do.

I'm using the buildlib.bat too.  I was able to invoke the MS VC++ 6.x
debugger when my program died, and I was able to step into the
pthreads code when I wanted to.

(the reason why the program died was entirely my fault, not the fault
of this excellent pthreads implementation)

--kevin
-- 
Kevin D. Clark (kclark@cabletron.com)          Give me a decent UNIX
Cabletron Systems, Inc.                      and I can move the world
Durham, N.H. (USA)

Re: debug versions of DLLs

[Maureen Byrne]

Kevin & Ross,

Thanks a million for your answers.....obviously I proved to be the ignorant
one here, I generated the MSDEV project from scratch (without looking at
the *.bat files !!..not very smart)...but, I was nearly there, all I needed
to do extra was include the pthread.def file along with all the *.c files
and MSDEV takes care of it.

So thanks guys for pointing me towards to pthread.def file :-)

Hopefully now,I won't get the crash in my debug exe, because I linked with
a release version of pthread.dll

thanks again,

Maureen 

>Ross Johnson writes:
>
>> I'm probably going to show my complete ignorance here so please feel
>> free to correct me. I'm not a regular Windows application developer
>> and am really guessing here, but, does __declspec(dllexport) do the
>> same job as the .def file? If so, Maureen, did you build the library
>> with the /def:pthread.def option?
>
>This tells me that I'm even more ignorant than Ross.  (-:
>
>> To build the dll and lib files I use the buildlib.bat file included
>> with the source code. The /Zi debugging info option is already
>> included when I build the library for upload but I've never used the
>> debugger so can't say that it should work. The reason I haven't used
>> it is because I build the library over a text-only telnet connection
>> to a remote NT box.
>> 
>> I suspect this is not very helpful, so if someone else can provide
>> some clarity please do.
>
>I'm using the buildlib.bat too.  I was able to invoke the MS VC++ 6.x
>debugger when my program died, and I was able to step into the
>pthreads code when I wanted to.
>
>(the reason why the program died was entirely my fault, not the fault
>of this excellent pthreads implementation)
>
>--kevin
>-- 
>Kevin D. Clark (kclark@cabletron.com)          Give me a decent UNIX
>Cabletron Systems, Inc.                      and I can move the world
>Durham, N.H. (USA)