Opened 16 years ago

Closed 8 years ago

#3289 closed bug (fixed)

Tracker crash in _add

Reported by: Adek336 Owned by: axeld
Priority: normal Milestone: R1
Component: Applications/Tracker Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

_add _fmt strftime

Attachments (7)

img_1571.jpg (191.5 KB ) - added by Adek336 16 years ago.
img_1394.jpg (181.1 KB ) - added by Adek336 16 years ago.
img_1646.jpg (340.9 KB ) - added by Adek336 16 years ago.
img_1647.jpg (131.9 KB ) - added by Adek336 16 years ago.
img_1648.jpg (155.9 KB ) - added by Adek336 16 years ago.
tr-cr-5.txt (18.0 KB ) - added by Adek336 16 years ago.
img_1674.jpg (212.8 KB ) - added by Adek336 16 years ago.

Download all attachments as: .zip

Change History (18)

by Adek336, 16 years ago

Attachment: img_1571.jpg added

comment:1 by Adek336, 16 years ago

hrev28845, crashed right after booting up

comment:2 by Adek336, 16 years ago

Happened to me twice.

comment:3 by aldeck, 16 years ago

Is it a recent bug? Does it happen when a particular folder is open? It seems that it's your 'tcp' folder that crashed. If that's the case, anything particular about the files it contains?

by Adek336, 16 years ago

Attachment: img_1394.jpg added

comment:4 by Adek336, 16 years ago

Both crashes straight after bootup with hrev28845, I have booted up several times and only twice did the bug happen.

The tcp and ipv4 are the folders for the generated files under add-ons/kernel/network/protocols on /haiku-dane bfs partition. Each of them contains a handful of .o files and a kernel add-on.

Also opened are /boot/beos/system/add-ons/kernel/network, /boot/beos/system/add-ons/kernel/network/protocols and the kernel/network/stack generated folder.

In img_1394 also opened two directories from /haiku-dane containing symbolic links.

Before closing the debug window, only tcp folder in img_1571 and only the ipv4 folder in img_1394 were affected. After closing it, the whole team would quit.

by Adek336, 16 years ago

Attachment: img_1646.jpg added

by Adek336, 16 years ago

Attachment: img_1647.jpg added

by Adek336, 16 years ago

Attachment: img_1648.jpg added

comment:5 by Adek336, 16 years ago

This time crash not right after boot but after some time with vim. Slightly different backtrace. After quiting the userland debugger for Tracker, the userland debugger for app_server thread picasso appeared. img_1648.jpg additional backtrace of the thread gotten from kdl.

comment:6 by Adek336, 16 years ago

picasso crashed when I tried to reach the Deskbar or click Restart tracker in processcontroller, not right after quiting the previous debugger

comment:7 by aldeck, 16 years ago

I have no idea what could be going on. What hardware (emu?) are you testing with? Do you build from source? GCC2 or 4? Any special driver? Are you sure that it's a Tracker thread that crashes and that gdb attached to the correct thread (see #2956) ? From your screenshot, i'm missing the first lines and can't see what called the debugger, what's the error, segment violation? assert?

Regards

by Adek336, 16 years ago

Attachment: tr-cr-5.txt added

comment:8 by Adek336, 16 years ago

Real hardware, gcc2 build built from source, the correct thread seems to be attached to, it's a segment violation.

It looks like in http://haiku.it.su.se:8180/source/xref/src/system/libroot/posix/time/strftime.c, lines 200-206, Locale->month[t->tm_mon] evaluates to NULL.

by Adek336, 16 years ago

Attachment: img_1674.jpg added

comment:9 by aldeck, 16 years ago

Component: - GeneralApplications/Tracker
Summary: Tracker crash in _add after bootupTracker crash in _add

Seen it happen once, while downloading a file, on one of my tests machine (dual core) a few weeks ago, didn't have time to report. Setting component so it's not forgotten.

comment:10 by umccullough, 13 years ago

2 years is a long time - does this still occur?

comment:11 by waddlesplash, 8 years ago

Resolution: fixed
Status: newclosed

No reply in 6 years, assuming fixed.

Note: See TracTickets for help on using tickets.