Latest Bugs & Tasks
Libnetapi currently lacks methods to get the system routing table.
Could be implemented in various places:
In the mailing list I proposed
status_t BNetworkInterface::GetRouteAt(int32 index, route_entry* entry)
but since the routing table isn't interface-specific, although a single route can of course be interface-specific, I think it could be implemented in BNetworkRoster as a single method
status_t BNetworkRoster::GetRoutingTable(const char* interfaceName, BObjectList<route_entry>*)
which would return a list of route_entry objects (or a more friendly class (BRoute?)), with the option of filtering by interface name, or even family.
Unfortunately I suspect we don't push the use of BObjectList in public api, so we'll need to use a BList here....
Other ideas ?
Should be fixed since hrev45436 (http://cgit.haiku-os.org/haiku/commit/?id=274b8be6c415dfb623f95ca9e4709c9f79836ae9) according to ticket:9591#comment:4
The debugger CLI's "threads" command currently lists a thread's state, but does not actually include the reason for the stopped state, i.e. the message passed to a deliberate debugger call. It needs to, especially for things like app_server crashes due to hitting an assert.
Again, BePDF is a third party app that is not part of Haiku's tree.
I appreciate this feature in the sense that it's a bit safer, but on the other hand, I wouldn't have lost nearly as much work due to the crashing bug if I were able to keep with the typical habit of saving every minute or so, which this safety feature prevents. Maybe there's a best-of-both worlds where it can rename the current file to " (copy 2)" or whatever and then save with the original filename whenever you hit Alt+S? That would make this much more useful, and even safer, for marking up PDFs.
For reference, this really isn't the right place for app-specific bugs like this. BePDF isn't part of the Haiku source tree, which is why it doesn't have a component under applications. It's actually located at http://sf.net/projects/bepdf, though I have no idea if it's still actively being developed.
- open a PDF file (e.g. simple.pdf)
- add a comment text annotation
- right-click, choose Properties, type "comment #1"
- save as simple2.pdf and close BePDF
- open simple2.pdf
- add a comment text annotation
- right-click, choose Properties, type "comment #2"
- save as simple3.pdf
Following these steps exactly, simple3.pdf is actually saved with both comments, but it still crashes (case 1).
I had originally been marking up a PDF sent to me generated using Mac OS X 10.5.7 Quartz PDFContext when I first encountered this, but since then I have reproduced this using simple.pdf, which I generated using StyledEdit and the PDF Writer driver.
Trying with the PDF sent to me but following similar steps, I've had (also reproduceable) the unfortunate result that it produces a PDF but without my latest annotations (this is both if I immediately choose to save a debug report, or try to debug, save the debug report, and then tell the debugger to continue)--in fact, the file size is identical to the version just opened containing the first round of annotations. So I'm attaching that PDF too.
Thanks for the note!
A few suggestions for improving the readability of the crash reports:
- Use a table format for the images, areas, and semaphores sections. Moving the name column rightmost, everything could be neatly aligned and would take a lot less horizontal space.
- Move the images, areas, and semaphores sections to the end of the report. I believe the threads section is usually the most interesting and should be topmost.
- In the areas section use hex format for the area size (or an end address), so it is easier to see whether an address falls into an area.
- Sort the images by address.
- Consider making the images table format similar to the areas table, maybe even two lines per image.
Hello! When type ' cal ' command in the Terminal, the app show the first row of days misaligned (please, see attachment).
On VirtualBox, with the Intel PRO gigabit NIC, doing the following results in a network configuration without default route.
ifconfig /dev/net/ipro1000/0 down ifconfig /dev/net/ipro1000/0 up auto-config
Note that at startup the default route is present and is correct
This is hrev45525.
Since the recent keystore addition, connecting to wifi isn't working every time. Connecting via the NetworkStatus icon in the Deskbar works sometimes, sometimes it doesn't. Sometimes I get asked to give the wpa_supplicant access to the keystore ("Allow always"), sometimes not. Then, while connecting, the connection window with the already filled in password appears 3 times after another. I'm not sure if I should check the box "Store this configuration" or not...
Anyway, then often the wpa_supplicant crashes, see attached report plus syslog and syslog.old. Not sure how much of syslog.old is from that session. Is there a way to detect the start of the entries for the most recent session?
In this session, I tried to down/up/scan with ifconfig to make my network ("haiku-top") visible again in the NetworkStatus replicant and tried once more to connect. Same result.