public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Nicholas_Karagas@cirilium.com
To: Chris Faylor <cgf@cygnus.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: segmentation fault on exit in Insight 5.0
Date: Wed, 28 Jun 2000 13:12:00 -0000	[thread overview]
Message-ID: <OF7E8514AB.DD6FB0D3-ON0725690C.006E2A8B@cirilium.com> (raw)

>>Hello again,
>>
>>I tried downloading the gdb/Insight 5.0 release, and still have the same
>>problem (SIGSEGV when exiting).  Here's the complete backtrace (actually,
>>all output) from debugging the Insight session.  All I did was start
>>Insight with my .gdbinit file and immediately exit.  Note that the line
>>numbers for remote.c may not match yours exactly, as I have some stuff
>>specific to our particular setup in there.  I am connecting to a remote
>>m68k via Remote/Serial at 38400 baud.  I am running Cygwin
1.1.0(0.18/3/2)
>>(from uname -r) on WINNT 4.0 (Build 1381: Service Pack 6).  Any help on
>>this would be greatly appreciated.  Thanks.
>>
>>GNU gdb 4.17.1
>         ^^^^^^
>This is not gdb 5.0.
>
>cgf

No, I realize that 4.17.1 is not 5.0.  But you must have misunderstood me.
I was debugging the Insight/gdb 5.0 cross-debugger for m68k, and to debug
it I was using my local gdb, which happens to be 4.17.1.  (In other words,
the command I entered to get the above output was "gdb m68k-coff-gdb".)
The segmentation violation is in Insight 5.0, not gdb 4.17.1.  Please take
a look at the rest of the output dump if you want to see the problem.  I
could not show the output from Insight 5.0, because the fault only occurs
when I use the GUI.

Nicholas Karagas
Associate Software Engineer
Cirilium Corporation
Tempe, AZ
(480) 317-1144

             reply	other threads:[~2000-06-28 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-28 13:12 Nicholas_Karagas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-28 15:17 Nicholas_Karagas
2000-06-27 10:22 Nicholas_Karagas
2000-06-28 12:54 ` Chris Faylor
2000-06-28 14:27   ` Jim Ingham
2000-06-28 14:36     ` Chris Faylor
2000-06-28 14:38       ` Chris Faylor

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=OF7E8514AB.DD6FB0D3-ON0725690C.006E2A8B@cirilium.com \
    --to=nicholas_karagas@cirilium.com \
    --cc=cgf@cygnus.com \
    --cc=insight@sourceware.cygnus.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).