Somebody scribbled about Re: [newbie] Core dump
>and I suppose it's going to start a rip file inside directory
> sources, yes ? if so I think I had better move the directory
Sure it will, but it's trivial to use -o /tmp/toystory.avi instead of
-o toystory.avi, provided of cours
On Thursday 08 Jan 2004 8:04 pm, John Richard Smith wrote:
> Richard Urwin wrote:
> >On Thursday 08 Jan 2004 11:04 am, John Richard Smith wrote:
> >>Forced video codec: ffmpeg12
> >>Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
> >>Cannot find codec 'mpegvideo' in libavcodec...
>
Richard Urwin wrote:
On Thursday 08 Jan 2004 6:41 pm, JoeHill wrote:
On Fri, 02 Jan 2004 16:59:19 +
John Richard Smith <[EMAIL PROTECTED]> wrote:
When you get a core dump, what can you then do to read it ?
I dunno, but I think this thread is heading for a record...holy shite.
Richard Urwin wrote:
On Thursday 08 Jan 2004 11:04 am, John Richard Smith wrote:
Forced video codec: ffmpeg12
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Cannot find codec 'mpegvideo' in libavcodec...
VDecoder init failed :(
Cannot find codec matching selected -vo and video
On Thursday 08 Jan 2004 6:41 pm, JoeHill wrote:
> On Fri, 02 Jan 2004 16:59:19 +
>
> John Richard Smith <[EMAIL PROTECTED]> wrote:
> > When you get a core dump, what can you then do to read it ?
>
> I dunno, but I think this thread is heading for a record...holy shite.
Especially since it's al
On Fri, 02 Jan 2004 16:59:19 +
John Richard Smith <[EMAIL PROTECTED]> wrote:
> When you get a core dump, what can you then do to read it ?
I dunno, but I think this thread is heading for a record...holy shite.
--
JoeHill ++ ICQ # 280779813
Registered Linux user #282046
Homepage: www.orderin
On Thursday 08 Jan 2004 11:04 am, John Richard Smith wrote:
> Forced video codec: ffmpeg12
> Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
> Cannot find codec 'mpegvideo' in libavcodec...
> VDecoder init failed :(
> Cannot find codec matching selected -vo and video format 0x1
Richard Urwin wrote:
On Wednesday 07 Jan 2004 10:33 pm, John Richard Smith wrote:
Your run:
MPEG Stream reached EOF0%) 19fps Trem: 0min 529mb A-V:-0.046
[817:96] A/Vms 4/40 D/B/S 28985/1/0
ds_fill_buffer: EOF reached (stream: audi
What is the value of LIBAVCODEC_BUILD ?
You will find it in libavcodec/avcodec.h on about line 20.
It will look something like:
#define LIBAVCODEC_BUILD
(If it's not there then grep the whole libavcodec directory for it.)
Thanks,
--
Richard Urwin
Want to buy your Pack or Services from M
Richard Urwin wrote:
Looks good. But I'm afraid I don't have time to look at it tonight.
Sure, We all have to fit this inbetween everything else in our lives.
Please let me know what you think when your've had time to think about it.
thanks,
John
--
John Richard Smith
[EMAIL PROTECTED]
Looks good. But I'm afraid I don't have time to look at it tonight.
--
Richard Urwin
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Richard Urwin wrote:
No.
Search the source code file libavcodec/mpegvideo.c for the line:
av_log(s->avctx, AV_LOG_ERROR, "get_buffer() failed (%d %d %d %p)\n", r, pic->age, pic->type, pic->data[0]);
Make a note of it's line number.
(kwrite displays line numbers in the bottom left of the status
On Monday 05 Jan 2004 9:11 pm, John Richard Smith wrote:
> Richard Urwin wrote:
> >On Monday 05 Jan 2004 10:29 am, John Richard Smith wrote:
> >>High quality encoding selected (non real time)!
> >>get_buffer() failed (0 -115967 0 0x40d5df30)
> >
> >Oh look at that.
> >Can you run it again, but befo
Richard Urwin wrote:
On Monday 05 Jan 2004 10:29 am, John Richard Smith wrote:
High quality encoding selected (non real time)!
get_buffer() failed (0 -115967 0 0x40d5df30)
Oh look at that.
Can you run it again, but before starting the application (run -v ...) set a
breakpoint on the line:
Richard Urwin wrote:
On Sunday 04 Jan 2004 5:10 pm, John Richard Smith wrote:
First off this is the instruction as per source code debug readme:-
B.4.6.1 How to conserve information about a reproducible crash
Recompile MPlayer with debugging code enabled:
./configure --enable-debug=3
make
and t
On Sunday 04 Jan 2004 11:29 pm, John Richard Smith wrote:
> (gdb) run -v mencoder dvd://1 -ovc lavc -lavcopts
> vcodec=mpeg4:vhq:vbitrate=1024 -oac mp3lame -lameopts br=96:cbr -alang
> en -idx -o toystory1.avi
Looking closer, you probably want
(gdb) run -v dvd://1 -ovc lavc -lavcopts
vcodec=mpe
On Sunday 04 Jan 2004 11:29 pm, John Richard Smith wrote:
> (gdb) run -v mencoder dvd://1 -ovc lavc -lavcopts
> vcodec=mpeg4:vhq:vbitrate=1024 -oac mp3lame -lameopts br=96:cbr -alang
> en -idx -o toystory1.avi
>
> and I suppose it's going to start a rip file inside directory sources, yes
> ? if so
Richard Urwin wrote:
On Sunday 04 Jan 2004 9:58 pm, John Richard Smith wrote:
$ gdb ./mencoder
(gdb) run -v [options to mencoder]
and reproduce the crash.
Then give the following commands:
backtrace
disass $pc-32 $pc+32
info all-registers
info threads
(gdb) gdb ./mencoder
Undefined com
On Sunday 04 Jan 2004 9:58 pm, John Richard Smith wrote:
> >$ gdb ./mencoder
> >(gdb) run -v [options to mencoder]
> >
> >and reproduce the crash.
> >
> >Then give the following commands:
> >backtrace
> >disass $pc-32 $pc+32
> >info all-registers
> >info threads
>
> (gdb) gdb ./mencoder
> Undefine
Richard Urwin wrote:
On Sunday 04 Jan 2004 5:10 pm, John Richard Smith wrote:
First off this is the instruction as per source code debug readme:-
B.4.6.1 How to conserve information about a reproducible crash
Recompile MPlayer with debugging code enabled:
./configure --enable-debug=3
make
and t
On Sunday 04 Jan 2004 5:10 pm, John Richard Smith wrote:
> First off this is the instruction as per source code debug readme:-
> B.4.6.1 How to conserve information about a reproducible crash
> Recompile MPlayer with debugging code enabled:
> ./configure --enable-debug=3
> make
> and then run MPlay
Richard Urwin wrote:
Then when you run it under gdb,
Or are you saying after the ./confure , and make, but before make
install, run gdb on the install file which lies somewhere in the source
directory ?
OK so I have to recompile with the debug options and then gdb the
make file in directory sourc
Richard Urwin wrote:
On Sunday 04 Jan 2004 10:07 am, John Richard Smith wrote:
Richard Urwin wrote:
You have tried the -idx flag to mencoder?
Oh gosh yes, always include it without fail,
Not quite:
On Saturday 03 Jan 2004 6:44 pm, John Richard Smith wrote:
> Core was generate
On Sunday 04 Jan 2004 10:07 am, John Richard Smith wrote:
> Richard Urwin wrote:
> >You have tried the -idx flag to mencoder?
>
> Oh gosh yes, always include it without fail,
Not quite:
On Saturday 03 Jan 2004 6:44 pm, John Richard Smith wrote:
> Core was generated by `mencoder dvd://1 -ovc la
Richard Urwin wrote:
On Sunday 04 Jan 2004 12:25 am, John Richard Smith wrote:
Now I have some
reason to suppose that it is an issue to do with how mencoder rips AC3
sound, which is dolby's surround sound. Sometimes it makes a dogs
breakfast of encoding and creating the all important index file
Richard Urwin wrote:
On Saturday 03 Jan 2004 6:44 pm, John Richard Smith wrote:
#0 0x081b5fb8 in ff_combine_frame ()
(gdb)
---
later
=
I should of read your email more carefully
#0 0x081b5fb8 in ff_combine_frame ()
(gdb) back
On Saturday 03 Jan 2004 6:44 pm, John Richard Smith wrote:
> #0 0x081b5fb8 in ff_combine_frame ()
> (gdb)
> ---
> later
> =
> I should of read your email more carefully
>
> #0 0x081b5fb8 in ff_combine_frame ()
> (gdb) backtrace
>
Richard Urwin wrote:
If you use:
gdb -core=core.7674 /usr/bin/mencoder
(or whereever mencoder lives on your system)
Wow,
bear with me this is all new experience for me.
so this is what I did,
[EMAIL PROTECTED] root]# cd /mnt/ext2-vol6/downloads2/divx
[EMAIL PROTECTED] divx]# ls
core.18439 core.31
Richard Urwin wrote:
If you use:
gdb -core=core.7674 /usr/bin/mencoder
(or whereever mencoder lives on your system)
Wow,
bear with me this is all new experience for me.
so this is what I did,
[EMAIL PROTECTED] root]# cd /mnt/ext2-vol6/downloads2/divx
[EMAIL PROTECTED] divx]# ls
core.18439 core.31
On Friday 02 Jan 2004 11:32 pm, John Richard Smith wrote:
> so when you get through the pre-amble it doesn't say much really,but,
> Core was generated by `mencoder dvd://1 -ovc lavc -lavcopts
> vcodec=mpeg4:vhq:vbitrate=1024 -oac mp3lam'.
> Program terminated with signal 11, Segmentation fault.
> #
Ronald J. Hall wrote:
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
Ronald J. Hall wrote:
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
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
Richard Urwin wrote:
On Friday 02 Jan 2004 5:30 pm, Ronald J. Hall wrote:
On Friday 02 January 2004 11:59 am, John Richard Smith wrote:
-> When you get a core dump, what can you then do to read it ?
->
Have you tried:
gdb -core=3D
I don't see why the 3D.
Try gdb -core=core
Without the exe
On Friday 02 Jan 2004 5:30 pm, Ronald J. Hall wrote:
> On Friday 02 January 2004 11:59 am, John Richard Smith wrote:
> -> When you get a core dump, what can you then do to read it ?
> ->
>
> Have you tried:
>
> gdb -core=3D
I don't see why the 3D.
Try gdb -core=core
Without the executable file th
On Friday 02 January 2004 12:53 pm, John Richard Smith wrote:
-> "i586-mandrake-linux-gnu"..."/mnt/ext2-vol6/downloads2/divx/core.7674":
-> not in executable format: File format not recognized
->
-> Attaching to process 3
-> ptrace: Operation not permitted.
-> /mnt/ext2-vol6/downloads2/divx/3D: No
Ronald J. Hall wrote:
On Friday 02 January 2004 11:59 am, John Richard Smith wrote:
-> When you get a core dump, what can you then do to read it ?
->
Have you tried:
gdb -core=3D
Lets see now,
[EMAIL PROTECTED] root]# cd /mnt/ext2-vol6/downloads2/divx
[EMAIL PROTECTED] divx]# ls
core.7674 d
On Friday 02 January 2004 11:59 am, John Richard Smith wrote:
-> When you get a core dump, what can you then do to read it ?
->
Have you tried:
gdb -core=3D
--
/\
When you get a core dump, what can you then do to read it ?
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
On Sun, 24 Oct 1999, you wrote:
> On Sat, Oct 23, 1999 at 10:10:46PM -0400, John Aldrich wrote:
> > On Sat, 23 Oct 1999, you wrote:
> > > What is a core dump??? and why do you get them???
> > >
> > Core dump is a memory dump of a crashed program. Instead of a "blue
> > screen of death" like you ge
On Sat, Oct 23, 1999 at 10:10:46PM -0400, John Aldrich wrote:
> On Sat, 23 Oct 1999, you wrote:
> > What is a core dump??? and why do you get them???
> >
> Core dump is a memory dump of a crashed program. Instead of a "blue
> screen of death" like you get with Microsoft, you get a "core dump"
Now
I noticed them after trying to install a GZIP proggy
[EMAIL PROTECTED] wrote:
> On Sat, Oct 23, 1999 at 12:27:51PM -0400, Jaguar wrote:
> > What is a core dump??? and why do you get them???
>
> A core dump is a dump of the system memory to allow debugging of a broken
> application.
>
> Why
On Sat, 23 Oct 1999, you wrote:
> What is a core dump??? and why do you get them???
>
Core dump is a memory dump of a crashed program. Instead of a "blue
screen of death" like you get with Microsoft, you get a "core dump"
when a program fails. Also, the nice thing about Linux is that the
PROGRAM f
On Sat, Oct 23, 1999 at 12:27:51PM -0400, Jaguar wrote:
> What is a core dump??? and why do you get them???
A core dump is a dump of the system memory to allow debugging of a broken
application.
Why do you get them? Programming errors. Yours, theirs, doesn't really
matter unless you don't have
What is a core dump??? and why do you get them???
TIA
Jaguar
Get your own FREE, personal Netscape WebMail account today at
http://webmail.netscape.com.
Thanx for the info guys. I'll be real carefull with this "core"
>> When something crashes or exits abnormally it may "core dump"...
>> I'm no expert but I think this is the programms way of trying to preserve
>> debugging or unsaved info? ..in anycase, you'll be left with a file
Suryo Mataram wrote:
>
> Hi all,
> I'm new with LINUX. Can anyone tell me what Core Dump is all about?
> Many thank's in advance.
>
> Suryo Mataram.
It means a program crashed and a map of memory has been saved
in order to detect the problem: the core file.
Unless you are a guru or the pro
- Original Message -
From: Alex Brown <[EMAIL PROTECTED]>
To: newbie <[EMAIL PROTECTED]>
Sent: Thursday, June 24, 1999 10:26 AM
Subject: Re: [newbie] Core Dump
> On Thu, 24 Jun 1999, Suryo Mataram wrote:
>
> > Hi all,
> > I'm new with LINUX. Can a
On Thu, 24 Jun 1999, Suryo Mataram wrote:
> Hi all,
> I'm new with LINUX. Can anyone tell me what Core Dump is all about?
> Many thank's in advance.
>
> Suryo Mataram.
>
>
When something crashes or exits abnormally it may "core dump"...
I'm no expert but I think this is the programms way
Hi all,
I'm new with LINUX. Can anyone tell me what Core Dump is all about?
Many thank's in advance.
Suryo Mataram.
50 matches
Mail list logo
