GNOME.org
 

Re: [Evolution] Weird messages and lock ups in Evolution 1.4.4

I just downloaded the Evolution 1.4.5, however, I am still encountering some weirdness.  I used to experience the problem described in Bug 46512, but what I am encountering is something additional to the message being left in the local outbox.  However, it used to seem related since sometimes the message would be left in the outbox, sometimes it would be mangled, and sometimes it would work.


Here is the message source of an HTML formatted message that I sent earlier today with evo 1.4.5.  I should have used gdb and set camel verbose, but I didn't .... sorry.  As you can see the HTML is somehow busted.  It's as if the message is partially sent HTM, partially as text only. 



The message is mangled somehow during the transfer from the local machine to the IMAP machine.  When I use a local sent folder the problem has not occured (it might perhaps, but I have not noticed it).  This mangling sometimes occurs when I drag a message from the local folders to the IMAP folders, but it occurs most frequently when I am sending messages.

I am speculating that that it might occur when evolution is sending and receiving simultaneously.  Is evolution able to communicate to the server in full duplex mode? 

Let me know if I should submit this as a bug in your Bugzilla data base.


-----Start of Message
Subject: Status
From: Ian Perryman <iperryma altera com>
To: Curt Wortman <CWORTMAN altera com>
Cc: Glenn Henshaw <GHENSHAW altera com>, Hans van der Schoot <HVDSCHOO altera com>, Chris Thompson <CTHOMPSO altera com>, Desmond Ambrose <DAMBROSE altera com>
Content-Type: multipart/alternative; boundary="=-eA87hDGOY8NwXtBsRhM8"
Message-Id: <1064408872 756 54 camel otc-dr5a43 altera com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5
Date: Wed, 24 Sep 2003 09:07:52 -0400
X-Evolution-Transport: smtp://iperryma sunrise altera com
X-Evolution-Account: iperryma altera com
X-Evolution-Fcc: imap://iperryma otc-msg01/Sent%20Items
X-Evolution-Format: text/html
X-Evolution-Source: imap://iperryma otc-msg01/


--=-eA87hDGOY8NwXtBsRhM8
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Accomplishments

      * Updated status message classes to fit paradigm.
      * Updated SPI4 rx and tx BFM's to included status path with new
        classes.
      * Modified configuration objects to align with spec
      * Updated loopback test bench to use new BFM's.
      * Checked everything in when it compiled clean.  Still needs run
        time debug still



      * Arranged meeting with Jasper Design Automation to look at their
        new tool JasperGold.


Issues

      * Still no word on 0-In .... what's going on?
      *


To Do

      * Patent application ... Assertions in FPGA's for h/w/ debug.
      * Debug loopback test to test status messa     * Measure
functional coverage of existing ap179 test suite.
      * Measure functional coverage of vera random tests on ap179.
      * Compare results
       
              * how many vera tests required (how many different tests,
                seeds, etc.)
              * how much more coverage achieved.
              * any new bugs found?
              *

--
Ian Perryman <iperryma altera com>

--=-eA87hDGOYging
      * Need to create mechanism for tracking stable intermediate builds
        in CVS.
      * Need to implement resolutions for code reuse.
      * Arrange Vera Training for rest of OTC.

On Hold

      * Need to create system side bfm's for status path.
      * Need to create status scoreboard
      * BFM only supports regular status messages, it does not support
        hitless bandwidth reprovisioning.  Existing code should be
        capable of support changes without major changes.
      *


AP179 Vera Environment

Hans and Chris have the ap179 vera environment essentially complete (in
so far as stimulus generation and output monitoring).  Still some on
going work to automatically terminate simulations based on results.

To Do. 

      * Analyze test plan and define coverage elements.
      * Capture/debug coverage elements
      * Create regression script for Vera tests
      * Modify Vera test environment to allow standalone Verilog test to
        control DUT.
 8NwXtBsRhM8
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9">
</HEAD>
<BODY>
Accomplishments
<UL>
    <LI>Updated status message classes to fit paradigm.
    <LI>Updated SPI4 rx and tx BFM's to included status path with new
classes.
    <LI>Modified configuration objects to align with spec
    <LI>Updated loopback test bench to use new BFM's.
    <LI>Checked everything in when it compiled clean.&nbsp; Still needs
run time debug still
</UL>
<BR>
<UL>
    <LI>Arranged meeting with Jasper Design Automation to look at their
new tool JasperGold.
</UL>
<BR>
Issues
<UL>
    <LI>Still no word on 0-In .... what's going on?
    <LI>
</UL>
<BR>
To Do
<UL>
    <LI>Patent application ... Assertions in FPGA's for h/w/ debug.
    <LI>Debug loopback test to test status messaging
    <LI>Need to create mechanism for tracking stable intermediate builds
in CVS.
    <LI>Need to implement resolutions for code reuse.
    <LI>Arrange Vera Training for rest of OTC.
</UL>
On Hold
<UL>
    <LI>Need to create system side bfm's for status path.
    <LI>Need to create status scoreboard
    <LI>BFM only supports regular status messages, it does not support
hitless bandwidth reprovisioning.&nbsp; Existing code should be capable
of support changes without major changes.
    <LI>
</UL>
<BR>
AP179 Vera Environment <BR>
<BR>
Hans and Chris have the ap179 vera environment essentially complete (in
so far as stimulus generation and output monitoring).&nbsp; Still some
on going work to automatically terminate simulations based on
results.<BR>
<BR>
To Do.&nbsp;
<UL>
    <LI>Analyze test plan and define coverage elements.
    <LI>Capture/debug coverage elements
    <LI>Create regression script for Vera tests
    <LI>Modify Vera test environment to allow standalone Verilog test to
control DUT.
    <LI>Measure functional coverage of existing ap179 test suite.
    <LI>Measure functional coverage of vera random tests on ap179.
    <LI>Compare results
    <BLOCKQUOTE>
        <LI>how many vera tests required (how many different tests,
seeds, etc.)
        <LI>how much more coverage achieved.
        <LI>any new bugs found?
        <LI>
    </BLOCKQUOTE>
</UL>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Ian Perryman &lt;<A
HREF="" altera com"><U>iperryma altera com</U></A>&gt;
</TD>
</TR>
</TABLE>

</BODY>
</HTML>

--=-eA87hDGOY8NwXtBsRhM8--


-----End of Message



Ian

On Thu, 2003-09-18 at 11:15, Jeffrey Stedfast wrote: 
we think this problem has been fixed in the latest snapshots (or 1.4.5
when it is released)

Jeff

On Wed, 2003-09-17 at 15:44, Ian Perryman wrote:
> I am using evo 1.4.4 on a RH8.0 machine.  I use red-carpet to update
> both.
>  
> I have evolution configured to connect to our Exchange server using
> IMAP, and I have sent messages stored in the IMAP "Sent"  folder
> rather than in the local folders that evolution created.
>  
> I just had some bad behaviour, and I have attached the output from the
> CAMEL-VERBOSE_DEBUG=1 log.
> The log also contains the "thread apply all bt" output where it hung.
>  
> The log has been reduced to the latest message being sent.  
>  
> The symptoms I observe are:
>  
> The message is sent correctly to the recipients.
>  
> When the message is being tranferred from the outbox to the sent
> folder I get intermittent behaviour.
>         Usually it works (Yeah !)
>         Sometimes it mangles the message in the sent folder
>         Less  frequently it hangs. Like this time.
> I am using Outlook to send this message.  I still have evolution
> suspended in gdb 
>  
> Thanks for any insight that you can give.
>  
> Ian Perryman
> 
--
Ian Perryman <iperryma altera com>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]