public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: kettenis@chello.nl
Cc: brobecker@gnat.com, mec.gnu@mindspring.com, cagney@gnu.org,
	gdb@sources.redhat.com
Subject: Re: [6.2] PROBLEMS file
Date: Fri, 23 Jul 2004 12:13:00 -0000	[thread overview]
Message-ID: <1438-Fri23Jul2004150121+0300-eliz@gnu.org> (raw)
In-Reply-To: <7494-Fri23Jul2004141636+0300-eliz@gnu.org>

> Date: Fri, 23 Jul 2004 14:16:37 +0200
> From: "Eli Zaretskii" <eliz@gnu.org>
> 
> > Date: Fri, 23 Jul 2004 11:23:32 +0200 (CEST)
> > From: Mark Kettenis <kettenis@chello.nl>
> > 
> > GDB loses track after frame #21, but I doubt whether
> > recursive_edit_1 is a frameless function.  Can you post a
> > dissassembly of that function?
> 
> Here it is:

Sorry, I failed to mention my GCC version.  It's 3.3.3.  I could
install 3.4.1 and try with that, if it matters.

  reply	other threads:[~2004-07-23 12:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 12:14 Michael Elizabeth Chastain
2004-07-22 18:28 ` Joel Brobecker
2004-07-22 19:26   ` Eli Zaretskii
2004-07-22 20:51     ` Mark Kettenis
2004-07-23  9:24       ` Eli Zaretskii
2004-07-23 11:22         ` Mark Kettenis
2004-07-23 12:03           ` Eli Zaretskii
2004-07-23 12:13             ` Eli Zaretskii [this message]
2004-07-23 12:16             ` Dave Korn
2004-07-23 13:36             ` Mark Kettenis
2004-07-23 16:17               ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2004-07-23  5:44 Michael Elizabeth Chastain
2004-07-23 20:44 ` Andrew Cagney
2004-07-19  3:51 Andrew Cagney
2004-07-19 21:01 ` Eli Zaretskii
2004-07-21 21:12   ` Mark Kettenis
2004-07-21 22:05     ` H. J. Lu
2004-07-22 20:58       ` Mark Kettenis
2004-07-22 21:33         ` Joel Brobecker
2004-07-22 21:38         ` H. J. Lu
2004-07-21 22:17     ` Andrew Cagney
2004-07-22  7:13       ` Eli Zaretskii
2004-07-22 13:04     ` Dave Korn
2004-07-22 15:17       ` Daniel Jacobowitz

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=1438-Fri23Jul2004150121+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=kettenis@chello.nl \
    --cc=mec.gnu@mindspring.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).