Oracle Segfault Error 6
Contents |
-getfileinfo Dumps Core When Executing cluvfy [ID 1359659.1] Applies to:
Linux Segfault Error 6
Oracle Server - Enterprise Edition - Version: 11.2.0.2 and later[Release: 11.2 kernel segfault error 4 and later ] Information in this document applies to any platform. Purpose Command 'exectask -getfileinfo'
Segfault At Rip Rsp Error 6
is called by Cluster Verification Utility (CVU), the note lists issues related to exectask coredumps exectask -getfileinfo Dumps Core When Executing cluvfy Symptoms of the issue: segfault at ip sp error 4 For 11.2.0.2 and above, it can happen every 6 hours since ora.cvu resource is executed at that interval As "-getfileinfo" is called in a few different place, CVU can generate various errors but always with same error string "GetFileInfo command failed" ERROR: PRVF-4175 : OCR config file "/var/opt/oracle/ocr.loc" check failed on kernel segfault at rip rsp error 4 the following nodes: racnode1:GetFileInfo command failed. ERROR: PRVF-4178 : Check for OCR location "/ocrvd/clu1/ocr" failed on the following nodes: racnode1:GetFileInfo command failed Bug list: bug 9771737 - Core dump occurs if a non-existent file name is specified, fixed in 11.2.0.3 $ /tmp/CVU_11.2.0.2.0_oracle/exectask.sh -getfileinfo non-exist-file Segmentation fault bug 11816441 - Core dump happens when calling -getfileinfo, affects Solaris only, fixed in 11.2.0.3 Solutions/Workarounds The recommended solution is to apply patch set and patch set updates. If patch is not available, and ora.cvu keeps generating core, the workaround is to stop and disable the resource as grid user: $ $GRID_HOME/bin/srvctl stop cvu
$ $GRID_HOME/bin/srvctl disable cvu Publicat de Alexandru Garbia la 11/11/2011 Reacții: Niciun comentariu: Trimiteți un comentariu Postare mai nouă Postare mai veche Pagina de pornire Abonați-vă la: Postare comentarii (Atom) Tags Bug Oracle RDBMS (7) Linux/UNIX (7) Tips and tricks (5) Oracle RMAN tool backup (2) Oracle Books
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
Dmesg Segfault Error 4
company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions segfault error 14 Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million
Segfault Error Codes
programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How do you read a segfault kernel log message up vote 49 down vote favorite 29 This can be a http://oradbastuff.blogspot.com/2011/11/segfault-error-6-in-exectask-after.html very simple question, I'm am attempting to debug an application which generates the following segfault error in the kern.log kernel: myapp[15514]: segfault at 794ef0 ip 080513b sp 794ef0 error 6 in myapp[8048000+24000] Here are my questions: Is there any documentation as to what are the diff error numbers on segfault, in this instance it is error 6, but i've seen error 4, 5 What is the meaning of the information at bf794ef0 ip 0805130b http://stackoverflow.com/questions/2179403/how-do-you-read-a-segfault-kernel-log-message sp bf794ef0 and myapp[8048000+24000]? So far i was able to compile with symbols, and when i do a x 0x8048000+24000 it returns a symbol, is that the correct way of doing it? My assumptions thus far are the following: sp = stack pointer? ip = instruction pointer at = ???? myapp[8048000+24000] = address of symbol? c++ c unix segmentation-fault syslog share|improve this question edited Mar 31 '10 at 0:25 Charles Duffy 96.1k15103144 asked Feb 1 '10 at 19:20 Sullenx 246143 Added [unix] [segmentation-fault] [syslog] tags. –Emile Cormier Feb 1 '10 at 19:41 add a comment| 3 Answers 3 active oldest votes up vote 32 down vote Based on my limited knowledge, your assumptions are correct. sp = stack pointer ip = instruction pointer myapp[8048000+24000] = address If I were debugging the problem I would modify the code to produce a core dump or log a stack backtrace on the crash. You might also run the program under (or attach) GDB. The error code is just the architectural error code for page faults and seems to be architecture specific. They are often documented in arch/*/mm/fault.c in the kernel source. My copy of Linux/arch/i386/mm/fault.c has the following definition for error_code: bit 0 == 0 means no page found, 1 means protection fault bit 1 == 0 means rea
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 http://stackoverflow.com/questions/1456899/what-are-segfault-rip-rsp-numbers-and-how-to-use-them company Business Learn more about hiring developers or posting ads 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 6.2 million https://kb.vmware.com/kb/1023696 programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What are segfault rip/rsp numbers and how to use them up vote 10 down vote favorite 5 When my linux segfault error application crashes, it produces a line in the logs something like: segfault at 0000000 rip 00003f32a823 rsp 000123ade323 error 4 What are those rip and rsp addresses? how do I use them to pinpoint the problem? do they correspond to something in the "objdump" or "readelf" outputs? are they useful if my program gets its symbols stripped out (to a separate file, which can be used using gdb) debugging segmentation-fault share|improve this question edited segfault error 6 Jan 12 '10 at 2:30 Bill the Lizard 223k139448737 asked Sep 21 '09 at 21:11 johnnys add a comment| 2 Answers 2 active oldest votes up vote 6 down vote Well the rip pointer tells you the instruction that caused the crash. You need to look it up in a map file. In the map file you will have a list of functions and their starting address. When you load the application it is loaded to a base address. The rip pointer - the base address gives you the map file address. If you then search through the map file for a function that starts at an address slightly lower than your rip pointer and is followed, in the list, by a function with a higher address you have located the function that crashed. From there you need to try and identify what went wrong in your code. Its not much fun but it, at least, gives you a starting point. Edit: The "segfault at" bit is telling you, i'd wager, that you have dereferenced a NULL pointer. The rsp is the current stack pointer. Alas its probably not all that useful. With a memory dump you "may" be able to figure out more accurately where you'd got to in the function but it can be really h