Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Brian Vandenberg <phantall@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>, gdb@sourceware.org
Subject: Re: gdbserver sparc solaris
Date: Mon, 11 Feb 2019 19:31:00 -0000	[thread overview]
Message-ID: <CAEJ-0i97GhQBQMpUooRowxeqzcG2MqSbtrzLqv-2kgiZXxWe8w@mail.gmail.com> (raw)
In-Reply-To: <20190209041209.GO6371@adacore.com>

On Fri, Feb 8, 2019 at 9:12 PM Joel Brobecker <brobecker@adacore.com> wrote:

> > Is it possible to make gdb act like gdbserver?
>
> Why not debug directly on the machine, then?
>

My apologies if my wording wasn't clear:


> > This all came about due to some GDB crashes we're seeing with a very
> > complicated executable.  I haven't had the time to try to figure out why
> > it's crashing, instead just limping by with dbx until I have more time.
> I
> > was just hoping for an easy way out until I have more free time.


GDB is crashing when trying to debug directly on the machine and I haven't
had the time to dive in to figure out why; we've had to limp along using
dbx from Solaris Studio in the mean-time.  I had hoped if I could get
remote debugging to work perhaps the problem wouldn't manifest or would
help shed light on the problem by causing a different problem.

-brian


  reply	other threads:[~2019-02-11 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08  1:41 Brian Vandenberg
2019-02-08 12:51 ` Pedro Alves
2019-02-08 13:05   ` Rainer Orth
2019-02-08 13:26     ` Pedro Alves
2019-02-08 21:20   ` Brian Vandenberg
2019-02-09  4:12     ` Joel Brobecker
2019-02-11 19:31       ` Brian Vandenberg [this message]
2019-02-12  3:09         ` Joel Brobecker
2019-02-13  0:32           ` Brian Vandenberg

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=CAEJ-0i97GhQBQMpUooRowxeqzcG2MqSbtrzLqv-2kgiZXxWe8w@mail.gmail.com \
    --to=phantall@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=palves@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