From: "Tomáš Čech" <tcech@suse.com>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: WIP: neomutt. segfaulting outside of gdb, functional inside.
Date: Wed, 3 Aug 2016 15:10:23 +0200 [thread overview]
Message-ID: <20160803131023.GA9060@venom> (raw)
In-Reply-To: <87k2fyxckk.fsf@we.make.ritual.n0.is>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
On Wed, Aug 03, 2016 at 12:27:07PM +0000, ng0 wrote:
>Tomáš Čech <sleep_walker@gnu.org> writes:
>
>> On Fri, Jun 24, 2016 at 04:04:43PM +0000, ng0 wrote:
>>>In gnu/packages/mail.scm I created this package.
>>>It builds succesfully, but when I run it, it segfaults.
>>>Running it in gdb however makes it succeed and not
>>>segfault. How do I debug such a software?
>>
>> I applied the patch and built neomutt. Works for me. I'd commit your
>> patch and solve your issue as bug.
>>
>> S_W
>The latest version of the patch with the more recent neomutt version?
Yes. /gnu/store/bx3krsvdq3n9l3y8awdvm4kzm5zbz237-neomutt-20160723/
>I had no time to further debug this.
>Do you mean my runtime problem is unique and you were able to run and
>use it without segfault?
Yes. It may be related to your configuration, I haven't had a problem.
S_W
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-03 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 16:04 WIP: neomutt. segfaulting outside of gdb, functional inside ng0
2016-06-27 7:58 ` Ricardo Wurmus
2016-06-29 9:54 ` Florian Paul Schmidt
2016-07-26 15:17 ` [PATCH] gnu: Add neomutt ng0
2016-07-26 15:22 ` ng0
2016-07-26 17:12 ` ng0
2016-07-26 18:47 ` WIP: neomutt. segfaulting outside of gdb, functional inside Tomáš Čech
2016-07-29 14:56 ` ng0
2016-07-31 10:52 ` Danny Milosavljevic
2016-08-03 10:30 ` Tomáš Čech
2016-08-03 12:27 ` ng0
2016-08-03 13:10 ` Tomáš Čech [this message]
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=20160803131023.GA9060@venom \
--to=tcech@suse.com \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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).