From: James Prestwood <prestwoj@gmail.com>
To: Michael John <MJohn@midmark.com>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: Segmentation fault
Date: Mon, 21 Aug 2023 05:50:37 -0700 [thread overview]
Message-ID: <56209aa3-d9dc-4199-b1ff-d81866cdc977@gmail.com> (raw)
In-Reply-To: <fa11a71a-42ff-4c54-9f0d-e8635e0782b5@gmail.com>
On 8/21/23 5:13 AM, James Prestwood wrote:
> Hi Michael,
>
> If this is a debug-enabled dump could you just post the stack trace?
> That way it won't require people log in to MS to see it. If not, how big
> is the file? We may want to figure out another way to share it.
In addition, I tried logging in and was unauthorized.
>
> Thanks,
> James
>
> On 8/21/23 5:09 AM, Michael John wrote:
>> Hello,
>>
>> I hit a segmentation fault with iwd version 2.7, and captured a
>> coredump. I've attached it at my onedrive below, please let me know if
>> you need more information.
>>
>> https://midmark-my.sharepoint.com/:u:/r/personal/mjohn_midmark_com/Documents/core.iwd.0.a68e5068b8214b27904b0fc85601ac35.241.1692277585000000?csf=1&web=1&e=4NPwg3
>>
>> Thanks,
>> -Michael John
>> CONFIDENTIALITY NOTICE: This message, including any attachments,
>> contains confidential information intended for a specific individual
>> and purpose. If you are not the intended recipient, you should delete
>> this message and any disclosure, copying, or distribution of this
>> message, or the taking of any action based on it, by you is strictly
>> prohibited.
>>
prev parent reply other threads:[~2023-08-21 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 12:09 Segmentation fault Michael John
2023-08-21 12:13 ` James Prestwood
2023-08-21 12:50 ` James Prestwood [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56209aa3-d9dc-4199-b1ff-d81866cdc977@gmail.com \
--to=prestwoj@gmail.com \
--cc=MJohn@midmark.com \
--cc=iwd@lists.linux.dev \
/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.
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).