[Next-Generation Sequencing Book]

Submit | Open tickets | Closed tickets

[ Ticket #178 ] -M problems on some systems
Date:
02/07/04 08:35
Submitted by:
dmb 		Assigned to:
unset
Category:
Compiling 		Priority:
5
Ticket group:
Non-critical 		Resolution:
Resolved
Summary:
-M problems on some systems
Original submission:
I have heard of and experienced a few problems with the -M option on some systems (sorry for lack of details). It seems that the units of -M can vary from system to system.
Please log in to add comments and receive followups via email.
Followups
Comment Date By

Linux beagle 2.4.20-31.9 #1 Tue Apr 13 17:38:16 EDT 2004 i686 athlon i386 GNU/Linux)

I found if I use -M up to 2212 the program runs fine, but after that (2213) I get a fatal memory error...

Fatal Error
No memory, change -M option

Program halted !!


Then if I increase the value of -M beyond 2211974 (i.e. to 2211975) it starts working again!

I am confused how / what causes the above error. Probing the memory space isn't showing up a clear pattern. I could do a full sweep, but it probably already makes sense to someone in the know
08/16/04 15:46 unset
No results for "Dependent on ticket"
No results for "Dependent on Task"
No other tickets are dependent on this ticket
Ticket change history
Field Old value Date By
status_id Open 05/16/11 00:38 liwz
assigned_to lducazu 05/16/11 00:38 liwz
resolution_id Unset 05/16/11 00:38 liwz
close_date 12/31/69 19:00 05/16/11 00:38 liwz
status_id Unset 08/19/04 07:32 dmb
assigned_to unset 08/13/04 11:05 dmb

© 1998-2025 Scilico, LLC. All rights reserved.