Linux PARISC architecture development
 help / color / mirror / Atom feed
From: thunder7@xs4all.nl
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: What's a "Trace/breakpoint trap" and why does he crash my system?
Date: Wed, 5 Sep 2001 21:03:09 +0200	[thread overview]
Message-ID: <20010905210309.A9929@middle.of.nowhere> (raw)
In-Reply-To: <20010901212835.A18546@middle.of.nowhere>

On Sat, Sep 01, 2001 at 09:28:35PM +0200, thunder7@xs4all.nl wrote:
> On Sat, Sep 01, 2001 at 08:14:55PM +0100, Matthew Wilcox wrote:
> > On Sat, Sep 01, 2001 at 08:32:32PM +0200, thunder7@xs4all.nl wrote:
> > > should be 'Trace/breakpoint trap'
> > 
> > hmm.. what version of glibc do you have installed?  something else you
> > can do is run strace -ff which will attempt to follow fork/clone/vfork.
> > 
> 2.2.3-9. 2.2.4 is out, I know.
> 
> strace -ff:
> 
<snip strace output>

one strance thing is that it will run correctly under gdb (the 5.0-4
version off the 0.9.2 iso).

Without gdb, it always prints
Trace/breakpoint trap

and no other output. The C200 then hangs, 90% of the time even the
power-switch doesn't work. I'm getting some sort of yoga-training just
trying to reach behind it for the power-cord :-)

Since I don't know how to get earlier kernels (it doesn't work in
2.4.9-pa13, it works with 2.4.0 from the 0.9.2 iso) I can't do anything
else than whine about it again. Sorry about that.

Jurriaan
-- 
HORROR FILM WISDOM:
3. Do not search the basement, especially when the power has just gone out.
GNU/Linux 2.4.9-ac7 SMP/ReiserFS 2x1402 bogomips load av: 0.34 0.22 0.16

  reply	other threads:[~2001-09-05 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-01 13:50 [parisc-linux] What's a "Trace/breakpoint trap" and why does he crash my system? thunder7
2001-09-01 18:32 ` thunder7
2001-09-01 19:14   ` Matthew Wilcox
2001-09-01 19:28     ` thunder7
2001-09-05 19:03       ` thunder7 [this message]
2001-09-02 17:39     ` 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=20010905210309.A9929@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --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