public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Joerg Rapka <joerg.rapka@duagon.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: insight crashed under cygwin
Date: Thu, 16 Jan 2003 16:20:00 -0000	[thread overview]
Message-ID: <1042734118.1413.2.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <3E268324.8020306@duagon.com>

On Thu, 2003-01-16 at 02:02, Joerg Rapka wrote:

> I have tried to used the debugger to debug the application 
> "arm-ecos-elf-insight.exe". I got the following warning message from GDB:
> Program received signal SIGSEV, segmentation fault (I cannot get the 
> position where it crash neither perform a stack backtrace).
> The same happens to all other "EXE" generated by the build process of 
> insight (e.g. arm-ecos-elf-gdb.exe, cygitclsh30.exe, tix4180.exe, etc.).

Are you saying the backtrace is worthless (ie., corrupted stack)? Then
the only other thing that I can think of doing is running one of these
executables under strace. Can your build environment build a simple,
"Hello, world" executable that runs (using same compiler, linker, etc
that's used to build insight et al)?

Keith


  reply	other threads:[~2003-01-16 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 14:37 Jörg Rapka
2003-01-10 14:45 ` Keith Seitz
2003-01-16 10:00   ` Joerg Rapka
2003-01-16 16:20     ` Keith Seitz [this message]
2003-01-17  7:28       ` Joerg Rapka
2003-01-17 15:13         ` Keith Seitz
2003-01-17 15:22           ` Joerg Rapka
2003-01-17 15:25             ` Keith Seitz
2003-01-17 15:48               ` Joerg Rapka
2003-01-17 16:33                 ` Keith Seitz

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=1042734118.1413.2.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=joerg.rapka@duagon.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).