It seems to work again, I don't know what the problem really was.
Cheers,
Tomasz
Hi,
I've hit this a few days ago. Twidge segfaults on any
command that uses network, I think.
Here is a gdb session (sorry, twidge has no debug symbols):
$ gdb twidge
Reading symbols from twidge...(no debugging symbols found)...done.
(gdb) run lsrecent
Starting program: /usr/bin/twidge lsrecent
[
Hi
I ran with -d and the output shows the request with OK Response and the
Twits List. At the end returns
Segmentation Fault.
The output is attached
On Thu, Jun 12, 2014 at 11:41 AM, John Goerzen
wrote:
> Please run with -d and capture debugging info
>
>
> On 06/11/2014 10:25 PM, Josue Ortega
Please run with -d and capture debugging info
On 06/11/2014 10:25 PM, Josue Ortega wrote:
> Package: twidge
> Version: 1.1.0
> Severity: important
> Tags: upstream
>
> Dear Maintainer,
>
> While running "twidge lsrecent" or "twidge lsreplies" returns a Segmentation
> Fault.
>
> I am sorry if I di
Package: twidge
Version: 1.1.0
Severity: important
Tags: upstream
Dear Maintainer,
While running "twidge lsrecent" or "twidge lsreplies" returns a Segmentation
Fault.
I am sorry if I didn't bring more technical information but I have no experience
with Haskell.
Hope this report will be helpful.
5 matches
Mail list logo
