On Mon, Apr 28, 2008 at 12:43 AM, Robins Tharakan <tharakan(at)gmail(dot)com> wrote:
> When we right click on the last row of a grid with very few rows (about
> 10-20), the application crashes to a halt with 'segmentation fault'.
> I am unable to find a good solution, but of what I understand,
> thread->IsRunning() fails when the thread is not actually running. Oddly,
> this happens only for small tables and not for those containing greater than
> ... say 50-100 rows.
> I tried the condition (thread & thread->IsRunning) and that fails too. Also
> (thread->IsAlive()) meets with the same fate. How can we check whether the
> thread is actually executing something or not, without actually causing a
> segfault for such cases ?
> If we remove this check altogether, this problem obviously gets resolved,
> but of course, pgAdmin would then certainly crash if the user requests two
> table refreshes back-to-back in quick succession.
> Could anyone hint at what is the possible cause / solution to this issue ?
> I am using v7237 (1.9 branch).
There are some nasty hacks in the debugger code to work around what
I've only been able to pin down as 'issues' in the wxWidgets threading
code. I wouldn't be at all surprised if you're seeing something
similar here - unfortunately I think the only thing you can do is get
far more familiar with GDB than anyone should ever have to :-(
EnterpriseDB UK: http://www.enterprisedb.com
In response to
pgadmin-hackers by date
|Next:||From: svn||Date: 2008-04-29 08:40:42|
|Subject: SVN Commit by dpage: r7238 - trunk/pgadmin3|
|Previous:||From: Erwin Brandstetter||Date: 2008-04-28 18:44:39|
|Subject: Refresh issue in object tree|