Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Randolph Chung <randolph@tausq.org>
Cc: Mark Kettenis <kettenis@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Modernize HP-UX core file handling
Date: Fri, 10 Dec 2004 15:50:00 -0000	[thread overview]
Message-ID: <20041210145001.GF987@adacore.com> (raw)
In-Reply-To: <20041210074458.GR29171@tausq.org>

> Mark, I haven't had a chance to test your patch yet. I will do that
> tomorrow. But in the recent past, core file handling was completely
> broken on both hppa2.0w-hp-hpux11.11 and hppa64-hp-hpux11.11 (it always
> segfaults when reading a core file for me), so i suspect whatever you
> have will be better (at least a step in the right direction)

Hmmm, bizarre. I thought it was working fine for me (at least not
crashing), but I must have been using 6.3. With head, I got:

    This GDB was configured as "hppa2.0w-hp-hpux11.00"...
    (gdb) core core
    Core was generated by `crash'.
    Program terminated with signal 6, Aborted.
    Register flags not found in core file.

(but no crash, like you). I'm running on 11.00.

After Mark's changes, I get something much better:

    (gdb) bt
    #0  0xc01f5e38 in kill () from /usr/lib/libc.2
    #1  0x00002988 in cause_crash () from ./crash
    Cannot access memory at address 0xffffffed

I'll look at the unwinding failure when I have a moment.

Nice work, Mark!
-- 
Joel


  parent reply	other threads:[~2004-12-10 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 23:36 Mark Kettenis
2004-12-10  9:45 ` Randolph Chung
2004-12-10 10:46   ` Mark Kettenis
2004-12-10 15:50   ` Joel Brobecker [this message]
2004-12-16 19:53     ` Joel Brobecker
2004-12-16 23:52       ` Randolph Chung
2004-12-17  6:52 John David Anglin

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=20041210145001.GF987@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@gnu.org \
    --cc=randolph@tausq.org \
    /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