Re: Can't install hw-probe on OpenSuSE 15.4
On 2024-08-16 14:47, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [08-16-24 07:05]:
On 2024-08-11 22:20, Dave Howorth wrote:
On Sun, 11 Aug 2024 20:27:49 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-08-11 14:40, Andreas Stieger via openSUSE Users wrote:
On 2024-08-11 14:33, Carlos E. R. wrote:
I don't understand the instructions in comment 2.
gdb /usr/bin/vdpauinfo <core-file> (gdb) bt
What is "<core-file>"? What do I write there EXACTLY?
It is the core file produced when vdpauinfo crashes. You put the full address of the file. (You may need to check your configuration to make sure it creates core files and to find where it puts them. I have no idea how to do that in opensuse. RTFM?)
How can I put the name of the core file produced after the crash, into the gdb command line which is written before it crashes?
It is nonsensical.
/var/lib/systemd/coredump/core.....
I know that. That is not the problem. I have to run gdb /usr/bin/vdpauinfo <core-file> which I understand will run vdpauinfo, then crash and generate a report and a coredump. But they tell me that <core-file> is from the previous crash! It doesn't make sense. I need the exact complete command sequence I have to run, or precise and complete instructions. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On Fri, 16 Aug 2024 20:46:30 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-08-16 14:47, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [08-16-24 07:05]:
On 2024-08-11 22:20, Dave Howorth wrote:
On Sun, 11 Aug 2024 20:27:49 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-08-11 14:40, Andreas Stieger via openSUSE Users wrote:
On 2024-08-11 14:33, Carlos E. R. wrote:
I don't understand the instructions in comment 2.
gdb /usr/bin/vdpauinfo <core-file> (gdb) bt
What is "<core-file>"? What do I write there EXACTLY?
It is the core file produced when vdpauinfo crashes. You put the full address of the file. (You may need to check your configuration to make sure it creates core files and to find where it puts them. I have no idea how to do that in opensuse. RTFM?)
How can I put the name of the core file produced after the crash, into the gdb command line which is written before it crashes?
It is nonsensical.
/var/lib/systemd/coredump/core.....
I know that. That is not the problem.
I have to run
gdb /usr/bin/vdpauinfo <core-file>
which I understand will run vdpauinfo, then crash and generate a report and a coredump. But they tell me that <core-file> is from the previous crash! It doesn't make sense.
No you run gdb after the crash with the corefile. The command bt causes gdb to produce a backtrace of what caused the crash. $ man gdb (i.e. RTFM !!!)
I need the exact complete command sequence I have to run, or precise and complete instructions.
On 2024-08-16 22:13, Dave Howorth wrote:
On Fri, 16 Aug 2024 20:46:30 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-08-16 14:47, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [08-16-24 07:05]:
On 2024-08-11 22:20, Dave Howorth wrote:
On Sun, 11 Aug 2024 20:27:49 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-08-11 14:40, Andreas Stieger via openSUSE Users wrote: > > On 2024-08-11 14:33, Carlos E. R. wrote:
I don't understand the instructions in comment 2.
gdb /usr/bin/vdpauinfo <core-file> (gdb) bt
What is "<core-file>"? What do I write there EXACTLY?
It is the core file produced when vdpauinfo crashes. You put the full address of the file. (You may need to check your configuration to make sure it creates core files and to find where it puts them. I have no idea how to do that in opensuse. RTFM?)
How can I put the name of the core file produced after the crash, into the gdb command line which is written before it crashes?
It is nonsensical.
/var/lib/systemd/coredump/core.....
I know that. That is not the problem.
I have to run
gdb /usr/bin/vdpauinfo <core-file>
which I understand will run vdpauinfo, then crash and generate a report and a coredump. But they tell me that <core-file> is from the previous crash! It doesn't make sense.
No you run gdb after the crash with the corefile. The command bt causes gdb to produce a backtrace of what caused the crash.
$ man gdb (i.e. RTFM !!!)
Why should I? I'm not a developer, I just reported a bug. I'm happy to run the commands they tell me, but that's it. Anyway, with your help I managed to produce the requested BT and submit it to the bugzilla. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On Sat, 17 Aug 2024 15:13:44 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-08-16 22:13, Dave Howorth wrote:
On Fri, 16 Aug 2024 20:46:30 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-08-16 14:47, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [08-16-24 07:05]:
On 2024-08-11 22:20, Dave Howorth wrote:
On Sun, 11 Aug 2024 20:27:49 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
> On 2024-08-11 14:40, Andreas Stieger via openSUSE Users > wrote: >> >> On 2024-08-11 14:33, Carlos E. R. wrote:
> I don't understand the instructions in comment 2. > > gdb /usr/bin/vdpauinfo <core-file> > (gdb) bt > > > What is "<core-file>"? What do I write there EXACTLY?
It is the core file produced when vdpauinfo crashes. You put the full address of the file. (You may need to check your configuration to make sure it creates core files and to find where it puts them. I have no idea how to do that in opensuse. RTFM?)
How can I put the name of the core file produced after the crash, into the gdb command line which is written before it crashes?
It is nonsensical.
/var/lib/systemd/coredump/core.....
I know that. That is not the problem.
I have to run
gdb /usr/bin/vdpauinfo <core-file>
which I understand will run vdpauinfo, then crash and generate a report and a coredump. But they tell me that <core-file> is from the previous crash! It doesn't make sense.
No you run gdb after the crash with the corefile. The command bt causes gdb to produce a backtrace of what caused the crash.
$ man gdb (i.e. RTFM !!!)
Why should I?
Because it might avoid you repeatedly asking the same silly question, which is what you have been doing :P :)
Anyway, with your help I managed to produce the requested BT and submit it to the bugzilla.
Glad to hear it :)
participants (2)
-
Carlos E. R. -
Dave Howorth