From: Alexander Nyberg <alexn@dsv.su.se>
To: Leonid Kalmankin <lvk@mashcenter.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: segfault and multiple traps on x86_64
Date: Tue, 14 Sep 2004 09:43:23 +0200 [thread overview]
Message-ID: <1095147803.701.3.camel@boxen> (raw)
In-Reply-To: <20040914013117.3bda812d.lvk@mashcenter.ru>
On Mon, 2004-09-13 at 23:31, Leonid Kalmankin wrote:
> Greetings!
>
> In dmesg I see stuff like:
>
> rpmbuild[3842] trap int3 rip:402d9e rsp:7fbfffb540 error:0
> rpmbuild[3842] trap int3 rip:4026d1 rsp:7fbfffb538 error:0
> sh[3843] trap int3 rip:415f39 rsp:7fbffff8c8 error:0
> sh[3843]: segfault at 0000000000000000 rip 0000000000000000 rsp 0000007fbffff8b8 error 14
> rpmbuild[3842] trap int3 rip:402dea rsp:7fbfffb540 error:0
> rpmbuild[3842] trap int3 rip:4025d1 rsp:7fbfffb538 error:0
> rpmbuild[3842] trap int3 rip:402ced rsp:7fbfffb540 error:0
> rpmbuild[3842] trap int3 rip:4027c1 rsp:7fbffff688 error:0
>
They just chose to show a small message in the log when some program
behaves badly. Nothing to worry about, more than your programs
misbehaving.
Alex
prev parent reply other threads:[~2004-09-14 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 21:31 segfault and multiple traps on x86_64 Leonid Kalmankin
2004-09-14 7:43 ` Alexander Nyberg [this message]
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=1095147803.701.3.camel@boxen \
--to=alexn@dsv.su.se \
--cc=linux-kernel@vger.kernel.org \
--cc=lvk@mashcenter.ru \
/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