Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH 1/4] Add sniffer for Cygwin x86_64 core dumps
Date: Mon, 24 Aug 2020 18:02:13 +0100	[thread overview]
Message-ID: <5def8e4e-c777-1844-3786-5d4d2e0cae1a@dronecode.org.uk> (raw)
In-Reply-To: <21fa41cf-ca6c-061e-2036-07c283313a41@simark.ca>

On 24/08/2020 16:47, Simon Marchi wrote:
> On 2020-08-22 3:52 p.m., Jon Turney wrote:
>>
>> Hmmm.  This often means the executable can't be started due to problems
>> loading DLLs.
>>
>> If you want to pursue this further, running under cygwin's strace (e.g.
>> 'strace dumper') might shed more light.
> 
> Ahh, I downloaded the x86 version of the snapshot instead of the x86-64!

:)

> When using dumper.exe from the x86-64, it works.  I that dumper.exe from the
> snapshot also runs much faster than the original dumper.exe, don't know if that's
> expected.

Yeah, I fixed some bogosity which was making it slow.

> I now get this:
> 
> $ ./gdb -q --data-directory=data-directory ~/a.exe -ex "core ~/core.core"
> Reading symbols from /home/simark/a.exe...
> warning: core file may not match specified executable file.
> [New process 6408]
> [New process 6504]
> [New process 904]
> [New process 5068]
> [New process 4892]
> #0  0x00007ff92bba01b4 in ?? ()
> [Current thread is 1 (process 6408)]
> (gdb) bt
> #0  0x00007ff92bba01b4 in ?? ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> 
> Since I just copied my binary and core out of Cygwin, and the program was stopped somewhere
> under sleep(), it's perhaps expected that GDB has trouble unwinding from system libraries
> it doesn't have access to.

Yeah, I don't think unwinding is going to be very successful in that 
case. Thanks for trying it out.

The "testing" I have been doing is mainly:

> $ cat dumper-test.c
> 
> void fault()
> {
>   // deref null pointer
>   *(int *)0 = 1;
> }
> 
> int main()
> {
>   fault();
> }
> 
> $ gcc -g -O0 dumper-test.c -o dumper-test.exe
> 
> $ CYGWIN='error_start=dumper' ./dumper-test
> 
> $ gdb dumper-test.exe dumper-test.exe.core
> [...]
> (gdb) bt
> #0  0x00007ffb4498fc20 in ntdll!KiUserExceptionDispatcher () from C:/WINDOWS/SYSTEM32/ntdll.dll
> #1  0x0000000100401089 in fault () at dumper-test.c:5
> #2  0x00000001004010a4 in main () at dumper-test.c:10


  reply	other threads:[~2020-08-24 17:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 19:18 [PATCH 0/4] Add gdb support for Cygwin x86_64 core dumps (v2) Jon Turney
2020-08-12 19:18 ` [PATCH 1/4] Add sniffer for Cygwin x86_64 core dumps Jon Turney
2020-08-20 22:20   ` Simon Marchi
2020-08-21 15:25     ` Jon Turney
2020-08-21 16:22       ` Simon Marchi
2020-08-21 16:28         ` Jon Turney
2020-08-22 19:41           ` Simon Marchi
2020-08-22 19:52             ` Jon Turney
2020-08-24 15:47               ` Simon Marchi
2020-08-24 17:02                 ` Jon Turney [this message]
2020-08-12 19:18 ` [PATCH 2/4] Add amd64_windows_gregset_reg_offset Jon Turney
2020-08-20 22:08   ` Simon Marchi
2020-09-18 16:31     ` Jon Turney
2020-08-12 19:18 ` [PATCH 3/4] Promote windows_core_xfer_shared_libraries and windows_core_pid_to_str Jon Turney
2020-08-12 19:18 ` [PATCH 4/4] Add handling for 64-bit module addresses in Cygwin core dumps Jon Turney
2020-08-24 18:34   ` Simon Marchi
2020-09-15 21:44     ` Jon Turney
2020-09-16  2:20       ` Simon Marchi
2020-09-16  9:15         ` Christian Biesinger
2020-08-12 19:30 ` [PATCH 0/4] Add gdb support for Cygwin x86_64 core dumps (v2) Eli Zaretskii
2020-08-13 14:43   ` Jon Turney
2020-08-13 16:48     ` Eli Zaretskii
2020-08-18 15:32       ` Jon Turney
2020-08-18 16:15         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5def8e4e-c777-1844-3786-5d4d2e0cae1a@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox