delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2002/01/14/14:24:02

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <3C432F1C.1000609@ece.gatech.edu>
Date: Mon, 14 Jan 2002 14:18:52 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: egor duda <cygwin-developers AT cygwin DOT com>
CC: Jonathan Kamens <jik AT curl DOT com>
Subject: Re: Am I using dumper.exe correctly?
References: <20020110214350 DOT 30413 DOT qmail AT lizard DOT curl DOT com> <380850877 DOT 20020111104002 AT logos-m DOT ru> <20020114175405 DOT 9881 DOT qmail AT lizard DOT curl DOT com> <96167013072 DOT 20020114211637 AT logos-m DOT ru>

</me cringes>
Is it possible that gdb has problems with the new, Paul-Sokolovsky-style 
auto-importable DLLs?   Hmmm...using dllhelpers-0.2.6 (pre-auto-import) 
and dllhelpers-0.2.9 (post-) and running gdb on the test executables 
should answer that question.  I'll try to run that simple test later 
this week if nobody beats me to it...

--Chuck

egor duda wrote:

> Hi!
> 
> Monday, 14 January, 2002 Jonathan Kamens jik AT curl DOT com wrote:
> 
> JK> OK, so I tried reconfiguring without --enable-threadsafe and
> JK> --enable-extra-threadsafe-checking.  It's faster, bug gdb still
> JK> crashes when I try to use it to look at an exe and core file produced
> JK> by dumper.
> 
> Hmm. Does resulting core dump "looks" ok? it should be elf file of
> size 1MB or more. Do i remember correctly that gdb crashes even on
> coredump created by simple { int* x=0; *x=1; } program?
> 
> 
>>> can you try "gdb -nw --core=foo.exe.core" in the step 5?
>>>
> 
> JK> No, that coredumps too.
> 
> 
>>> what version of gdb are you using?
>>>
> 
> JK> Version 1.3.6-6 of the cygwin package (although I've actually built
> JK> the DLL from the repository -- I'm telling you the version of this
> JK> package I'm using so you know which dumper.exe I'm using) and version
> JK> 20010428-3 of the gdb package.
> 
> this should be fine.
> 
> JK> Do I need to update dumper.exe from the current repository along with
> JK> cygwin1.dll, or is it safe to use dumper.erxe from the cygwin 1.3.6-6
> JK> package?
> 
> I haven't changed anything in dumper since 1.3.6-6, so it's probably
> won't help.
> 
> you can wrap dumper.exe into dumper.cmd file and call it with
> debugging output to see what's going on.
> 
> anyway, i believe that even if dumper creates wrong dump file, gdb
> shouldn't crash on it. Is it possible for you to send me by private
> mail your foo.exe.core.bz2 (along with debugging output from
> dumper.exe, if possible), so i could take a look at them?
> 
> Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19
> 
> 


- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019