From: Rusty Russell <rusty@rustcorp.com.au>
To: Ian Zimmerman <itz@very.loosely.org>, ccan@lists.ozlabs.org
Subject: Re: configurator still segfaults, what am I doing wrong?
Date: Wed, 13 Feb 2019 09:46:38 +1030 [thread overview]
Message-ID: <87lg2kiomh.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20190209224423.qvo356b3jy3oyowr@matica.foolinux.mooo.com>
Ian Zimmerman <itz@very.loosely.org> writes:
> On 2019-02-09 14:00, Rusty Russell wrote:
>
>> Ian Zimmerman <itz@very.loosely.org> writes:
>> > matica!60 ccantest$ /home/itz/git/ccan/tools/create-ccan-tree --build-type=make+config /home/itz/ccantest/ccan tal
>> > Building ccan_depends, modfiles
>> > sh: line 1: 17440 Segmentation fault (core dumped) ./configurator.out 2>&1
>>
>> OK, that's weird. If you run tools/configurator/configurator normally
>> does it do this? If so, try under gdb...
>
> Not much help, see below. Could this be some kind of resource
> exhaustion? My desktop has "only" 8GB store. Also, what is this about
> "configurator.out"?? The executable name in the file system is called
> "configurator".
Actually, I missed that; it's a configurator test failing, which is
actually OK.
Your problem is actually not being in the top-level of the ccan dir.
Hope that helps!
Rusty.
PS. Running ./tools/configurator/configurator --verbose will tell you
what test it was, if you're curious...
>
> gdb -c configurator.core ./tools/configurator/configurator
> GNU gdb (GDB) Fedora 8.1.1-4.fc28
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from ./tools/configurator/configurator...done.
>
> warning: core file may not match specified executable file.
> [New LWP 15858]
> Core was generated by `./configurator.out'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x00007fe2ed934989 in ?? ()
> (gdb) bt
> #0 0x00007fe2ed934989 in ?? ()
> #1 0x0000000000000000 in ?? ()
>
> (Debug symbols for glibc are installed.)
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
> _______________________________________________
> ccan mailing list
> ccan@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/ccan
next prev parent reply other threads:[~2019-02-13 4:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 4:13 configurator still segfaults, what am I doing wrong? Ian Zimmerman
2019-02-09 3:30 ` Rusty Russell
2019-02-09 22:44 ` Ian Zimmerman
2019-02-12 23:16 ` Rusty Russell [this message]
2019-02-21 6:38 ` Ian Zimmerman
2019-02-22 5:15 ` Rusty Russell
2019-03-17 21:12 ` Ian Zimmerman
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=87lg2kiomh.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=ccan@lists.ozlabs.org \
--cc=itz@very.loosely.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).