From: Albert Berger <nbdspcl@gmail.com>
To: sox-devel@lists.sourceforge.net
Subject: Debugging SoX in MSVC
Date: Wed, 26 Sep 2018 04:19:55 +0300 [thread overview]
Message-ID: <20180926011954.GB27895@kw.merryville> (raw)
Hello,
probably this problem with SoX code (or rather with MSVC debugger)
is known and there is a solution, but I could not find it on the Web.
The problem is that MSVC 2015 debugger seems to get confused with
multiple definitions of 'priv_t' structure in many source files and
doesn't show the correct fields for instances of different variations
of this structure. I tried to set the flag "Compile as C" and a
different debug information format, but to no avail.
Could someone advise how this difficulty can be overcome?
Thanks.
/Al
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
reply other threads:[~2018-09-26 1:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180926011954.GB27895@kw.merryville \
--to=sox-devel@lists.sourceforge.net \
/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://80x24.org/mirrors/sox.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).