On Thu, Mar 13, 2008 at 11:14:04AM +0000, Amos Shapira wrote:
> On Thu, Mar 13, 2008 at 8:43 AM, Dan Kenigsberg <[EMAIL PROTECTED]>
> wrote:
>
> > On Thu, Mar 13, 2008 at 02:08:05PM +1100, Amos Shapira wrote:
> > > On Thu, Mar 13, 2008 at 3:29 AM, Dan Kenigsberg
> > > <[EMAIL PROTECTED]> wrote:
> > > > Thanks for the idea. What could cause SIGSEGV on brctl?
> > > > My dmesg has a lot of noise, but no segfault visible.
> > > >
> > > > Mar 9 04:53:49 w kernel: device if_11 entered promiscuous mode
> > > > Mar 9 04:53:49 w kernel: sw0: port 5(if_11) entering learning state
> > > > Mar 9 04:53:49 w kernel: sw0: topology change detected, propagating
> > >
> > > Enable core dumps ("ulimit -c unlimited").
> >
> > Did that. No traces of a segfault.
>
>
> What do you mean? Have you tried to run brctl without getting a core dump
> when it bombed?
I mean that I recreated the error with -c unlimited, and no core was dumped.
I don't know what THAT means.
--
Dan Kenigsberg http://www.cs.technion.ac.il/~danken ICQ 162180901
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
