[haiku-bugs] Re: [Haiku] #5485: 103: DEBUGGER: _numBlocks > 0
- From: "mmadia" <trac@xxxxxxxxxxxx>
- Date: Sat, 27 Feb 2010 17:31:13 -0000
#5485: 103: DEBUGGER: _numBlocks > 0
--------------------------------+-------------------------------------------
Reporter: mmadia | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: Servers/app_server | Version: R1/Development
Keywords: | Blockedby:
Platform: All | Blocking:
--------------------------------+-------------------------------------------
Comment(by mmadia):
Replying to [comment:1 stippi]:
> These are random heap corruptions. But I wonder why it drops in the
white GDB session. When have these crashes started?
I'm not sure. After upgrading to 35500 or newer, the vm_page_faults have
been occurring. I never reported them, as it looked to be fixed in a newer
revision. Over a few updates, I've lost track of the first revision the
_numBlocks > 0 occurred.
Replying to [comment:3 bonefish]:
> Just to clarify, Matt, you're getting crashes ("_numBlocks > 0" debugger
calls) from various teams, but only when it happens in the app server you
get the white gdb screen, right? If so, then this is probably a bug in
libroot or libbe.
>
Right. Other times the application itself will crash, raising a debug
alert window. More often than not, it's in app_server. To note,
vm_page_faults still show up on the serial log at times. Later today, I'll
be updating a second partition to trunk.
> You could try to use the debug libroot globally (e.g. "export
LD_PRELOAD=libroot_debug.so" at the beginning of the BootScript, or rename
libroot.so and symlink to libroot_debug.so). Maybe that will turn up
something earlier.
Attached is the output with the export statement in use.
--
Ticket URL: <http://dev.haiku-os.org/ticket/5485#comment:7>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
