Package: newsbeuter
Version: 1.3-1.0.0.clark.0
Followup-For: Bug #498377

I rebuild newsbeuter 1.3-1 with debug symbols and I'm seeing a very
similar segfault.  Here's the backtrace:

(gdb) bt
#0  0x00007fc4847dd06b in ?? () from /lib/libc.so.6
#1  0x00000000004361c2 in newsbeuter::rss_item::pubDate (
    this=<value optimized out>) at src/rss.cpp:101
#2  0x000000000045ecf9 in newsbeuter::itemview_formaction::prepare (
    this=0x2240ad0) at src/itemview_formaction.cpp:95
#3  0x0000000000420abd in newsbeuter::view::run (this=0x7fff8e18aff0)
    at src/view.cpp:161
#4  0x000000000042db10 in newsbeuter::controller::run
(this=0x7fff8e18af10, 
    argc=1, argv=0x7fff8e18b158) at src/controller.cpp:445
#5  0x00000000004089a1 in main (argc=1, argv=0x7fff8e18b158)
    at newsbeuter.cpp:24

I am running against a modified libmrss with the patch in bug #503225
applied but this seems to be unrelated.

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages newsbeuter depends on:
ii  libc6               2.7-16               GNU C Library: Shared libraries
ii  libcurl3-gnutls     7.18.2-7             Multi-protocol file transfer libra
ii  libgcc1             1:4.3.2-1            GCC support library
ii  libmrss0 [libmrss-a 0.19.2-1.0.0.clark.1 C library for parsing, writing and
ii  libncursesw5        5.7+20081129-1       shared libraries for terminal hand
ii  libnxml0 [libnxml-a 0.18.3-2             C library for parsing, writing and
ii  libsqlite3-0        3.5.9-6              SQLite 3 shared library
ii  libstdc++6          4.3.2-1              The GNU Standard C++ Library v3

newsbeuter recommends no packages.

newsbeuter suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to