Hans de Graaff wrote:
> On Wed, 2006-04-26 at 22:24 +0200, Christian Biere wrote:
> > > 06-04-26 18:26:07 (CRITICAL): gtk_tree_path_next: assertion `path !=
> > > NULL' failed
[...]
> I get a lot of them every time I start Gtk-Gnutella. I also seem to get
> a bunch of them when I switch to see som
On Wed, 2006-04-26 at 22:24 +0200, Christian Biere wrote:
> > 06-04-26 18:26:07 (CRITICAL): gtk_tree_path_next: assertion `path !=
> > NULL' failed
> > 06-04-26 18:26:07 (CRITICAL): gtk_tree_path_up: assertion `path != NULL'
> > failed
> > 06-04-26 18:26:07 (CRITICAL): gtk_tree_path_next: assertio
Bill Pringlemeir wrote:
> I also remember I had a case without a core file. I think that a
> break point instructions was hit.
Unless you run Gtk-Gnutella in a debugger, a break point instruction
should cause a SIGTRAP and thus a core as well. For debugging
purposes you should disable "fast asser
On 26 Apr 2006, [EMAIL PROTECTED] wrote:
> Bill Pringlemeir wrote:
>> (gdb) bt
>>> 0 0x0811bdf3 in pcache_outgoing_connection (n=0xd59) at
>>> override.h:78 1 0x080fc20e in node_is_now_connected (n=0xd59)
>>> at nodes.c:3213
> It would be interesting to see the details of "n". So far I don
Bill Pringlemeir wrote:
> (gdb) bt
> #0 0x0811bdf3 in pcache_outgoing_connection (n=0xd59) at override.h:78
> #1 0x080fc20e in node_is_now_connected (n=0xd59) at nodes.c:3213
It would be interesting to see the details of "n". So far I don't see
how the assertion could trigger.
> Any req
I
wrote a crash agent, which allows any user, with gdb or dbx(Solaris) to
email a crash report when ever
a specified program crashes (Like Mozilla/Netscape crash agent). I'd
be willing to relicense it from BSD to GPL.
Even if the user doesn't have a debugger, it will email Gtk-GNUtellas
std
I wrote a crash agent, which allows any user, with gdb or dbx(Solaris)
to email a crash report when ever
a specified program crashes (Like Mozilla/Netscape crash agent). I'd be
willing to relicense it from BSD to GPL.
Even if the user doesn't have a debugger, it will email Gtk-GNUtellas
stdou
On 26 Apr 2006, [EMAIL PROTECTED] wrote:
> is anyone else seeing frequent crashes with the Gtk+ 2.x GUI? The
> stack traces always end in gtk_tree_view_get_hover_expand with
> a SIGSEGV and related to removing or reordering rows in the
> search results display. I doubt it's a bug in Gtk-Gnutella b
On 26 Apr 2006, [EMAIL PROTECTED] wrote:
> On Wednesday 26 April 2006 18:13, Christian Biere wrote:
>> is anyone else seeing frequent crashes with the Gtk+ 2.x GUI?
> ...
>> it just happens sooner or later e.g., when
>> I close a search,
>
> I have also had some crashes in the past months which I c
Hans de Graaff wrote:
> No crashes, but I do get a lot of warnings:
> 06-04-26 18:26:07 (CRITICAL): gtk_tree_path_next: assertion `path !=
> NULL' failed
> 06-04-26 18:26:07 (CRITICAL): gtk_tree_path_up: assertion `path != NULL'
> failed
> 06-04-26 18:26:07 (CRITICAL): gtk_tree_path_next: assert
On Wed, 2006-04-26 at 18:52 +0200, Haxe wrote:
> On Wednesday 26 April 2006 18:13, Christian Biere wrote:
> > is anyone else seeing frequent crashes with the Gtk+ 2.x GUI?
> ...
> > it just happens sooner or later e.g., when
> > I close a search,
>
> I have also had some crashes in the past months
On Wednesday 26 April 2006 18:13, Christian Biere wrote:
> is anyone else seeing frequent crashes with the Gtk+ 2.x GUI?
...
> it just happens sooner or later e.g., when
> I close a search,
I have also had some crashes in the past months which I couldn't
reproduce. It seemed to only happen in the
Hi,
is anyone else seeing frequent crashes with the Gtk+ 2.x GUI? The
stack traces always end in gtk_tree_view_get_hover_expand with
a SIGSEGV and related to removing or reordering rows in the
search results display. I doubt it's a bug in Gtk-Gnutella but
this doesn't seem to be a known bug in Gtk
13 matches
Mail list logo
