From: "David S. Miller" <davem@redhat.com>
To: kukuk@suse.de
Cc: gcc@gcc.gnu.org
Subject: Re: Illegal instruction on sparc32-linux
Date: Fri, 19 Apr 2002 03:40:00 -0000 [thread overview]
Message-ID: <20020419.031602.107960434.davem@redhat.com> (raw)
In-Reply-To: <20020419114721.A8609@suse.de>
From: Thorsten Kukuk <kukuk@suse.de>
Date: Fri, 19 Apr 2002 11:47:22 +0200
On Thu, Apr 18, David S. Miller wrote:
> Can you put the program under GDB so we can see what the instruction
> is that it is trapping on?
I tried it. But when I compile it with -g, I cannot reproduce it from
the shell or from gdb. But if I call "make", it fails again.
It has to be dropping a core file somewhere, check that out
with gdb.
next prev parent reply other threads:[~2002-04-19 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 13:18 Thorsten Kukuk
2002-04-18 13:32 ` Christian Jönsson
2002-04-18 14:51 ` David S. Miller
2002-04-19 2:51 ` Thorsten Kukuk
2002-04-19 3:40 ` David S. Miller [this message]
2002-04-19 4:45 ` Thorsten Kukuk
2002-04-19 9:03 ` David S. Miller
2002-04-19 9:20 ` Thorsten Kukuk
2002-04-24 7:07 ` David S. Miller
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=20020419.031602.107960434.davem@redhat.com \
--to=davem@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kukuk@suse.de \
/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).