public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Florian Weimer <fw@deneb.enyo.de>, Andrew Haley <aph@redhat.com>,
	Xi Ruoyao <xry111@mengyan1223.wang>,
	gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Recursive SIGSEGV question
Date: Thu, 28 Mar 2019 14:39:00 -0000	[thread overview]
Message-ID: <b72e77ce-a16a-f603-6b7c-bf62b8185dc8@jguk.org> (raw)
In-Reply-To: <CAH6eHdQJ1L8v6BR8qRQ1WOWCF_Zwc-ckVLAO1+6s57YA-FLakA@mail.gmail.com>



On 28/03/2019 11:52, Jonathan Wakely wrote:
> On Wed, 27 Mar 2019 at 23:47, Jonny Grant wrote:
>> I did wonder, as -fsanitize=address seems to inhibit the core dump that
>> is otherwise created by the abort() that appears to be called - is that
>> a known issue?
> 
> Sorry for not thinking of this before you filed the bug report, but as
> I said there, the problem is probably not Asan but your settings.
> Check what ulimit -a shows for the max core file size, see what
> 'sysctl -a | grep kernel.core' shows and if appropriate check the
> MaxCrashReportsSize in /etc/abrt/abrt.conf
> 
> So Asan isn't suppressing the core file, it's just making the address
> space larger (for the shadow memory it uses to track heap usage) and
> that causes a much larger core file, which your system then doesn't
> dump.
> 

Hi!
Thank you for your reply

My system is on unlimited core size, so should be okay, 416G free..?

Maybe at least the code that isn't outputting the core, could output the 
reason. I wondered if Asan had overridden the abort() function? Maybe 
Asan putting in an ABRT handler...?

It would b the same as sending ABRT signal I expect:
kill -ABRT <pid>



$ ulimit -a
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 63536
max locked memory       (kbytes, -l) 16384
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 63536
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited



# sysctl -a | grep kernel.core
kernel.core_pattern = core
kernel.core_pipe_limit = 0
kernel.core_uses_pid = 0
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.enp4s0.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
sysctl: reading key "net.ipv6.conf.vmnet1.stable_secret"
sysctl: reading key "net.ipv6.conf.vmnet8.stable_secret"
sysctl: reading key "net.ipv6.conf.wlp3s0.stable_secret"

I don't have /etc/abrt/abrt.conf  on Ubuntu

Jonny

  reply	other threads:[~2019-03-28 14:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 22:05 Jonny Grant
2019-03-20  4:02 ` Florian Weimer
2019-03-20  8:11   ` Jonny Grant
2019-03-25 13:23   ` Jonny Grant
2019-03-25 13:27     ` Jonathan Wakely
2019-03-25 13:56     ` Florian Weimer
2019-03-25 14:01     ` Xi Ruoyao
2019-03-25 15:47       ` Florian Weimer
2019-03-25 16:10         ` Andrew Haley
2019-03-25 16:13           ` Jonny Grant
2019-03-25 16:23             ` Jonathan Wakely
2019-03-25 18:51           ` Florian Weimer
2019-03-25 20:39             ` Jonny Grant
2019-03-26  6:50               ` Xi Ruoyao
2019-03-27  0:29                 ` Jonathan Wakely
2019-03-27 21:34             ` Jonny Grant
2019-03-27 23:43               ` Jonathan Wakely
2019-03-27 23:51                 ` Jonny Grant
2019-03-28  8:26                   ` Xi Ruoyao
2019-03-28 11:52                     ` Jonathan Wakely
2019-03-29  2:24                     ` Jonny Grant
2019-03-30 17:32                       ` Jonny Grant
2023-02-19 21:21                       ` Jonny Grant
2023-02-19 21:34                         ` Jonny Grant
2019-03-28 13:55                   ` Jonathan Wakely
2019-03-28 14:39                     ` Jonny Grant [this message]
2019-03-28 14:39                       ` Jonathan Wakely
2019-03-25 20:28         ` Segher Boessenkool
2019-03-25 18:56       ` Segher Boessenkool
2019-03-25 22:05       ` Jonny Grant
2019-03-26 10:20         ` Xi Ruoyao

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=b72e77ce-a16a-f603-6b7c-bf62b8185dc8@jguk.org \
    --to=jg@jguk.org \
    --cc=aph@redhat.com \
    --cc=fw@deneb.enyo.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=xry111@mengyan1223.wang \
    /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).