![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Rules & FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Advanced UNIX and Linux questions go here. Expert-to-Expert. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problem in checking file abort | ahjiefreak | Shell Programming and Scripting | 1 | 04-16-2008 05:42 PM |
| stack overflow in function psync_status Abort (core dumped) | jmcpreach | BSD | 0 | 04-29-2006 01:26 PM |
| Any tool to examine the error or traffic on the machine? | umen | SUN Solaris | 2 | 04-26-2006 05:14 AM |
| Abort core dumped!!!! | zing | Filesystems, Disks and Memory | 2 | 07-09-2003 09:59 PM |
| How to examine the memory usage?? | comadreja | UNIX for Advanced & Expert Users | 11 | 01-22-2003 09:05 PM |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
examine core file after abort()
I'm running Red Hat Linux 2.6.7 on a x86_64 box.
I have a core file from a program that called abort(). Does anyone here know how can I get a backtrace? (Re-creating the error with svd running inside gdb has proved impossible). % gdb svd core.25223 GNU gdb Red Hat Linux (6.0post-0.20040223.19rh) ... Core was generated by `svd'. Program terminated with signal 6, Aborted. ... #0 0x0000003db9b2dc05 in raise () from /lib64/tls/libc.so.6 (gdb) bt #0 0x0000003db9b2dc05 in raise () from /lib64/tls/libc.so.6 Cannot access memory at address 0x7fbfffe038 (gdb) |
| Forum Sponsor | ||
|
|