From: "Eli Zaretskii" <eliz@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Partial fix for PR backtrace/1718
Date: Sat, 24 Jul 2004 17:58:00 -0000 [thread overview]
Message-ID: <7105-Sat24Jul2004205643+0300-eliz@gnu.org> (raw)
In-Reply-To: <200407241259.i6OCxu8R041119@elgar.kettenis.dyndns.org> (message from Mark Kettenis on Sat, 24 Jul 2004 14:59:56 +0200 (CEST))
> Date: Sat, 24 Jul 2004 14:59:56 +0200 (CEST)
> From: Mark Kettenis <kettenis@chello.nl>
>
> This fixes the backtrace problem with Emacs that Eli reported.
Alas, it doesn't fix the problem for me: after applying the patch to
i386-tdep.c that shipped with GDB 6.1, I still get the same mess in
the backtrace at the same place. Should the patch work for GDB 6.1?
Let me know how can I help you further.
next prev parent reply other threads:[~2004-07-24 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 12:59 Mark Kettenis
2004-07-24 17:58 ` Eli Zaretskii [this message]
2004-07-30 18:35 ` Eli Zaretskii
2004-07-30 20:08 ` Mark Kettenis
2004-07-31 13:41 ` Eli Zaretskii
2004-07-31 15:09 ` Michael Chastain
2004-07-31 18:44 ` Eli Zaretskii
2004-08-01 5:35 ` Michael Chastain
2004-08-01 13:54 Mark Kettenis
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=7105-Sat24Jul2004205643+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.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