Caught Bus Error Dumping Stack
Contents |
1 #1 2011-07-08 13:39:32 agkbill Member Registered: 2011-06-13 Posts: 85 [SOLVED] rtorrent. Caught Bus error dumping stack. Hi,I am experience problems with rtorrent, it have been running very nice bus error c for some weeks. But not any more.I get:christer ~ $ rtorrent Caught
Bus Error Linux
Bus error, dumping stack: Stack dump not enabled. A bus error probably means you ran out of diskspace. bus error vs segmentation fault Aborted christer ~ $When I check diskspace it looks like that is not the issue here.christer ~ $ df Filesystem Size Used Avail Use% Mounted on udev 10M 0 bus error (core dumped) linux 10M 0% /dev run 10M 168K 9.9M 2% /run /dev/sda3 12G 4.2G 6.9G 38% / shm 120M 0 120M 0% /dev/shm /dev/sdb1 76G 32G 41G 44% /media/torr christer ~ $Folders belongin to rtorrent are located on a external USB disk /dev/sdb-Downloads-torrents-sessionI mount the USB disk at /media/torr.Disks look like.christer ~ $ sudo fdisk -ls Password: Disk /dev/sda: 40.0
How To Debug Bus Error
GB, 40007761920 bytes 255 heads, 63 sectors/track, 4864 cylinders, total 78140160 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00077627 Device Boot Start End Blocks Id System /dev/sda1 2048 52537343 26267648 83 Linux /dev/sda2 77160195 78140159 489982+ 83 Linux /dev/sda3 * 52537344 77160194 12311425+ 83 Linux Partition table entries are not in disk order Disk /dev/sdb: 82.0 GB, 81963515904 bytes 255 heads, 63 sectors/track, 9964 cylinders, total 160084992 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00096092 Device Boot Start End Blocks Id System /dev/sdb1 2048 160083967 80040960 83 Linux christer ~ $ Any ideas what it could be or how to pinpoint what the problem is?Thank you!All the best./Christer Last edited by agkbill (2011-07-10 09:41:27) Offline #2 2011-07-08 14:30:38 Inxsible Forum Fellow From: Chicago Registered: 2008-06-09 Posts: 9,079 Re: [SOLVED] rto
'non-existent physical address' Next message: [R-SIG-Mac] [R] R 2.10 memory leak on OS X Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Hi Simon, I think I've found the problem: filehash needs to be rebuilt. how to fix bus error in linux The data that I've been using the problematic expressions on resides in a filehash database. Having bus error (core dumped) c reduced the problem to one particular data frame of two columns and 1000 rows, I just copied it to its own database, zipped
Bus Error Python
it, and attached it to an email containing instructions on how to reproduce the problem, when I decided I should test whether you could indeed reproduce the problem by following my instructions. And, of course, everything worked just https://bbs.archlinux.org/viewtopic.php?id=122267 as I had not expected, i.e., there was no bus error. So I copied the data frame from the small database that I was going to send to you to the original, and there the problem occurred. I could not reproduce the problem, however, if I copied the original data frame to my workspace and forced R to actually instantiate the copy before running the problematic script. So the problem seemed to have something to do https://stat.ethz.ch/pipermail/r-sig-mac/2009-November/006855.html with filehash and the size of the database. I also recalled that I had no problem with the script if I ran R in 32-bit mode. I therefore tried reinstalling the filehash binary, but that did not solve the problem. Then, I installed it from the source. That evidently is what was required. So I guess it only needs a rebuild so that other folks do not experience the same problem. Regards, Richard Richard R. Liu Dittingerstr. 33 CH-4053 Basel Switzerland Tel.: +41 61 331 10 47 Mobil: +41 79 708 67 66 Email: richard.liu at pueo-owl.ch On Nov 30, 2009, at 17:18 , Simon Urbanek wrote: > Richard, > > I didn't touch anything, but then you didn't supply a reproducible > example so we can't do much about it (the trace is unfortunately > bogus). My next step woul dbe to try it in valgrind if I could > reproduce it ... > > Cheers, > Simon > > On Nov 30, 2009, at 11:01 , Richard R. Liu wrote: > >> This problem disappeared in patched releases soon after I replied >> to Simon that I was unable to obtain the information that he >> required from the debugger. After checking a few releases I quite >> monitoring the problem. I assumed that it had been fixed with >> comment. However, today, the patched r
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads http://stackoverflow.com/questions/2069450/how-to-get-a-bus-error with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign https://forums.gentoo.org/viewtopic-p-5982305.html up How to get a “bus error”? up vote 12 down vote favorite 1 I am trying very hard to get a bus error. One way is misaligned access and I have tried the examples given here and here, but no bus error error for me - the programs execute just fine. Is there some situation which is sure to produce a bus error? c++ bus-error share|improve this question edited Jan 15 '10 at 9:50 asked Jan 15 '10 at 4:06 Lazer 24.8k65210309 2 What platform and hardware architecture are you using? –R Samuel Klatchko Jan 15 '10 at 5:32 it should be noted that by default x86 will not have a bus error, instead it will work but the memory access will be bus error (core not as performant as an aligned read. on the other hand SPARC arches do have a bus error. –Evan Teran Jan 15 '10 at 6:50 1 No, see Michael Burr's comments and my answer. Even on x86, you can get a bus error by attempting to access memory which does not exist (as opposed to a segmentation fault, which comes from a violation of access policy). –ephemient Jan 16 '10 at 16:29 add a comment| 11 Answers 11 active oldest votes up vote 11 down vote accepted Bus errors can only be invoked on hardware platforms that: Require aligned access, and Don't compensate for an unaligned access by performing two aligned accesses and combining the results. You probably do not have access to such a system. share|improve this answer answered Jan 15 '10 at 4:09 Ignacio Vazquez-Abrams 443k62792950 is there some way to be sure of that? –Lazer Jan 15 '10 at 4:11 @eSKay: If you're using an Intel CPU, which means basically any personal computer nowadays, you will never get a bus error from misaligned access. If you're using PowerPC, SPARC, etc., then you can cause a bus error that way. –Chris Jester-Young Jan 15 '10 at 4:13 2 Do you have any SPARC or MIPS equipment? –Ignacio Vazquez-Abrams Jan 15 '10 at 4:13 yes, I am using Intel P4. Any idea why no error on Intels? –Lazer Jan 15 '10 at 4:14 3 There are typically othe
posts View posts from last 24 hours Gentoo Forums Forum Index Kernel & Hardware View previous topic :: View next topic Author Message MouseeApprenticeJoined: 29 Mar 2004Posts: 291Location: Illinois, USA Posted: Tue Sep 22, 2009 1:14 am Post subject: High Overhead and Kernel (mis?)Configuration Issues Sorry if the topic name is a bit ambiguous/non-descript. This is a problem I've been trying to work out for over two weeks now without any real success and I think I've narrowed it down to an issue with my kernel configuration - I'm just not sure where exactly. Let me explain and I'll post the relevant information following it in hopes that someone can find where my fault lies. I apologize in advance if I'm too verbose or descriptive - I'm just trying to go over every detail in case someone catches something I may have missed. See the very end of this post for system information also. In short: This post is about me trying to get rtorrent to stop crashing while hashing torrents over 8gigs in size and my associating it to a possible kernel (mis-)configuration issue. Problem: Intro: I recently migrated to dedicated server hosted by OVH/Kimsufi. In doing so I decided I wanted to start torrenting some of the programs I use and normally download via bittorrent (ie. OpenOffice). I therefore installed rtorrent and its dependencies, modified the port number, home directory, and session directory in .rtorrent.rc, and fired rtorrent up all ready to start downloading and seeding. This worked really well until I closed rtorrent and reopened it. Once re-opened, rtorrent naturally started to re-hash each fully and partially downloaded torrent. At random percentages, usually less than half-way through, larger torrents of 8gigs or more would completely crash my system. By completely crash I mean I had to perform a hard reboot on