From: Stu Grossman <grossman@juniper.net>
To: Mark Kettenis <kettenis@science.uva.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patches for FreeBSD 4.2
Date: Thu, 12 Jul 2001 16:51:00 -0000 [thread overview]
Message-ID: <15182.14341.585416.731581@gundor.juniper.net> (raw)
In-Reply-To: <s3izoa9fswj.fsf@soliton.wins.uva.nl>
Mark Kettenis writes:
> * This file won't compile on FreeBSD 3.x, since <machine/sigframe.h>
> doesn't exist. Besides, the implementation of a *_frame_saved_pc
> function belongs in a target-dependent file, and shouldn't depend on
> the target headers. What's wrong with the old implementation?
Let me clarify my previous message... This needs to be fixed in order to make
backtraces through signal handlers work. I think that without this fix, the
backtrace stops at the signal handler, or worse yet, it prints junk for the
caller or the interrupted code.
Stu
prev parent reply other threads:[~2001-07-12 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 23:39 Stu Grossman
2001-07-11 8:46 ` Andrew Cagney
2001-07-11 9:18 ` Stu Grossman
2001-07-12 13:50 ` Mark Kettenis
2001-07-12 14:58 ` Stu Grossman
2001-07-13 8:16 ` Mark Kettenis
2001-07-12 16:51 ` Stu Grossman [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=15182.14341.585416.731581@gundor.juniper.net \
--to=grossman@juniper.net \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@science.uva.nl \
/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