Hi!
I'm having a very weird problem with gdb. I hadn't used the debugger for
some time, so I'm not sure for how long it has been broken...
The problem is that the debugged program does not stop in any breakpoing,
exception, signal... nothing. Just as if it weren't being debugged.
First I thought
Rodrigo Rivas gmail.com> writes:
>
> Hi!
>
> I'm having a very weird problem with gdb. I hadn't used the debugger for
> some time, so I'm not sure for how long it has been broken...
> The problem is that the debugged program does not stop in any breakpoing,
> exception, signal... nothing. Just
On Sat, Nov 23, 2013 at 3:18 PM, jb wrote:
> Rodrigo Rivas gmail.com> writes:
>
> >
> > Hi!
> >
> > I'm having a very weird problem with gdb. I hadn't used the debugger for
> > some time, so I'm not sure for how long it has been broken...
> > The problem is that the debugged program does not sto
On 23/11/2013 13:14, Rodrigo Rivas wrote:
> So it looks like some kind of permission issues. Maybe something related to
> the recent SELinux changes?
Nothing related to SELinux support has been merged in official Arch
packages for now (as far as I know). And even if it had been, SELinux
would cert
All, tpowa,
As of approximately 8-12 months ago, I was under the impression that upstream
dmraid would not continue and that dmraid functionality would move into mdraid.
(maybe that was just an arch plan?) Early in the discussion on this list it was
noted that not all existing dmraid chipset sup
On Sun, Nov 24, 2013 at 1:03 AM, Timothée Ravier wrote:
> On 23/11/2013 13:14, Rodrigo Rivas wrote:
> > So it looks like some kind of permission issues. Maybe something related
> to
> > the recent SELinux changes?
>
> Nothing related to SELinux support has been merged in official Arch
> packages
6 matches
Mail list logo