From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 8110437 for ecs-isp@2rosenthals.com; Thu, 12 Oct 2023 11:39:01 -0400 Received: from [192.168.200.201] (port=59776 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.96) (envelope-from ) id 1qqxly-0005Wb-33 for ecs-isp@2rosenthals.com; Thu, 12 Oct 2023 11:38:51 -0400 Received: from mta-101a.earthlink-vadesecure.net ([51.81.61.60]:39027) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1qqxlv-000107-2k for ecs-isp@2rosenthals.com; Thu, 12 Oct 2023 11:38:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=Bx5yhf52cXv1P28ZbNfWvXaVkaReCIbxQsV0V2 NHYS8=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1697125127; x=1697729927; b=Ux9+tmJhHygQHOHf8mLJ3XQTRgOUR5Bx80uP9uCXukC1YhL5YsRAlPc +RVrIpwcWNtv12on5tPiXlX4MsEtfeVuyNNNeMBip49BX2RL8xs44VPn+L15WjXXT5YQzg0 50d/Iq3XqcEz64usv/MAVj1D/kF1sdaQGo3gDPO/gmZEc/pw0Q++9pJVl+hjy7Sb+TjmH2e q9EAF8kcSami343te4N4Zhze3or9ggXgWgwfrnLJKAbeMUbYmBP4V/xwKV6MuQRSK8frgL9 aJaU8bR82MYvS5X13t4ahj70Cx4zKdJa4bGuLut2IHwVLeS6OPijQDMJDLT4qV2JFAJ2Hdn HUw== Received: from slamain ([108.193.253.247]) by vsel1nmtao01p.internal.vadesecure.com with ngmta id c3af833f-178d664faf5bad97; Thu, 12 Oct 2023 15:38:47 +0000 Message-ID: <65281dca.2.mr2ice.fgrirsq@earthlink.net> Date: Thu, 12 Oct 2023 08:24:42 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] ClamAV X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 10/12/23 at 10:12 AM, "Massimo S." said: HI Massimo, >No, except to ask Paul to compile a (debug) build with symbolics. So you do know the answer. >I can >only solve the issue by myself when there are no .xqs files using >"mapxqs" tool. That is not really a viable solution for complex apps. As has been explained many times, a build with debug data in the executable is generally better than using an .xqs file or a .sym file. If all you have is an .xqs file or a .sym file, it's what you will have to use. However, the problem with these files is that they include only global symbols. For complex apps like ClamAV, which contain lots of static functions, the exceptq report will be better than nothing, but may not be sufficient to analyze the failure. The lack of line number data also makes the analysis process much more tedious. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------