unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: szgyg <szgyg@ludens.elte.hu>
To: 39118@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#39118: Segfault while building on 64-bit Cygwin
Date: Tue, 21 Jan 2020 19:40:12 +0100	[thread overview]
Message-ID: <20200121184011.GA1659__5128.74378343753$1579632090$gmane$org@dtk> (raw)
In-Reply-To: <87sgk9faih.fsf@gnu.org>

On Tue, Jan 21, 2020 at 10:01:58AM +0100, Ludovic Courtès wrote:
> but before that you’d run
> “ulimit -c unlimited” in that shell to make sure there’s a core dumped
> when it crashes.

This won't work on cygwin. If you want a core dump, you should use the
dumper tool, as described here
https://cygwin.com/cygwin-ug-net/dumper.html
Or you can set error_start to gdb to get an interactive gdb session on error.

s





  parent reply	other threads:[~2020-01-21 18:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87zherlphs.fsf@pobox.com>
2020-01-13 17:26 ` GNU Guile 2.9.9 Released [beta] John Cowan
2020-01-13 23:09   ` bug#39118: " John Cowan
2020-01-20 16:35   ` bug#39118: Segfault while building on 64-bit Cygwin Ludovic Courtès
2020-01-20 16:38     ` John Cowan
     [not found]     ` <CAD2gp_ReS1DCZmsakcNK-FegZB_fhzOknDf_d0QdyDJVJS6X_A@mail.gmail.com>
2020-01-20 17:22       ` Mike Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-02-06 10:53         ` Andy Wingo
     [not found]         ` <87wo90kmw9.fsf@pobox.com>
2020-02-07  4:56           ` Charles Stanhope
     [not found]           ` <CAPydmiP42upuz1S=aP+hZk+tD5EJm00b4Gox1+LzEoJXVmRO=w@mail.gmail.com>
2020-02-14 17:46             ` Charles Stanhope
     [not found]             ` <CAPydmiN7eFD5r-v44hwdFM=1J24okQO8XjHqJ3bXQ2N1OkRVhA@mail.gmail.com>
2020-02-16 23:23               ` Mike Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2020-02-16 23:23               ` Mike Gran via Bug reports for GUILE, GNU's Ubiquitous Extension Language
     [not found]               ` <20200216232334.GA2448000@spikycactus.com>
2020-02-16 23:24                 ` John Cowan
2020-02-17  1:08                 ` Charles Stanhope
     [not found]                 ` <CAPydmiNnZ7qBbUgNJ_aKhfDORSBcHn8PbQABikL=sbP357tD=Q@mail.gmail.com>
2020-02-17 19:27                   ` Charles Stanhope
     [not found]                   ` <CAPydmiP44TawQf4SWLp1j4OsN-3e_VdDDx4i_R1w83hYQVGhyw@mail.gmail.com>
2020-02-17 21:05                     ` Andy Wingo
2020-01-21  9:01       ` Ludovic Courtès
     [not found]       ` <87sgk9faih.fsf@gnu.org>
2020-01-21 18:40         ` szgyg [this message]
2020-01-21 21:37         ` John Cowan
     [not found]         ` <20200121184011.GA1659@dtk>
2020-01-21 21:53           ` John Cowan
     [not found]         ` <CAD2gp_Ts8VfLUaQ+kC=g+f_5mv0jzLZpN_-U9dvi6Y4jy0-cLw@mail.gmail.com>
2020-01-23 20:35           ` Ludovic Courtès
     [not found]           ` <871rrpoqql.fsf@gnu.org>
2020-01-24 14:36             ` John Cowan
     [not found]             ` <CAD2gp_RkOYj6E6b9PjHerctAJN6NPYznQ4qi8NSXL0edKEM9dw@mail.gmail.com>
2020-01-25 13:51               ` Ludovic Courtès
     [not found]               ` <87wo9fbq60.fsf@gnu.org>
2020-01-25 15:54                 ` John Cowan
     [not found]                 ` <CAD2gp_Q3Ua+kRW5OV1jXM1D-H7UhKQp-TSd0RQjue7U=1ua62Q@mail.gmail.com>
2020-01-31 14:23                   ` John Cowan
2020-02-03 22:11                     ` szgyg
2020-02-05 21:11                       ` John Cowan
     [not found]                       ` <CAD2gp_Rcv81x4uKKTuokNbAWOkz-j77Hjet-oOzci1UFcgVDWg@mail.gmail.com>
2020-02-05 22:42                         ` szgyg
2020-01-24 15:26   ` dsmich

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to='20200121184011.GA1659__5128.74378343753$1579632090$gmane$org@dtk' \
    --to=szgyg@ludens.elte.hu \
    --cc=39118@debbugs.gnu.org \
    --cc=guile-devel@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).