It is currently Wed Dec 01, 2021 12:22 am

All times are UTC - 8 hours [ DST ]




Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: bad_alloc
PostPosted: Wed Mar 04, 2009 8:34 am 
Offline

Joined: Tue Mar 03, 2009 3:58 pm
Posts: 3
Location: McGill HEP
Hi,

As a new user, I just installed v50p on Linux and am getting a bad_alloc error when running either of the test files (599278 and 999276). After entering

>galprop 599276

I receive a large number of

iso_abundance_28_067
iso_abundance_28_067 not found in galdef file!
iso_abundance_28_068
iso_abundance_28_068 not found in galdef file!

etc, followed by (what looks like) proper execution, until

>>>> read_HIR
reading HIR from ../FITS/rbands_hi7.fits
read HIR open status= 104
0read HIR status= 104
1read HIR status= 104
2read HIR status= 104
3read HIR status= 104
5read HIR status= 104
6read HIR status= 104
8read HIR status= 104
9read HIR status= 104
NAXIS = 136035360
NAXIS1,2,3 = -1207769308 -1078009944 135946699
CRVAL1,2 = 89129 -3.25739e-05
CDELT1,2 = -3.12078e-05 4.68648e-34
#read HIR status= 104
generating galaxy.HIR:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Abort


rbands_hi7.fits is in the /FITS directory as it should be, and as far as I could find out bad_alloc is a memory problem, although running galprop on different machines doesn't seem to help (the most I have access to is 3gb). Has anyone run into this problem before? Any help would be greatly appreciated.

thanks,

Aaron


Top
 Profile  
 
 Post subject: Re: bad_alloc
PostPosted: Mon Mar 09, 2009 11:30 am 
Offline

Joined: Tue Mar 03, 2009 3:58 pm
Posts: 3
Location: McGill HEP
Turned out to be a directory issue. Working now!


Top
 Profile  
 
 Post subject: Re: bad_alloc
PostPosted: Sat Jul 29, 2017 7:12 am 
Offline

Joined: Thu Jun 22, 2017 5:51 pm
Posts: 2
I am new to Galprop, and now using galprop-54.1.984, It show errors as follows, and computer screen gets stuck for a while.

.
.
.
store_gcr: Exit
store_gcr: Time elapsed: 0.0533s (Real); 0.04s (Process); 0s (System)
terminate called after throwing an instance of 'std :: bad_alloc'
what(): std :: bad_alloc
Aborted (core dumped)


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC - 8 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group