From: rpm <rajendra.mishra@timesys.com>
To: root@chaos.analogic.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: c++ program reboots system.
Date: Mon, 13 May 2002 21:08:18 +0530 [thread overview]
Message-ID: <200205131540.g4DFcI601617@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.3.95.1020513075608.19504A-100000@chaos.analogic.com>
> }
> Script started on Mon May 13 07:51:12 2002
> # gdb xxx
> GDB is free software and you are welcome to distribute copies of it
> under certain conditions; type "show copying" to see the conditions.
> There is absolutely no warranty for GDB; type "show warranty" for details.
> GDB 4.15 (i586-unknown-linux), Copyright 1995 Free Software Foundation,
> Inc... (gdb) run
> Starting program: /root/xxx
>
> Program received signal SIGSEGV, Segmentation fault.
> ostream::flush (this=0x8c224) at iostream.cc:864
> 864 if (_strbuf->sync())
> (gdb) quit
> The program is running. Quit anyway (and kill it)? (y or n) y
> # exit
> exit
> Script done on Mon May 13 07:51:49 2002
>
> On Linux 2.4.18, the program just seg-faults (as it should).
> On the version you are using, you should write a 'C' program
> that does lseek() beyond EOF. There could be a bug there, but
> otherwise I can't tell from the program presented.
I executed the same C++ code on iPAQ , on the 2.4.7 kernel and it works fine !
no seg faults no reboots,
I also tried the C program you suggested , but that too works fine, no
reboots no seg faults! :(
rpm
next prev parent reply other threads:[~2002-05-13 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 12:02 Richard B. Johnson
2002-05-13 15:38 ` rpm [this message]
2002-05-13 16:40 ` Richard B. Johnson
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=200205131540.g4DFcI601617@localhost.localdomain \
--to=rajendra.mishra@timesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®