Hi Richard,
Unfortunately I will not be able to bisect the issue - I really don't have the
knowledge to do that. My best contribution will probably be the testing of a
future solution, please let me know if you need any assistance with that.
I really appreciate your work!
Thanks,
Gunnar
> Dat
On Mon, Aug 15, 2011 at 5:58 PM, Gunnar Lindroth
wrote:
> Thank you Richard, that's really great news!
> My UML has 2GB available, I have assumed that to be enough?
> I'm sorry if I didn't make myself very clear about the output of the test
> program.
> In my UML this test program is not crashing
Thank you Richard, that's really great news!
My UML has 2GB available, I have assumed that to be enough?
I'm sorry if I didn't make myself very clear about the output of the test
program. In my UML this test program is not crashing either, but it's sometimes
printing "0.75 < 0" which it should _
Hello,
We've been using UML to run some computational applications (developed
in-house). The application runs fine for nearly 24h, then is killed
with signal 9. Just before the application is killed, these lines
appear on the console:
[102159.27] do_syscall_stub : ret = -12, offset = 105
On Mon, Aug 15, 2011 at 11:09 AM, Gunnar Lindroth
wrote:
> Hi,
> I'm trying to run a Java application in my 64-bit UML. Unfortunately I have
> experienced a lot of SIGSEGV's when running my application which makes it
> next to unusable (it crashes maybe 80% of the time). The only way I have
> foun
Hi,
I'm trying to run a Java application in my 64-bit UML. Unfortunately I have
experienced a lot of SIGSEGV's when running my application which makes it next
to unusable (it crashes maybe 80% of the time). The only way I have found to
make the SIGSEGV's go away has been to disable the Java Hot
Hi,
I'm resurrecting this old thread just to summarize the final outcome
for people coming to it from archive searches.
The "clone" stack trace has nothing to do with the real cause of the
error: starting with version R2010b, the MatLab runtime fails instead
with an "out of memory" error.
Indeed
On 15/08/11 04:04, Aniruddha Laud wrote:
> http://lkml.indiana.edu/hypermail/linux/kernel/1002.2/01983.html
>
> I see this thread discussing a similar issue where the main question is
> unanswered. Is it just a case of the Kconfig option not being there?
No, minimal support for 32-bit on 64-bit ker
