On Tue, Jun 25, 2019 at 12:26:55AM +0200, Mark Wielaard wrote:
> Hi,
>
> On Wed, 2019-04-17 at 14:41 +0800, Mao Han wrote:
> > I'v just spent sometime debuging this. Core dump backtrace on C-SKY
> > seems
> > can't be supported with current generic routine. DWARF register order is
> > different fr
Hi,
On Wed, 2019-04-17 at 14:41 +0800, Mao Han wrote:
> I'v just spent sometime debuging this. Core dump backtrace on C-SKY
> seems
> can't be supported with current generic routine. DWARF register order is
> different from the order in core notes. The initialization of frame
> registers is totall
On Sun, Apr 14, 2019 at 10:23:49PM +0200, Mark Wielaard wrote:
> It is hard to say what went wrong.
> In theory you can examine the executable and core file cross arch, if
> there is backend support. So if you could post a small binary and a
> core file for it somewhere we can try debugging togethe
On Wed, 2019-04-10 at 15:51 +0800, Mao Han wrote:
> I'v check some of the failed testcase.
Thanks for double checking, it seems we understand all of the cases why
they fail except...
> > I haven't looked at the code yet, so maybe none of the backtrace tests
> > would work even if you could run in
I'v check some of the failed testcase.
> > FAIL: run-native-test.sh
> >
> >
> > allregs: 23064: No such file or directory
> > FAIL run-native-test.sh (exit status: 1)
>
> This is probably because of the script modifications. The test cannot
> find the running process.
>
