Re: How to make sure your applications still works with Bug-Buddy 2.16.0

[Behdad Esfahbod <behdad behdad org>]

On Sun, 2006-08-13 at 22:27 +0200, Fernando Herrera wrote:
> Replying to my-self, this time adding d-d-l :)
> 
> I did a try with bug-buddy adding the /proc/self/maps contents:
> 
> http://bugzilla.gnome.org/show_bug.cgi?id=351197
> 
> Those contents are really huge for a GNOME applications linked to our
> "little" stack of libraries.

Wow, that's really long.  Maybe you can make it do it as an attachment?
That needs more work though.  Is there a way to make it not wrap the
lines?  Some kind of <pre> element that bugzilla supports?

> I know that "pmap" output is smaller and prettier, but is it installed
> on all GNOME supported platforms?

On Linux systems pmap should be always available.  On SunOS pmap is
available and useful too, but /proc/self/map (map, not maps) is
available but apparently has some kind of binary format.  Not sure about
any other systems.

behdad  

> Salu2
> 
> On 8/13/06, Fernando Herrera <fherrera onirica com> wrote:
> > On 8/13/06, Behdad Esfahbod <behdad behdad org> wrote:
> > > Another thing that may be very easy to get in Bug-Buddy, yet is very
> > > helpful to developers is the output form pmap on the crashed process.
> > > Tells a fortune in one list.  Do you think you can do that?
> >
> > Yes, is it quite easy, I was planning to include that when no gdb nor
> > debug info is present:
> > - mem map of the application
> > - linked libraries md5sum
> > - symbolic stack trace
> >
> > so we could populate this backtrace on server-side (the famous debug
> > server project).
> >
> > However, if you find useful the mem map with current reports, I can add it.
> >
> > Salu2
> >
-- 
behdad
http://behdad.org/

"Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill"
        -- Dan Bern, "New American Language"