On Mon, May 22, 2006 at 09:24:32PM +0200, Jan Kiszka wrote:
> PS: Please CC me on reply.
>
> [1] http://gcc.gnu.org/ml/gcc-help/2006-05/msg00202.html
Would you mind following up to yourself? This seems like a gcc bug
because if the weak function is _not_ empty, things work as expected.
And that
Tom Rini wrote:
On Mon, May 22, 2006 at 09:24:32PM +0200, Jan Kiszka wrote:
Hi,
I stumbled over some issue of kgdb in combination with gcc 4.1 since
kernel 2.6.16. The background can be found in [1]. It melts down that
the default arch-dependent functions in kernel/kgdb.c got compiled in -
and
On Fri, May 19, 2006 at 10:15:39PM +0400, Vladimir A. Barinov wrote:
> The stack exception occurs always at the same step during debugging in
> kgdb_mem2hex().
> I've attached patch that fixes this issue. Could you please review, is
> this patch appropriate
> to the problem?
>
> Vladimir
> --
On Mon, May 22, 2006 at 09:24:32PM +0200, Jan Kiszka wrote:
> Hi,
>
> I stumbled over some issue of kgdb in combination with gcc 4.1 since
> kernel 2.6.16. The background can be found in [1]. It melts down that
> the default arch-dependent functions in kernel/kgdb.c got compiled in -
> and immedia
Hi,
I stumbled over some issue of kgdb in combination with gcc 4.1 since
kernel 2.6.16. The background can be found in [1]. It melts down that
the default arch-dependent functions in kernel/kgdb.c got compiled in -
and immediately optimised out again. The effect is, of course, lethal.
As a workar
