public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
To: b.a.t.m.a.n@open-mesh.net
Subject: Re: [B.A.T.M.A.N.] problems running batman rev350
Date: Mon, 21 May 2007 20:12:05 +0200	[thread overview]
Message-ID: <200705212012.05818.axel@open-mesh.net> (raw)
In-Reply-To: <4651838D.3000203@gmx.net>

Hello Dragan,

If you want you can try rv360 now. Marek fixed two of the bugs indicated by 
you. Hopefully its better now and thanks a lot for your help. 

Seems like your real-time kernel makes you a real-time debugger :-)

ciao,
axel



On Monday 21 May 2007 13:33, Dragan Noveski wrote:
> Marek Lindner wrote:
> > Hi,
> >
> >> since i got the core dump created now, i suppose that the patches are in
> >> rev352?
> >>
> >> pleas tell me what to do with the core file, but for now i will attach
> >> it.
> >
> > to fully debug your problem I need the binary you created the core dump
> > with. Do not create a new binary - I have to have the binary which was
> > running during the segmentation fault.
> >
> > Regards,
> > Marek
>
> where can i upload the binary?
>
> cheers,
> doc
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n

      reply	other threads:[~2007-05-21 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19 14:55 [B.A.T.M.A.N.] problems running batman rev350 Dragan Noveski
2007-05-19 15:49 ` Axel Neumann
2007-05-19 17:02   ` Dragan Noveski
2007-05-19 17:31     ` Dragan Noveski
2007-05-19 18:44       ` Dragan Noveski
2007-05-19 20:10         ` Marek Lindner
2007-05-21 10:35           ` Dragan Noveski
     [not found]             ` <200705211311.50293.lindner_marek@yahoo.de>
2007-05-21 11:33               ` Dragan Noveski
2007-05-21 18:12                 ` Axel Neumann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200705212012.05818.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox