From: John Marvin <jsm@udlkern.fc.hp.com>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: Trace/Breakpoint trap on "make mrproper"
Date: Fri, 7 Sep 2001 07:56:42 -0600 (MDT) [thread overview]
Message-ID: <200109071356.HAA22153@udlkern.fc.hp.com> (raw)
>
> It looks like this patch:
> >Date: Thu, 6 Sep 2001 03:48:16 -0600 (MDT)
> >From: John Marvin jsm@udlkern.fc.hp.com
> >Subject: [parisc-linux-cvs] Patch for SMP support, etc.>
> >A rather large patch that includes my current SMP support changes, plus
> >a variety of other fixes/changes.
>
> did something. But it's so large I'm not sure what exactly :-)
>
> Jurriaan
>
I was pretty sure my changes to handle_break (in traps.c) would fix that
problem. When I read your note I remembered that I had seen a similar
problem and fixed it. The kernel would hang when a user program executed
a break instruction (either intentionally or not) without an attached
debugger. That is the problem you were seeing.
However, now that the machine doesn't hang, I am not sure if the remaining
problem you are seeing is a kernel bug or a userland bug. It would appear
that you are executing 0's (0x00000000 is a break instruction). That
should cause the kernel to send you a SIGTRAP signal. I just checked some
of your old mail, and it looks like you are getting a SIGTRAP. One thing
that looks strange is that you are getting signals delivered using stack
addresses both at ~0xfaf00000 and ~0xbff00000. I wonder if make is using
an alternate signal stack?
John
next reply other threads:[~2001-09-07 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 13:56 John Marvin [this message]
2001-09-07 19:13 ` [parisc-linux] Re: Trace/Breakpoint trap on "make mrproper" thunder7
2001-09-16 14:28 ` thunder7
-- strict thread matches above, loose matches on Subject: below --
2001-09-07 19:22 [parisc-linux] Re: Trace/Breakpoint trap on "make mrproper"] thunder7
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=200109071356.HAA22153@udlkern.fc.hp.com \
--to=jsm@udlkern.fc.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
/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