Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>,
	Ulrich Weigand <uweigand@de.ibm.com>,
	GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [IRIX] eliminate deprecated_insert_raw_breakpoint uses
Date: Wed, 10 Sep 2014 22:44:00 -0000	[thread overview]
Message-ID: <20140910224358.GS28404@adacore.com> (raw)
In-Reply-To: <54107860.6060301@redhat.com>

> I think I understand this enough now.  See patch below, which
> gets rid of that loop completely.

Thanks for walking me by memory lane :-)

> Untested, of course.

I found an IRIX machine that's still up and running, and I was able
to rebuild it. Unfortunately, two issues occured:
  1. I had to make insert_breakpoint_locations non-static;
  2. GDB now SIGSEGV-s when starting a program:

Program received signal SIGSEGV, Segmentation fault.
0x10163180 in bpstat_stop_status (aspace=0x108b97b0, bp_addr=268791248, 
    ptid=..., ws=0x7ffd7870)
    at /nfs/nas/homes/brobecke/act/gdb-public/gdb/breakpoint.c:5536
5536          b->ops->check_status (bs);

The problem is that b->ops is NULL. I can continue investigating,
but I have this feeling that this is just a waste of time, since
I strongly suspect that IRIX support is going to be removed
a couple of weeks from now (I can start the procedure if you'd like).

-- 
Joel


  reply	other threads:[~2014-09-10 22:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 17:46 eliminate deprecated_insert_raw_breakpoint. what's left Pedro Alves
2014-09-08 19:24 ` Joel Brobecker
2014-09-08 21:34   ` Joel Brobecker
2014-09-08 22:50     ` Pedro Alves
2014-09-09  0:25       ` Peter Schauer
2014-09-09  0:16     ` Peter Schauer
2014-09-09 11:39       ` Ulrich Weigand
2014-09-09 12:38         ` Peter Schauer
2014-09-09 21:25           ` Ulrich Weigand
2014-09-10 12:21             ` Joel Brobecker
2014-09-10 13:15               ` Ulrich Weigand
2014-09-10 15:22                 ` Pedro Alves
2014-09-09 21:48   ` Ulrich Weigand
2014-09-10 12:29     ` Joel Brobecker
2014-09-10 14:45       ` Ulrich Weigand
2014-09-10 15:21         ` Pedro Alves
2014-09-10 15:50           ` Maciej W. Rozycki
2014-09-10 16:12             ` [IRIX] eliminate deprecated_insert_raw_breakpoint uses Pedro Alves
2014-09-10 22:44               ` Joel Brobecker [this message]
2014-09-10 23:02                 ` Pedro Alves
2014-09-11  3:27                   ` Joel Brobecker
2014-09-12 19:34                     ` Pedro Alves
2014-09-12 20:23                       ` Joel Brobecker
2014-09-10 15:50           ` eliminate deprecated_insert_raw_breakpoint. what's left Joel Brobecker
2014-09-10 16:00             ` Sergio Durigan Junior
2014-09-10 16:36             ` Ulrich Weigand
2014-09-10 18:59               ` New deprecation procedure Pedro Alves
2014-09-11 19:03                 ` Joel Brobecker
2014-09-12  8:51                   ` Ulrich Weigand
2014-10-07  0:25         ` eliminate deprecated_insert_raw_breakpoint. what's left Stan Shebs
2014-09-09 17:33 ` Pedro Alves

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=20140910224358.GS28404@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.com \
    --cc=palves@redhat.com \
    --cc=uweigand@de.ibm.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