* Re: Debugging the cygwin DLL
@ 1999-02-22 14:33 Earnie Boyd
1999-02-28 23:02 ` Earnie Boyd
0 siblings, 1 reply; 11+ messages in thread
From: Earnie Boyd @ 1999-02-22 14:33 UTC (permalink / raw)
To: Curtis Galloway, cygwin
---Curtis Galloway <curtis@pdi.com> wrote:
>
> Anyone have any hints for debugging the Cygwin dll? The messages I
found in
> the archive on the subject were pretty dated.
>
> Creating a static version of libcygwin.a seems to be the way to go.
If anyone
> has done this already in b20.1, I'd love to hear from them.
I've not heard of this but according to Geoff Noer in a personal note
to me it would be possible to create a static version of libcygwin.a
but that it would require quite a bit of work as it is currently setup
to create the dynamic library. I believe this to mean the working
internals as well.
==
- \\||//
-------------------o0O0--Earnie--0O0o-------------------
-- earnie_boyd@yahoo.com --
-- http://www.freeyellow.com/members5/gw32/index.html --
----------------------ooo0O--O0ooo----------------------
PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Debugging the cygwin DLL
1999-02-22 14:33 Debugging the cygwin DLL Earnie Boyd
@ 1999-02-28 23:02 ` Earnie Boyd
0 siblings, 0 replies; 11+ messages in thread
From: Earnie Boyd @ 1999-02-28 23:02 UTC (permalink / raw)
To: Curtis Galloway, cygwin
---Curtis Galloway <curtis@pdi.com> wrote:
>
> Anyone have any hints for debugging the Cygwin dll? The messages I
found in
> the archive on the subject were pretty dated.
>
> Creating a static version of libcygwin.a seems to be the way to go.
If anyone
> has done this already in b20.1, I'd love to hear from them.
I've not heard of this but according to Geoff Noer in a personal note
to me it would be possible to create a static version of libcygwin.a
but that it would require quite a bit of work as it is currently setup
to create the dynamic library. I believe this to mean the working
internals as well.
==
- \\||//
-------------------o0O0--Earnie--0O0o-------------------
-- earnie_boyd@yahoo.com --
-- http://www.freeyellow.com/members5/gw32/index.html --
----------------------ooo0O--O0ooo----------------------
PS: Newbie's, you should visit my page.
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Debugging the cygwin DLL
1999-02-22 15:06 ` Curtis Galloway
[not found] ` < 36D1E0A5.D4B841D2@pdi.com >
@ 1999-02-28 23:02 ` Curtis Galloway
1 sibling, 0 replies; 11+ messages in thread
From: Curtis Galloway @ 1999-02-28 23:02 UTC (permalink / raw)
To: DJ Delorie; +Cc: cygwin
DJ Delorie wrote:
>
> > Anyone have any hints for debugging the Cygwin dll? The messages I
> > found in the archive on the subject were pretty dated.
>
> You should be able to just use gdb to debug it, even as a dll. Have
> you tried? Hmmm, maybe it's one of those things that didn't make it
> into the last beta, or maybe it doesn't work as well as I think it
> does. If you did try, what happened?
Ah, indeed, if I
gdb cygwin1.dll
and then
gdb> exec-file myprogram.exe
I can debug functions within the cygwin DLL. Very nice.
Unfortunately, gdb's use of signals seems to interfere with debugging the
cygwin signal handling code. I think I'm stuck with using strace after all.
Thanks,
--Curtis
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Debugging the cygwin DLL
1999-02-22 15:36 ` DJ Delorie
@ 1999-02-28 23:02 ` DJ Delorie
1999-02-28 23:02 ` Christopher Faylor
1 sibling, 0 replies; 11+ messages in thread
From: DJ Delorie @ 1999-02-28 23:02 UTC (permalink / raw)
To: curtis; +Cc: cygwin
> Unfortunately, gdb's use of signals seems to interfere with
> debugging the cygwin signal handling code. I think I'm stuck with
> using strace after all.
Signals are just barely supported in gdb as is. Chris and I also use
strace to debug them.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Debugging the cygwin DLL
1999-02-22 15:36 ` DJ Delorie
1999-02-28 23:02 ` DJ Delorie
@ 1999-02-28 23:02 ` Christopher Faylor
1 sibling, 0 replies; 11+ messages in thread
From: Christopher Faylor @ 1999-02-28 23:02 UTC (permalink / raw)
To: DJ Delorie; +Cc: curtis, cygwin
On Mon, Feb 22, 1999 at 06:35:52PM -0500, DJ Delorie wrote:
>
>> Unfortunately, gdb's use of signals seems to interfere with
>> debugging the cygwin signal handling code. I think I'm stuck with
>> using strace after all.
>
>Signals are just barely supported in gdb as is. Chris and I also use
>strace to debug them.
Cygwin signals should be handled better in one of the recent gdb snapshots
if any adventurous soul would like to try to compile a new cygwin gdb.
The new snapshot should also allow some thread support as well as the
ability to attach to a running process using the *Win32* pid (not the
cygwin pid).
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Debugging the cygwin DLL
1999-02-22 14:02 Curtis Galloway
[not found] ` < 36D1D392.2FA663A3@pdi.com >
@ 1999-02-28 23:02 ` Curtis Galloway
1 sibling, 0 replies; 11+ messages in thread
From: Curtis Galloway @ 1999-02-28 23:02 UTC (permalink / raw)
To: cygwin
Anyone have any hints for debugging the Cygwin dll? The messages I found in
the archive on the subject were pretty dated.
Creating a static version of libcygwin.a seems to be the way to go. If anyone
has done this already in b20.1, I'd love to hear from them.
--Curtis
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Debugging the cygwin DLL
1999-02-22 14:12 ` DJ Delorie
1999-02-22 15:06 ` Curtis Galloway
@ 1999-02-28 23:02 ` DJ Delorie
1 sibling, 0 replies; 11+ messages in thread
From: DJ Delorie @ 1999-02-28 23:02 UTC (permalink / raw)
To: curtis; +Cc: cygwin
> Anyone have any hints for debugging the Cygwin dll? The messages I
> found in the archive on the subject were pretty dated.
You should be able to just use gdb to debug it, even as a dll. Have
you tried? Hmmm, maybe it's one of those things that didn't make it
into the last beta, or maybe it doesn't work as well as I think it
does. If you did try, what happened?
> Creating a static version of libcygwin.a seems to be the way to go.
> If anyone has done this already in b20.1, I'd love to hear from
> them.
It can be done, but it's not that easy. The big problem is that the
DLL has some initialization stuff that doesn't happen if you link it
statically, and it expects some things to be in the dll vs the exe,
like malloc, so you have to replace those as well.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Debugging the cygwin DLL
[not found] ` < 36D1E0A5.D4B841D2@pdi.com >
@ 1999-02-22 15:36 ` DJ Delorie
1999-02-28 23:02 ` DJ Delorie
1999-02-28 23:02 ` Christopher Faylor
0 siblings, 2 replies; 11+ messages in thread
From: DJ Delorie @ 1999-02-22 15:36 UTC (permalink / raw)
To: curtis; +Cc: cygwin
> Unfortunately, gdb's use of signals seems to interfere with
> debugging the cygwin signal handling code. I think I'm stuck with
> using strace after all.
Signals are just barely supported in gdb as is. Chris and I also use
strace to debug them.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Debugging the cygwin DLL
1999-02-22 14:12 ` DJ Delorie
@ 1999-02-22 15:06 ` Curtis Galloway
[not found] ` < 36D1E0A5.D4B841D2@pdi.com >
1999-02-28 23:02 ` Curtis Galloway
1999-02-28 23:02 ` DJ Delorie
1 sibling, 2 replies; 11+ messages in thread
From: Curtis Galloway @ 1999-02-22 15:06 UTC (permalink / raw)
To: DJ Delorie; +Cc: cygwin
DJ Delorie wrote:
>
> > Anyone have any hints for debugging the Cygwin dll? The messages I
> > found in the archive on the subject were pretty dated.
>
> You should be able to just use gdb to debug it, even as a dll. Have
> you tried? Hmmm, maybe it's one of those things that didn't make it
> into the last beta, or maybe it doesn't work as well as I think it
> does. If you did try, what happened?
Ah, indeed, if I
gdb cygwin1.dll
and then
gdb> exec-file myprogram.exe
I can debug functions within the cygwin DLL. Very nice.
Unfortunately, gdb's use of signals seems to interfere with debugging the
cygwin signal handling code. I think I'm stuck with using strace after all.
Thanks,
--Curtis
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Debugging the cygwin DLL
[not found] ` < 36D1D392.2FA663A3@pdi.com >
@ 1999-02-22 14:12 ` DJ Delorie
1999-02-22 15:06 ` Curtis Galloway
1999-02-28 23:02 ` DJ Delorie
0 siblings, 2 replies; 11+ messages in thread
From: DJ Delorie @ 1999-02-22 14:12 UTC (permalink / raw)
To: curtis; +Cc: cygwin
> Anyone have any hints for debugging the Cygwin dll? The messages I
> found in the archive on the subject were pretty dated.
You should be able to just use gdb to debug it, even as a dll. Have
you tried? Hmmm, maybe it's one of those things that didn't make it
into the last beta, or maybe it doesn't work as well as I think it
does. If you did try, what happened?
> Creating a static version of libcygwin.a seems to be the way to go.
> If anyone has done this already in b20.1, I'd love to hear from
> them.
It can be done, but it's not that easy. The big problem is that the
DLL has some initialization stuff that doesn't happen if you link it
statically, and it expects some things to be in the dll vs the exe,
like malloc, so you have to replace those as well.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* Debugging the cygwin DLL
@ 1999-02-22 14:02 Curtis Galloway
[not found] ` < 36D1D392.2FA663A3@pdi.com >
1999-02-28 23:02 ` Curtis Galloway
0 siblings, 2 replies; 11+ messages in thread
From: Curtis Galloway @ 1999-02-22 14:02 UTC (permalink / raw)
To: cygwin
Anyone have any hints for debugging the Cygwin dll? The messages I found in
the archive on the subject were pretty dated.
Creating a static version of libcygwin.a seems to be the way to go. If anyone
has done this already in b20.1, I'd love to hear from them.
--Curtis
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~1999-02-28 23:02 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-02-22 14:33 Debugging the cygwin DLL Earnie Boyd
1999-02-28 23:02 ` Earnie Boyd
-- strict thread matches above, loose matches on Subject: below --
1999-02-22 14:02 Curtis Galloway
[not found] ` < 36D1D392.2FA663A3@pdi.com >
1999-02-22 14:12 ` DJ Delorie
1999-02-22 15:06 ` Curtis Galloway
[not found] ` < 36D1E0A5.D4B841D2@pdi.com >
1999-02-22 15:36 ` DJ Delorie
1999-02-28 23:02 ` DJ Delorie
1999-02-28 23:02 ` Christopher Faylor
1999-02-28 23:02 ` Curtis Galloway
1999-02-28 23:02 ` DJ Delorie
1999-02-28 23:02 ` Curtis Galloway
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).