Displaying 6 results from an estimated 6 matches for "fbreg".
Did you mean:
breg
2012 Jul 23
2
Intel D2500cc video problem: no scrolling
Dear colleagues,
in the process of upgrading my home router I'm trying to utilise Intel D2500CC
mini-ITX motherboard[1].
Both stable/9 and head suffer from no scrolling issue: from the beginning of
booting the kernel, all output overrides the last line on the screen, while
others keep the loader phase.
Provided the board has multiple serial ports and the final target (headless
2012 Apr 26
1
[LLVMdev] Bug with debug information generation?
...files, the output is almost entirely the same, though in the working case, it had AT_frame_base( rsp ), while the broken case had AT_frame_base( rbp ). Some of the PC extents are different, but in ways that look reasonable. For the location of "r" in the working case, it has AT_location( fbreg -4 ), with AT_location( fbreg +28 ) in the broken case. These locations both seem correct, based on an eyeballing of the assembly output, so there's nothing obviously wrong there, either.
>
> I'd be delighted to hear any suggestions or pointers!
>
> Thanks,
> -matt
>...
2011 Oct 13
1
[LLVMdev] Local variable information in scope
Hi,
I want to list some additional information on this.
The variable collection I am looking at is, "variables 'declared' in scope".
1. When I traverse the MachineInstructions in the LexicalScopes ranges, and check for variables, I get variables used in this scope.
The variables listed include variables which may not have been declared in the scope. (for example
2012 Apr 23
0
[LLVMdev] Bug with debug information generation?
...files, the output is almost entirely the same, though in the working case, it had AT_frame_base( rsp ), while the broken case had AT_frame_base( rbp ). Some of the PC extents are different, but in ways that look reasonable. For the location of "r" in the working case, it has AT_location( fbreg -4 ), with AT_location( fbreg +28 ) in the broken case. These locations both seem correct, based on an eyeballing of the assembly output, so there's nothing obviously wrong there, either.
I'd be delighted to hear any suggestions or pointers!
Thanks,
-matt
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
Sorry, this is the attachment.
2014-02-19 15:08 GMT+08:00 杨勇勇 <triple.yang at gmail.com>:
> Thank you.
>
> Here is an example and the attchment contains extra files including object
> file and executable file.
> I want to print for example the value of "a", but lldb command "frame
> variable a" displays "0" and so does "b", and
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...; DW_AT_name( "a" )
> DW_AT_decl_file(
> "/home/yangyy/workspace/newlib/test.c" )
> DW_AT_decl_line( 4 )
> DW_AT_type( {0x0000007f} ( int ) )
> DW_AT_location( fbreg +16 )
>
> The location says it is at the frame base register + 16 bytes. The frame
> base is defined in the parent DIE:
>
> 0x00000022: DW_TAG_subprogram [2] *
> DW_AT_name( "main" )
> DW_AT_decl_file( "/home/yangyy/workspace...