Mike Marchywka wrote:
>
> > .rdata relocs it is then.
>
> This is why I lurk as I now remember something about this and, sure, I can
> find it on google.
> Of course, it would still be nice to have a fully instrumented load ( so
> where do I find the
> unreolcatable data?) .
> I relinked with -
e any concerns if applicable.
Note: Hotmail is possibly blocking my mom's entire
ISP - try me on [EMAIL PROTECTED] if no reply
here. Thanks.
> Date: Wed, 28 May 2008 14:08:31 -0700
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: cygwin@cygwin.com
> Subject: Re: MS o
Mike Marchywka wrote:
> I think I mentioned the windoze invokation before and got the definitive "
> The app failed to initialize ..."
> meesage. I didn't know about strace, let me see if I can expand on this,
.rdata relocs it is then.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsu
e
ISP - try me on [EMAIL PROTECTED] if no reply
here. Thanks.
> Date: Wed, 28 May 2008 12:47:44 -0700
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: cygwin@cygwin.com
> Subject: Re: MS or cygwin dll debug tools/ was "sys/sockio.h" etc.
>
> Mike Marchywka
Christopher Faylor wrote:
> Aren't we still talking about using msvcrt and cygwin1 in the same
> application where something like a SIGSEGV prior to initialization would
> be the expected consequences of mixing the two dlls?
Right, that too I suppose. You'd have to set breakpoints at the DllMain
On Wed, May 28, 2008 at 12:47:44PM -0700, Brian Dessent wrote:
>Mike Marchywka wrote:
>
>> (gdb) b *0x0401000
>> Breakpoint 1 at 0x401000
>> (gdb) run
>> Starting program: /cygdrive/e/new/temp/nmap/src3/nmap-4.62/a.exe
>>
>> Program received signal SIGSEGV, Segmentation fault.
>>
>> Program recei
Mike Marchywka wrote:
> (gdb) b *0x0401000
> Breakpoint 1 at 0x401000
> (gdb) run
> Starting program: /cygdrive/e/new/temp/nmap/src3/nmap-4.62/a.exe
>
> Program received signal SIGSEGV, Segmentation fault.
>
> Program received signal SIGSEGV, Segmentation fault.
>
> Program received signal SIGS
SIGSEGV, Segmentation fault.
Program exited with code 0200.
You can't do that without a process to debug.
(gdb)
> Date: Wed, 28 May 2008 08:36:33 -0700
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: cygwin@cygwin.com
> Subject: Re: MS or cygwin dll debug tools/ was "
Hello,
* On Wed, May 28, 2008 at 10:15:05AM -0400 Mike Marchywka wrote:
>
> Regarding recent comments on dll problems and understanding cygwin1.dll
> versus msvcrt,
> I was curious to know if anyone has used these ( free? ) MS tools or has
> comments on competing
> products?
>
> http://msdn.mi
Greg Chicares wrote:
> Using cygwin's gdb on a MinGW app, I can set this breakpoint
> b '__mingw_CRTStartup'
> on the function that invokes main(), and then examine variables
> before main() is invoked. For a Cygwin app, I guess you'd break
> on 'mainCRTStartup'. Does that breakpoint happen earl
On 2008-05-28 14:15Z, Mike Marchywka wrote:
>
> I was curious to know if anyone has used these ( free? ) MS tools
Probably not free as in freedom; I haven't used them.
> Apparently gdb didn't let you do anything until getting to main() which is
> after the initial
> process loads but some of the
11 matches
Mail list logo
