From: Michael Snyder <msnyder@specifix.com>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB cannot access memory after Emacs abort
Date: Wed, 14 Nov 2007 12:00:00 -0000 [thread overview]
Message-ID: <1195041083.12695.57.camel@localhost.localdomain> (raw)
In-Reply-To: <873av9i2b6.fsf@escher.local.home>
On Wed, 2007-11-14 at 10:50 +0100, Stephen Berman wrote:
> On Sun, 11 Nov 2007 21:06:28 -0800 Michael Snyder <msnyder@specifix.com> wrote:
> [...]
> > To pursue it further, we can go one of two ways:
> >
> > A) maybe you can provide us with enough information and
> > context to reproduce the problem ourselves? This seems
> > unlikely, but maybe, for instance, you know that with
> > a certain released version of emacs and a certain released
> > version of linux, you can give a fixed sequence of commands
> > and reliably reproduce the crash?
> >
> > or
> >
> > B) we can keep asking you for more information, question
> > and answer style.
> >
> > For instance, I'd like to know the output that you get
> > from the following gdb commands when you're at the breakpoint:
> >
> > i) info registers
> > ii) info target
> > iii) x /64x $esp
>
> I posted a followup providing the requested information but it hasn't
> yet appeared on the list, perhaps because it was too long (the output of
> `info target' was 1815 lines long). Since I've gotten a backtrace in
> the mean time (see my followup to your suggestion to attach the emacs
> process to gdb), do you want me to repost or email you this information,
> or is it no longer relevant?
I think it's moot now.
Good luck!
prev parent reply other threads:[~2007-11-14 12:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r6j6rvn3.fsf@escher.local.home>
2007-11-10 23:50 ` Stephen Berman
2007-11-11 6:46 ` Michael Snyder
2007-11-11 7:44 ` Eli Zaretskii
2007-11-11 23:05 ` Stephen Berman
2007-11-12 4:18 ` Eli Zaretskii
2007-11-12 5:24 ` Michael Snyder
2007-11-13 22:40 ` Stephen Berman
2007-11-13 23:20 ` Michael Snyder
2007-11-13 23:28 ` Dan Nicolaescu
2007-11-14 10:00 ` Stephen Berman
2007-11-13 23:57 ` Andreas Schwab
2007-11-11 19:22 ` Daniel Jacobowitz
2007-11-11 23:10 ` Stephen Berman
2007-11-12 0:39 ` Daniel Jacobowitz
2007-11-12 17:47 ` Jim Blandy
2007-11-12 19:44 ` Andreas Schwab
2007-11-13 22:36 ` Stephen Berman
2007-11-13 22:34 ` Stephen Berman
2007-11-13 23:14 ` Michael Snyder
2007-11-14 9:48 ` Stephen Berman
2007-11-13 23:51 ` Andreas Schwab
2007-11-12 7:39 ` Vladimir Prus
2007-11-13 22:36 ` Stephen Berman
2007-11-13 23:24 ` Michael Snyder
2007-11-14 9:50 ` Stephen Berman
2007-11-14 12:00 ` Michael Snyder
2007-11-14 19:24 ` Stephen Berman
2007-11-15 1:00 ` Michael Snyder
2007-11-11 23:01 ` Stephen Berman
2007-11-12 5:15 ` Michael Snyder
2007-11-14 9:55 ` Stephen Berman
2007-11-14 12:00 ` Michael Snyder [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=1195041083.12695.57.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=Stephen.Berman@gmx.net \
--cc=gdb@sources.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).