On Friday 02 January 2004 06:15 pm, Richard Urwin wrote:
-> I don't see why the 3D. -> Try gdb -core=core -> -> Without the executable file that produced the core you aren' t likely to get -> much useful information. What are you trying to do?
Thanks Richard, for clarifying - I just passed this along to John after searching the archives. I've never had reason to run this (so far). :-)
Trouble is, I cannot seem to get the 3D bit to work at all. gdb -core=core.7674 doesn't give you much, so if 3D is to work how does it go in the line ?
John
LATER
=====
Experimenting with man gdb I came up with,
[EMAIL PROTECTED] root]# cd /mnt/ext2-vol6/downloads2/divx
[EMAIL PROTECTED] divx]# ls
core.18439 dvdripsingle toystory1.avi
[EMAIL PROTECTED] divx]# gdb mencoder core.18439
GNU gdb 5.3-22mdk (Mandrake Linux)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-mandrake-linux-gnu"...
(no debugging symbols found)...
Core was generated by `mencoder dvd://1 -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=1024 -oac mp3lam'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libmp3lame.so.0...(no debugging symbols found)...
done.
Loaded symbols for /usr/lib/libmp3lame.so.0
Reading symbols from /usr/lib/libvorbis.so.0...(no debugging symbols found)...
done.
Loaded symbols for /usr/lib/libvorbis.so.0
Reading symbols from /usr/lib/libogg.so.0...(no debugging symbols found)...
done.
Loaded symbols for /usr/lib/libogg.so.0
Reading symbols from /usr/lib/libpng.so.3...(no debugging symbols found)...
done.
Loaded symbols for /usr/lib/libpng.so.3
Reading symbols from /lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /usr/lib/libjpeg.so.62...(no debugging symbols found)...
done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/libfreetype.so.6...
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libfreetype.so.6
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/i686/libpthread.so.0...
(no debugging symbols found)...done.
Loaded symbols for /lib/i686/libpthread.so.0
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/i686/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/i686/libm.so.6
Reading symbols from /lib/i686/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/i686/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0x081b5fb8 in ff_combine_frame ()
(gdb)
and so gdb <programme> <core[nnnn]> seems to yield up more info
However in the above case it still comes back to
"Loaded symbols for /lib/ld-linux.so.2
#0 0x081b5fb8 in ff_combine_frame ()
(gdb)"
which is not that much more info really, except that all the prior stuff doesn't seem to caused any problems , whch I suppose is helpful info of a sort.
I wonder what more detailed info one can extract.
There are usually core files placed all over your OS in various odd places, if anyone would lke to experiment with the CL try doing gdb in the directory of the core file.
If I understand this correctly I can run gdb with the programme in question , which might yield up better information, so if I figure out how to do this maybe that is the better route.
John
-- John Richard Smith [EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
