Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Livestation seg faults

  1. #1
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Livestation seg faults

    Livestation <http://www.livestation.com/> is a TV player client,
    allowing connection to several international news streams
    (video/audio) from around the world..

    it is available for Linux, Mac as well as pervasive game systems..
    it ran ok in 10.3 but seg faults in 11.3..

    after manually tinkering with its audio setup in ~/.openalrc it runs
    good here until the seg fault...sometime it runs five minutes,
    sometimes 25 minutes or more...i have been unable to detect the
    triggering event..

    started by executing 'livestation' in an open terminal always results
    (eventually) in "Segmentation fault" and nothing else as the client
    disappears..

    anyone else seen this?
    or, running with no problems?

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  2. #2
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: Livestation seg faults

    On 02/18/2011 07:31 PM, DenverD wrote:
    > started by executing 'livestation' in an open terminal always results
    > (eventually) in "Segmentation fault" and nothing else as the client
    > disappears..


    however, /var/messages captures:


    Code:
    Feb 19 17:49:57 linux kernel: [37842.688024] DMA write timed out
    Feb 19 17:51:07 linux kernel: [37912.736039] parport0: FIFO is stuck
    Feb 19 17:51:07 linux kernel: [37912.784049] parport0: BUSY timeout
    (1) in compat_write_block_pio
    Feb 19 17:51:17 linux kernel: [37922.784024] DMA write timed out
    Feb 19 17:52:27 linux kernel: [37992.800030] parport0: FIFO is stuck
    Feb 19 17:52:27 linux kernel: [37992.848031] parport0: BUSY timeout
    (1) in compat_write_block_pio
    Feb 19 17:52:37 linux kernel: [38002.848025] DMA write timed out
    Feb 19 17:53:47 linux kernel: [38072.868036] parport0: FIFO is stuck
    Feb 19 17:53:47 linux kernel: [38072.916122] parport0: BUSY timeout
    (1) in compat_write_block_pio
    Feb 19 17:53:57 linux kernel: [38082.916046] DMA write timed out
    Feb 19 17:55:07 linux kernel: [38152.155847] show_signal_msg: 6
    callbacks suppressed
    Feb 19 17:55:07 linux kernel: [38152.155858] Livestation.bin[11749]:
    segfault at 28 ip b089a63c sp bff61b40 error 6 in
    libgdk_pixbuf-2.0.so.0.2000.1[b0894000+1d000]
    Feb 19 17:55:07 linux kernel: [38152.928040] parport0: FIFO is stuck
    Feb 19 17:55:07 linux kernel: [38152.976018] parport0: BUSY timeout
    (1) in compat_write_block_pio
    Feb 19 17:55:17 linux kernel: [38162.976026] DMA write timed out
    Feb 19 17:56:09 linux su: (to root) denverd on /dev/pts/3
    Feb 19 17:56:28 linux kernel: [38233.012024] parport0: FIFO is stuck
    Feb 19 17:56:28 linux kernel: [38233.060036] parport0: BUSY timeout
    (1) in compat_write_block_pio
    Feb 19 17:56:38 linux kernel: [38243.060031] DMA write timed out
    with the FIFO and BUSY stuck continuing afterward, so i guess that is
    not part of this problem (any idea how to solve the livestation OR
    FIFO problem?)

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  3. #3
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: Livestation seg faults

    On 02/19/2011 06:08 PM, DenverD wrote:
    > with the FIFO and BUSY stuck continuing afterward, so i guess that is
    > not part of this problem


    the FIFO problem was a print job trying to run...killed, and the
    'problem' died too..



    > any idea how to solve the livestation ... FIFO problem?


    still open.

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  4. #4

    Default Re: Livestation seg faults

    Hi,

    doesn't a segfault cause the program to do a core dump?

    perhaps you'll find more info in that?

    HTH

    Lenwolf

  5. #5
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: Livestation seg faults

    On 02/19/2011 07:36 PM, lenwolf wrote:
    >
    > doesn't a segfault cause the program to do a core dump?


    tell me more...where should i look?

    i've not been able to find a debug pack for Livestation..

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  6. #6

    Default Re: Livestation seg faults

    Hi

    In most cases it'ill be called core or core.[PID] where [PID] will have been replaced with the process ID of the process that dumped.
    (check that first with , eg, top)0
    It's located in var/crash/

    HTH

    Lenwolf

  7. #7
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: Livestation seg faults

    On 02/19/2011 08:36 PM, lenwolf wrote:
    >
    > It's located in var/crash/


    this from tail messages:

    Code:
    Feb 19 20:46:42 linux kernel: [ 9396.061697] show_signal_msg: 6
    callbacks suppressed
    Feb 19 20:46:42 linux kernel: [ 9396.061708] Livestation.bin[8022]:
    segfault at 28 ip b002863c sp bf802340 error 6 in libgdk_pixbuf-2.0.
    but /var/crash remains empty..
    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  8. #8

    Default Re: Livestation seg faults

    Hi,
    Then it seems that it doesn't produce a core dump, darn.

    It *could* also be in the current working dir when the program crashes.

    Do you think you could look at "man 5 core" to see where else the program might have dumped its core dump?



    Lenwolf

  9. #9
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: Livestation seg faults

    On 02/20/2011 10:36 AM, lenwolf wrote:
    >
    > Then it seems that it doesn't produce a core dump, darn.


    i'm not a programmer so i do not know for sure, but i do not believe
    it is routine for executables to produce a "core dump" unless they
    have been programmed to do so..


    > It *could* also be in the current working dir when the program
    > crashes.


    the executable is in /usr/bin and i think it would be quite rude to
    plop a core dump there, don't you?


    > Do you think you could look at "man 5 core" to see where else the
    > program might have dumped its core dump?


    'man 5 core' returns "No manual entry for core in section 5"

    i have been unable to find anything that might look like a "core dump"
    in /tmp, or /var/tmp, or /var/crash

    i have logged a bug with livestation.com and await their
    reply...perhaps they send a version with debug routines built in..

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  10. #10

    Default Re: Livestation seg faults

    Hi,

    now htat id=s definitely struange.

    "man 5 core" definitely gives me a large output.

    This is crazy.

    I've posted it at CORE(5) Linux Programmer's Manu. Perhaps that helps you.

    HTH

    Lenwolf

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •