|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Expert-to-Expert. Learn advanced UNIX, UNIX commands, Linux, Operating Systems, System Administration, Programming, Shell, Shell Scripts, Solaris, Linux, HP-UX, AIX, OS X, BSD. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problem in checking file abort | ahjiefreak | Shell Programming and Scripting | 1 | 04-16-2008 09:42 PM |
| stack overflow in function psync_status Abort (core dumped) | jmcpreach | BSD | 0 | 04-29-2006 05:26 PM |
| Any tool to examine the error or traffic on the machine? | umen | SUN Solaris | 2 | 04-26-2006 09:14 AM |
| Abort core dumped!!!! | zing | Filesystems, Disks and Memory | 2 | 07-10-2003 01:59 AM |
| How to examine the memory usage?? | comadreja | UNIX for Advanced & Expert Users | 11 | 01-23-2003 01:05 AM |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
07-31-2007
|
||||
|
||||
|
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) |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Threaded Mode
