public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: elfutls using assert
Date: Thu, 12 Jul 2007 15:10:00 -0000	[thread overview]
Message-ID: <46964453.1010608@redhat.com> (raw)
In-Reply-To: <20070710184623.A1F904D0585@magilla.localdomain>

Roland McGrath wrote:
>> Unless I'm mistaken, it isn't possible to attach the abort signal as it 
>> may be sent to any thread?  
>>     
>
>   

Good, I'll add code to attempt that.

> You are mistaken.  If you are catching the signal, you will catch all such
> signals in whatever thread they are delivered.  Anyway, abort is equivalent
> to raise (SIGABRT), which means synchronously to the calling thread (the
> signal will appear to happen immediately after the syscall instruction for
> the syscall that performs the "raise").
>
>   
>> Anyway, to make the problem more concrete, when a panic like this occurs,
>> frysk needs time to pull all inserted breakpoints before detaching from
>> the program and exiting.
>>     
>
> Like I said, when one of these hits, you are lucky if all memory is not
> randomly clobbered already.  But if you just avoid anything that would call
> into elfutils libs at all, you might be avoiding the memory that is
> definitely clobbered already, and be lucky enough to survive long enough to
> withdraw gracefully.
>
>
> Thanks,
> Roland
>   

      reply	other threads:[~2007-07-12 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 12:38 Andrew Cagney
2007-07-09 23:08 ` Roland McGrath
2007-07-10 15:34   ` Andrew Cagney
2007-07-10 18:47     ` Roland McGrath
2007-07-12 15:10       ` Andrew Cagney [this message]

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=46964453.1010608@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=roland@redhat.com \
    /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).