From: ng0 <ng0@we.make.ritual.n0.is>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnunet-svn, gnunet-gtk-svn
Date: Sat, 27 Aug 2016 13:20:11 +0000 [thread overview]
Message-ID: <87lgziqrg4.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <CAJ98PDxkH6f_RGfdhVvSxizOggsKR51ceFXKri2Le82qzOET9Q@mail.gmail.com>
Hi,
Catonano <catonano@gmail.com> writes:
> 2016-08-20 14:04 GMT+02:00 ng0 <ng0@we.make.ritual.n0.is>
>
>
>
>> Reported at https://gnunet.org/bugs/view.php?id=4619
>>
>>
> Christian Grothoff replied that he would like you to extract a stacktrace
> from a core dump.
>
> Did you notice ?
>
> I would attempt that myself but admittedly I don't know how to obtain a
> core dump
Yes I noticed it.
I follow my bugtickets but often I'm just occupied with multiple things
at the same time to reply in time.
I wanted to produce this today or at the beginning of next week.
Thanks
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-08-27 13:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 15:11 [PATCH] gnunet-svn, gnunet-gtk-svn ng0
2016-07-30 15:41 ` ng0
2016-07-30 15:56 ` ng0
2016-07-31 13:08 ` ng0
2016-08-01 14:34 ` ng0
2016-08-01 19:01 ` Catonano
2016-08-01 19:42 ` ng0
2016-08-01 22:21 ` Andreas Enge
2016-08-02 8:27 ` ng0
2016-08-02 10:30 ` ng0
2016-08-02 13:05 ` Catonano
2016-08-02 14:09 ` ng0
2016-08-02 14:57 ` Catonano
2016-08-02 15:31 ` ng0
2016-08-03 11:45 ` ng0
2016-08-03 12:05 ` Catonano
2016-08-03 21:10 ` Andreas Enge
2016-08-06 12:54 ` ng0
2016-08-06 23:43 ` ng0
2016-08-07 8:21 ` ng0
2016-08-18 13:27 ` Catonano
2016-08-18 14:15 ` ng0
2016-08-20 11:17 ` ng0
2016-08-20 12:04 ` ng0
2016-08-27 0:06 ` Catonano
2016-08-27 13:20 ` ng0 [this message]
2016-08-19 7:13 ` Alex Kost
2016-08-19 7:42 ` ng0
2016-08-25 11:36 ` ng0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgziqrg4.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=catonano@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).