On Tue, 30 May 2017 11:04:57 +0200
Arvin Schnell <[email protected]> wrote:

> On Tue, May 30, 2017 at 10:04:33AM +0200, Josef Reidinger wrote:
> 
> [...]
> 
> > Now lets get to storage-ng. I try to port this fix there. So my
> > first question is, what is similar equivalent in storage-ng
> > which allows me to see if there is change in storage, so
> > bootloader proposal is no longer valid?  
> 
> That was discussed and even documented in
> yast2-storage-ng/doc/software-requirements.md but unfortunately
> already deleted. Have a look at
> https://w3.suse.de/~shundhammer/storage-timer.txt.

Thanks for pointing this out. I will try to discuss it today with ancor when he 
is still in Prague.

> 
> [...]
> 
> > Also I have to say, that from user POV, segfault and ruby
> > exception is very very different. When I get ruby exception, I
> > see popup saying what is a problem. I can continue. I was asked
> > to report bug. And the most important part, I can get logs as
> > environment still lives! When I get segfault, I get quick black
> > screen followed by red area on blue which mention Error occured
> > during installation without any details and what is more
> > important: I do not find way how to get any logs, at least
> > y2signal log will be useful!!  
> 
> AFAIR as long as the red popup is there you can switch to another
> console and copy logs and debug the issue.

Thanks, I am not aware about this possibility. So we should at least add it as 
hint for customers which face it and want to grab logs.

> 
> For debugging I recommend to attach gdb before the error happens.

In the end with a bit help from google I can get ruby backtrace.

So for future reference, you can get ruby backtrace in gdb ( or if you get core 
).
with this command:

p rb_eval_string_protect("puts caller.inspect", (int *)0)

which will print it to console. If stdout is redirected, you can there write it 
to file with 

p rb_eval_string_protect("File.write(\"/tmp/debug\", caller.inspect)", (int *)0)


And it should also work with core dumps. So what we need in such case from 
customers are core dump from them, which looks reasonable.

Thanks for help

Josef

> 
> ciao
>   Arvin
> 

-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to