Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 19 Apr 2001 17:21:23 +0400
From: egor duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: egor duda <cygwin AT sources DOT redhat DOT com>
Organization: deo
X-Priority: 3 (Normal)
Message-ID: <44422777892.20010419172123@logos-m.ru>
To: "Reinhard JESSICH" <Reinhard DOT JESSICH AT frequentis DOT com>
CC: cygwin AT sources DOT redhat DOT com, reinhard DOT jessich AT telering DOT at
Subject: Re: dumper.exe doesn't work
In-reply-To: <sadefa6c.040@mail.frequentis.com>
References: <sadefa6c DOT 040 AT mail DOT frequentis DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Thursday, 19 April, 2001 Reinhard JESSICH Reinhard DOT JESSICH AT frequentis DOT com wrote:

>> >>>i don't think so. maybe gdb snapshots are built without cygwin core
>> >>>dumps support? can you build gdb yourself and check? make sure that
>> >>>configure finds sys/procfs.h and win32_pstatus_t in it.
>>                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ only this, i think.
RJ> I have build gdb from source and I saw in the config.h file in the bfd subdirectory, that
RJ> HAVE_WIN32_PSTATUS_T is defined. Therefore, I think core dump support is build
RJ> in gdb per default. Sorry for making you trouble with this.

...

RJ> I have found in the list archive, that I have to do the following, to activate dumper.exe.
RJ> I have to add "error_start=drive:\\pathtodumper\\dumper.exe" to the CYGWIN
RJ> environment variable (I have tried unix path name and this doesn't work).

that's right. path should be native win32

RJ> The problem was, that this never terminated (maybe I have waited to less time,
RJ> only 2 Minutes). Then I have used gdb instead of dumper to check if cygnus exception
RJ> handler will call any program and this worked.

you can make dumper more "verbose":

set CYGWIN=error_start=drive:\\pathtodumper\\dump_wrapper.cmd

and create drive:\\pathtodumper\\dump_wrapper.cmd file containing one line:

============== dump_wrapper.cmd ====================
drive:\\pathtodumper\\dumper.exe -v -c %1 %2
====================================================

for a testing purposes you can also dump any "healthy" process. just
get its win32-pid using 'ps -l' command, and then type

dumper -v <win32_pid_of_target_process>

RJ> Please can you tell me what I have done wrong here.

RJ> Then I have compiled my test program with the -mno_cygwin switch and installed
RJ> dumper instead of DrWatson in the registry as debugger.
RJ> This worked now and I got a coredump (.core), but this was not readable by gdb
RJ> (gdb --core=.core test.exe says unknown architecture).

ah, i remember something like this. but IIRC, message about unknown
architecture was only warning, and core loads successfully afterwards.

can you try to type
'info target' and 'info threads' and 'backtrace' in gdb?

i'll look if i can fix this warning, though.

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple