From: Geoff Keating <geoffk@cygnus.com>
To: "George T. Talbot" <george@phat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: -fstack-check on Linux x86--Dumb question...
Date: Sat, 18 Mar 2000 16:27:00 -0000 [thread overview]
Message-ID: <jm66ujst23.fsf@envy.cygnus.com> (raw)
In-Reply-To: <001901bf90eb$82923f00$18db08cf@lottalove.phat.com>
"George T. Talbot" <george@phat.com> writes:
> <whine>
> It would be a nice patch to GDB and/or GNU/Linux to print:
>
> "Program received SIGSEGV at address 0x2394782 while attempting
> to read from address 0xFDFEFFF."
>
> Right now, it just gives me the program counter. Of course, I'm not really
> sure of how to patch GDB or the kernel to give me such support.
> </whine>
The program 'catchsegv' which comes with GNU libc 2.1 and later does
exactly this.
--
- Geoffrey Keating <geoffk@cygnus.com>
next prev parent reply other threads:[~2000-03-18 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-18 7:05 George T. Talbot
2000-03-18 16:27 ` Geoff Keating [this message]
2000-03-19 20:43 ` George T. Talbot
-- strict thread matches above, loose matches on Subject: below --
2000-03-17 18:46 Mike Stump
2000-03-17 17:11 George T. Talbot
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=jm66ujst23.fsf@envy.cygnus.com \
--to=geoffk@cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=george@phat.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).