home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!spool.mu.edu!umn.edu!csus.edu!netcom.com!hill
- From: hill@netcom.com (Tom Hill)
- Subject: Re: Calling C from VB--Debug??
- Message-ID: <1993Jan5.065703.16842@netcom.com>
- Organization: Netcom Online Communications Services (408-241-9760 login: guest)
- References: <1993Jan5.003744.19694@hplabsz.hpl.hp.com>
- Date: Tue, 5 Jan 1993 06:57:03 GMT
- Lines: 13
-
- In article <1993Jan5.003744.19694@hplabsz.hpl.hp.com> yefchak@hplabsz.hpl.hp.com (George Yefchak) writes:
- >I'm using Microsoft QuickC to write DLL's which I call from Visual
- >Basic 2.0. Is there a way to do source-level debugging in the C
- >code after it's called from VB? (Yes, I've already used the debugger
- >from within QuickC by having a little main() routine call the DLL
- >from C, but now that that worked I'm having problems getting VB to
- >call it correctly, and I thought having the debugger alive might
- >help.)
-
- Try softice/w from NuMega, it seems to be able to debug most anything
- at a source level, including DLLs and VxDs.
-
- Tom Hill
-