From: Brian Vandenberg <phantall@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: gdbserver sparc solaris
Date: Fri, 08 Feb 2019 21:20:00 -0000 [thread overview]
Message-ID: <CAEJ-0i96RbfnUEMPHxpPR4Fg0HVjWMVxEabzaXqniO_ZWBpZaw@mail.gmail.com> (raw)
In-Reply-To: <657f3267-c77a-096f-561b-96136c5efc4f@redhat.com>
>
> Not without someone porting gdbserver to solaris.
>
> > Is there an alternative to gdbserver?
>
> Might exist, but I don't know of one myself.
>
Is it possible to make gdb act like gdbserver?
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.
-brian
next prev parent reply other threads:[~2019-02-08 21:20 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 [this message]
2019-02-09 4:12 ` Joel Brobecker
2019-02-11 19:31 ` Brian Vandenberg
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-0i96RbfnUEMPHxpPR4Fg0HVjWMVxEabzaXqniO_ZWBpZaw@mail.gmail.com \
--to=phantall@gmail.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