#40 Crash after sorting Uploads on Status

[WvV]

When I sort the entries on the Uploads window by
clicking the Status column. And after that select 'Clear
Finished' and 'Clear Aborted', WinLopster 1.2.2 crashes
everytime I tested this. When I tested this there were
severall items on the Uploads window with different
statuses...

[Daniel K. O.]

Logged In: YES
user_id=472304

I can't reproduce this problem on the CVS version (there's
no change on that part of the code).

Does it happen with the version with debugging info? It
could be a problem with the compilation (aka MinGW bug). The
binary without debugging info is released with "-O2
-fexpensive-optimizations", it sometimes reveals both
compiler erros and programming errors.
What OS are you using?
How much [winlop] uptime?
How big is the upload list you are sorting?
Are there files in the upload list with non-ascii chars?
(GTK+ 1.3 is a b**ch with non-ascii chars)
Does it also happen when sorting and no item were cleared
before?
Does it happen if you aren't using any theme?
Can you try using DrMingw (or any jit debugger) to find out
where it's crashing?

[WvV]

Logged In: YES
user_id=1043873

It happens with the regular 1.2.2 0.10 version (I'm not using
the version with debugging info).

I'm using WinXPsp1.

Uptime doesn't mather, I first noticed it with more then 1000
hours uptime. But I also noticed it after a few hours uptime.

The upload list was between 15 and 25 entries I think.

All filenames in the list only contained ascii characters, I don't
have files with non-ascii chars in my share.

I don't know about the theme, I never configured one, does
winlop use a default one?

I'll look into the debugger question later...

[WvV]

Logged In: YES
user_id=1043873

The output of DrMingw is in the attachment. I hope this helps
because there isn't much information on lopster code in it,
probably because I'm not using the version with debug info in
it.

Btw: This time I tried 'Clear Finished' and 'Clear Aborted', the
other way around, so 'Clear Aborted' first. It again crashed on
the second 'Clear ...'. So the order doesn't seem to mather.

[WvV]

[Daniel K. O.]

Logged In: YES
user_id=472304

I still can't reproduce this bug. Could you please test it
with the latest CVS-20050215 snapshot release?

[WvV]

Logged In: YES
user_id=1043873

Yes it still crashes. I had only two finished uploads in the
upload tab this time.

Here's the debug output:

lopster.exe caused an Access Violation at location 6dc2a494
in module libgtk-0.dll Reading from location 42b60f3a.

Registers:
eax=01990ad0 ebx=42b60f3a ecx=00000000 edx=00000000
esi=00000001 edi=01990ad0
eip=6dc2a494 esp=0022ebc0 ebp=0022ebf8 iopl=0 nv up
ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00000206

Call stack:
6DC2A494 libgtk-0.dll:6DC2A494 gtk_clist_undo_selection
6DC2ADE3 libgtk-0.dll:6DC2ADE3 gtk_clist_undo_selection
6DC8A6B4 libgtk-0.dll:6DC8A6B4 gtk_marshal_NONE__NONE
6DCC5287 libgtk-0.dll:6DCC5287
gtk_signal_add_emission_hook_full
6DCC4812 libgtk-0.dll:6DCC4812
gtk_signal_connect_object_while_alive
6DCC2AC0 libgtk-0.dll:6DCC2AC0 gtk_signal_emit_by_name
6DC2A7CF libgtk-0.dll:6DC2A7CF gtk_clist_undo_selection
6DC2FC39 libgtk-0.dll:6DC2FC39 gtk_clist_set_sort_type
6DC1D6C1 libgtk-0.dll:6DC1D6C1 gtk_clist_thaw
00410D4E lopster.exe:00410D4E on_button241_clicked
callbacks.c:3586
void on_button241_clicked(
GtkButton * button = &(indirect),
gpointer user_data =
)
6DC8A6B4 libgtk-0.dll:6DC8A6B4 gtk_marshal_NONE__NONE
6DCC5287 libgtk-0.dll:6DCC5287
gtk_signal_add_emission_hook_full
6DCC4812 libgtk-0.dll:6DCC4812
gtk_signal_connect_object_while_alive
6DCC26C0 libgtk-0.dll:6DCC26C0 gtk_signal_emit
6DC0F8F4 libgtk-0.dll:6DC0F8F4 gtk_button_clicked
6DC117B3 libgtk-0.dll:6DC117B3 gtk_button_get_relief
6DC8A6B4 libgtk-0.dll:6DC8A6B4 gtk_marshal_NONE__NONE
6DCC46E0 libgtk-0.dll:6DCC46E0
gtk_signal_connect_object_while_alive
6DCC26C0 libgtk-0.dll:6DCC26C0 gtk_signal_emit
6DC0F814 libgtk-0.dll:6DC0F814 gtk_button_released
6DC10EFA libgtk-0.dll:6DC10EFA gtk_button_get_relief
6DC8A442 libgtk-0.dll:6DC8A442 gtk_marshal_BOOL__POINTER
6DCC4848 libgtk-0.dll:6DCC4848
gtk_signal_connect_object_while_alive
6DCC26C0 libgtk-0.dll:6DCC26C0 gtk_signal_emit
6DD0BDEC libgtk-0.dll:6DD0BDEC gtk_widget_event
6DC895F9 libgtk-0.dll:6DC895F9 gtk_main_do_event
6DC891A4 libgtk-0.dll:6DC891A4 gtk_main_do_event
67FA4003 libgdk-0.dll:67FA4003 gdk_flush
1001815F libglib-2.0-0.dll:1001815F g_main_depth
10018C58 libglib-2.0-0.dll:10018C58 g_main_context_dispatch
10018EFF libglib-2.0-0.dll:10018EFF g_main_context_dispatch
100193A2 libglib-2.0-0.dll:100193A2 g_main_loop_run
6DC88D84 libgtk-0.dll:6DC88D84 gtk_main
004B8D9D lopster.exe:004B8D9D main main.c:229
int main(
int argc = 1,
char * * argv = &0x00f83c59
)
004011E7 lopster.exe:004011E7
00401238 lopster.exe:00401238
77E8141A kernel32.dll:77E8141A GetCurrentDirectoryW

[Daniel K. O.]

Logged In: YES
user_id=472304

Thanks, now this crash report was much more useful. It seems
a problem with gtk_clist_thaw(); I'll see what I can do to
work around it.